283 karma · joined February 18, 2016
https://www.ardmediathek.de/video/comedy-und-satire/dinner-f...
It is rarely broadcasted in Germany, however, because people just like the original black and white version better and vocally rejected the colorized version when it was first aired.
There were also plans to record a live version in color in 1968, but Freddy Frinton sadly passed away before it was realized.
There are also some German adaptations, like the one with Anette Frier and Ralf Schmitz (two well-known comedians). It's in _kölsch_, the dialect spoken in the Cologne area - which is quite fun to listen to, at least for Germans:
In bigger projects and companies, there might be a dedicated person for each aspect of the process, a designer, and front end developer, etc. But the responsibilities are also different in that case. For example, a UX person doesn't just tell you that something isn't as intuitive as it could be or even improve it, but conduct actual research like A/B testing etc. to properly asses the usability, compare different design solutions and so on.
Conan's recent development is promising and it gives you the full power of Python. It can also be used declaratively but with limitations. If I remember correctly, there are discussions in the C++ world about a declarative exchange format for dependencies and build information, but it's in the early stages. It's not trivial because there are also C++ modules now.
Some guesses:
- Because scientists aren't that much into programming and Python is one of the easier languages to start with?
- Some aspects of its language design, like the syntax for slices, making it easy to express often used operations in a rather intuitive way?
- The two points above leading to the numpy project, enabling high-volume computations with a friendly programming language?
- Maybe Jupyter Notebooks played a role as well? It's a great teaching tool.
Another use case was parsing proprietary, text-based file formats with ancient encodings. I believe I did use Python for that as there wasn't that much data to convert anyway and it just worked.
I have the feeling that its user base is pretty lopsided, but I might underestimate its importance in other areas, like teaching programming. I'd love to see a breakdown of its popularity by field.
In reality you just end up [with] a shitty, nerfed version of a programming language, that [...] users can't understand, because you still have to understand [CMake's] logic to [utilize its magic behavior], oh and [the] documentation is terrible because devs don't bother with the boring stuff. Most of the time [you] end up implementing [workarounds] anyway because [CMake doesn't] actually work properly.
My manager shared this opinion and said, we can't sell our software with the argument that users need specialized software and do the exact opposite ourselves by using software that wasn't even remotely designed and fit for project management and the like. Custom solutions do also have certain advantages. But you get like 80% of what you want with common software, usually for a reasonable price and without the headache.
A more interesting question would be how likely code AI is to introduce security vulnerabilities with a training set of high quality code that has no (well, hardly) any vulnerabilities. Does it still cause security issues because it doesn't truly "understand" what it does, merely piecing together text fragments with little "thought"?
For personal use, maybe it's not that much of an issue, except for bank accounts? I wonder if I should store credentials locally using a password manager, and regularly create physical copies in paper form, which should be in two different locations at least. Password rotation and new credentials make this challenging, however.
What did monks do if not copy books?
The Compiler Explorer backstory starts here: https://youtu.be/bSkpMdDe4g4?t=4m57s
If there was an integrated web server, but fully decoupled to not block the database, then there would probably be no real benefit over running a separate web server on the side.