Please more details - I can not find any feature on the OBS website similar to what we see here. Do we need some plugin / extension? Please give us some urls, thank you!
b) Can anybody please describe the general experience with Centos for a media production machine - needs to run NVIDIA GPU support, Ardour, low latency jackd and Davinci Resolve on XFCE.
But I did not make an "overarching indictment" based on a requirements-feature misalignment. That was just the starting point for taking a closer look.
Do your analysis of the users permissions design of that software and ask yourself how would you do that or compare to other systems and you will understand what I mean.
Also I was writing about unnecessary limitations possibly introduced by framework usage - and this was just a friday afternoon virtual water cooler talk, certainly not a scientific thesis. And certainly I do not want to go for war about it with anyone, that was just a little reminder for younger programmers to never stop asking questions about the tools they use.
Last year I was looking for a tool where one team could provide chat support to customers - of course the customers should have their own space, in tulip this would be organizations. Zulip comes with some good UI ideas for a chat system, the multi-organization experience was not so great.
Unfortunately it was not possible to have users take part in several organizations - so each support team member would need to have one account in each organization - that gets messy really quick.
I do not think that this is a very edgy use case, but it is an indicator of some underlying design limitation. Having users limited to 'org' does not seem to make sense - instead it is obvious that one wants to have users and groups and some sane way to fine-tune rw permissions and visibility between groups and objects that groups create.
I was wondering if such an obvious limitation in the basic design was somehow induced by the use of Django. A programmer with some DB design experience would have spotted that quirk in a very early stage. I understand that Django traps new users into these kind of constructs with its obscure db layer - this is the microsoft principle - 'hiding complexity' in the end leads to hiding knowledge and makes people produce problematic results.
It is a good example of how the use of a framework can destroy a good software idea. Hopefully some people with good db knowledge can fork the frontend and build a better backend for Zulip - obviously Elixir would be a good fit with its soft-realtime channels for this kind of communication software.
Zulip is still good enough for more simplistic use cases, but you could use any php chat system out there without the incredible installation and maintenance overhead that python brings in - absurd over-complication seems to be another symptom of the framework disease, people just do not seem to know that they are in the 'absurd zone' because they have never seen how it can be done in a much easier way.
The tools you use make up your view of the world, so you can not understand what people with other tools are even talking about as long as you do not try them. A good lesson for every developer to stay open-minded and not let productivity pressure eat your learning and research time.
EU GDPR compatibility would be a cool thing - I am sure that people have been asking for that "long time enough" ago.
Also now that this software has left prototype status for long enough time - why are you still using ruby?
Ruby is much too slow and bloated for production - there are only a few companies out there that missed the right time to jump from the ruby-prototype-bloat and have enough money to burn to just stick with it, but for a project like gitlab this is a huge problem. Judging from the roadmap there seem to be many bored developers with no good ideas about what to do next, so maybe unbloating could be a good direction?
There must be at least one person in that team with a feeling for architectural brilliance?
* How is the workflow for updating OSM data with this project?
* What is the recommended procedure for backup + restore?
I find a lot of projects in this space make you go through an manual copy-paste setup process like if it was a one-time thing - it is not - updating OSM data is a crucial part in this process and should be part of it.
* is the proxy cache an accepted use case also for commercial projects? Where can I find details about that?
* what is your recommendation for a geocoder?
Also I would like to ask you about your procedure for updating the OSM data and tiles - I found this to be a tedious process. Not at all is this a one-time set-and-forget thing, it is quite a bit of things to understand and maintain.