What makes you think python is in optimized and bloated?
Did you know vast majority of AI development happening right now is on python? The thing that literally consumes billions of dollars of even-beefier-than-4090 GPUs like A100. Don't you think if they could do this more efficiently and better on C or assembly, they would do it? They would save billions.
Reality is that it makes no benefit to move away from python to lower level languages. There is no poor optimization you seek. In fact if they were to try this in lower level languages, they'll take even longer to optimize and yield worse results.
Idk, it's rare for an electron app to literally not even run. Meanwhile I'm yet to encounter a python app that doesn't require me to Google what specific environment the developer had and recreate it.
With a properly packaged python app, you shouldn't even notice you're running a python app. But yeah, for some reason there's a lot of them that ... aren't.
Ah yes, those precious precious CPU cycles. Why spend one hour writing a python program that runs for five minutes, if you could spend three days writing it in C++ but it would finish in five seconds. Way more efficient!
Because when it is to actually get paid work done, all the bloat adds up and that 3 days upfront could shave weeks/months of your yearly tasks. XKCD has a topic abut how much time you can spend on a problem before effort outweighs productivity gains.
If the tasks are daily or hourly you can actually spend a lot of time automating for payback
And note this is one instance of task, imagine a team of people all using your code to do the task, and you get a quicker ROI or you can multiply dev time by people
SDLC can be made to be inefficient to maximize billable hours, but that doesn't mean the software is inherently badly architected. It could just have a lot of unnecessary boilerplate that you could optimize out, but it's soooooo hard to get tech debt prioritized on the road map.
Killing you own velocity can be done intelligently, it's just that most teams aren't killing their own velocity because they're competent, they're doing it because they're incompetent.
And note this is one instance of task, imagine a team of people all using your code to do the task, and you get a quicker ROI or you can multiply dev time by people
In practice, is only quicker ROI if your maintenance plan is nonexistent.
So, I've noticed this tendency for Python devs to compare against C/C++. I'm still trying to figure out why they have this tendency, but yeah, other/better languages are available. 🙃
I mean, I'd say it depends on what you do. When I see grad students writing numeric simulations in python I do think that it would be more efficient to learn a language that is better suited for that. And I know I'll be triggering many people now, but there is a reason why C and Fortran are still here.
But if it is for something small, yeah of course, use whatever you like. I do most of my stuff in R and R is a lot of things, but not fast.
I know it makes me sound like an of man shouting at clouds but the other day I installed Morrowind and was genuinely blown away by how smooth and reliable it ran and all the content in the game fitting in 2gb of space. Skyrim requires I delete my other games to make room and still requires a whole second game worth of mods to match the stability and quantity of morrowind.
High res textures (especially normal maps) and higher quality/coverage audio really made game sizes take off. Unreal's new "Nanite" tech, where models can have literally billions of polygons, actually reduces game size because no normal maps.
Yes, but also community rewrite of the Morrowind engine, to make it even more better: https://openmw.org/
Admittedly, some changes might make it use more resources, for example it's got basically no loading screens, because nearby cells get loaded before you enter them...
Tbh this all seems to be related to following principles like Solid or following software design patterns. There's a few articles about CUPID, SOLID performance hits, etc
it all suggests that following software design patterns cost about a decade of hardware progress.
If SOLID is causing you performance problems, it's likely completely solvable.
Most companies throwing out shitty software have engineers who couldn't tell you what SOLID is without looking it up.
Most people who use this line of reasoning don't have an actual understanding of how often patterns are applied or misapplied in the industry and why.
SOLID might be a bottle neck for software that needs to be real-time compliant with stable jitter and ultra-low latency, the vast majority of apps are just spaghetti code.
It used to be pretty terrible, but the frameworks are getting there, starting with the languages they are based on.
Believe it or not, Java has been optimized a ton and can be written to be very efficient these days. Another great example of a high-level, high-efficiency language is Julia. And then there is Rust of course, which basically only sacrifices memory-efficiency for C-speeds with Python-esque comfort. It's getting better.