I think the sore point is definitely build and packaging systems. Take zulip for example, they do use requirements but they go their own way in most other thin

I think the sore point is definitely build and packaging systems. Take zulip for example, they do use requirements but they go their own way in most other things. Managing an application is much easier if it uses standard build system. Setup.py, requirements.txt and so forth. Gitlab is an example of a very complex packaging for a ruby application, but it works! It's complex but solid. People are tugging in all kinds of different directions. My bad experiences with Ruby and node usually include seeing a loooong list of dependencies being installed and then at dependency #187 it suddenly stops for some reason like one rogue commit breaking compatibility with other packages. This is hell to someone who doesn't develop in the language regularly, it's a bad packaging system for users. To be clear, I'm not saying Python is better. I'm just identifying the issues I've had. The only reason Python is easier for me is because I've decided to use it more than the other languages. On the one hand you can build a complex but solid system like Gitlab has, on the other you can use more standardized systems to distribute your app that require more steps and are less automated. But they're well documented and established methods used for that language.