German content is mostly on Sharehosters or One-Click-Hosters or whatever you call them. I really don’t know why because they are expensive and worse than the other options. I know BitTorrent is not popular in Germany because of the law but the Usenet could be the better option if it was more popular.
It’s the amount of legacy it’s carrying on that drives me crazy. Many of the implicit default implementations are confusing. That’s where all these “rule of 3”, “rule of 7”, “rule of whatever” come from. The way arguments are passed into functions is another issue. From the call-side you (sometimes) cannot tell if you’ll end up with a moved value or a dangling reference. The compiler will not stop you from using it. Even if the compiler has something to tell you, it’ll do it on the most cryptic way possible. I’m grateful we have C++, it paid lots of my bills. But it’s also a pain in the ass.
tl;dr Language evolution and future outlook are big factors besides the existing language features themselves.
I guess Rust has attracted many C++ devs because C++ is painful and there were no other/better options. Rust comes with a build/dependency management system and memory safety guarantees on top of the type safety. Even though C++ templates are still unmatched, I prefer Rust 95% of the time. C++ is evolving very slow and it’s extremely hard to participate. Rust will win that race eventually.
Python has been around since 1991(!) and it took a looong time to build the community. It was a niche like Nim is now for many years.
I’ll definitely keep an eye on Nim because it has the potential to become quite popular.
Again, that’s all just my opinion.
I have to disagree with your “when use what” list. Python has production ready web backend frameworks, Rust is perfectly fine for complex and high-level software, and PHP is mostly obsolete. That’s my humble opinion though. I looked into Nim and like many of the concepts. It’s quite complex and I prefer Rust most of the time when Nim would be an option. I’d argue it’s some kind of “jack of all trades”. A bit like python but compiled, ref-counted, and probably a lot faster. It’s lacking the huge community python has though.
Apple Music is different because it uses ALAC not FLAC which actually sounds better, definitely a must-have service.
That’s only because Apple marketing makes you believe this. They are both lossless, up to 32 bits/sample and very high sample rates (FLAC allows even higher ones than ALAC afaik). The only “advantage” of ALAC is Apple ecosystem compatibility but that’s only for them to lock you in and make it harder for you to migrate.
It could sound better if they - for whatever reason - had access to better recordings, but that still doesn’t have anything to do with the codec.
Danke :-)