I personally have moved on to a Nim + Lua combo (depending on use case), because I can see your point. But I will always love Python.
I too am looking into nim more and more recently because I don't want to write code without static typing anymore and it has very nice syntax and native compilation.
Each of the tools you mention have their good part wrt/ one of those four categories, and the rest is an afterthought.
They did not end up doing one thing well, but one thing well and the other three too. Not as well.
The way, or one way to change that would be to borrow the overall idea and semantics from each "good" implementation, but to limit it to just that; and build four separate projects under one community, so that there is pollination of knowledge and efforts, but no cross-contamination of goals and semantics.
I'm not sure I am the person to start something like that.
Isn’t it a perfectly understandable reason? We regularly pan C++ on here for its smorgasbord of implementation options for any given thing, and the complexity, customization, and fragility of a C++ code base always seems to be high especially for non experts in the domain.
So, accordingly, people who know how to maintain code in a simpler and more flexible setup and can still convert to C++ for performance are taking a probable performance hit relative to “native” C++ (whatever that is in 2021), in order to maintain their tool with more ease.
It’s very silly you move to slandering python developers and not contemplating the trade offs meaningfully
Furthermore, there is no shortage of statically typed compiled languages to choose from. Go, Rust, Java(with GraalVM) or my recent favourite, Nim comes to mind.
> It's written in Python, so the code is short and easy to change. But we automatically translate it to C++ with custom tools, to make it fast and small. The deployed executable doesn't depend on Python.
Why Python developers will do absolutely anything to work around the limitations of python but not use a different language.