Sooo if you have significant CPU & RAM constraints, like when working in the embedded world, pick a tool that works for it (e.g. MicroPython, ha).
The fear of the unknown future is not a great argument against today's problems, we shouldn't write great programs faster because in the future we might not be able to just buy more RAM.
If you honestly want everyone to write everything in assembler and optimize both CPU & RAM use (which, as I explained earlier, is impossible) for everything written, you can expect the software world to not move anywhere.
There aren't enough working hours in the world to do that.
Sensible people pick the battles that are important and focus on those: Some specific bit is taking too much CPU/RAM on Python? Write that bit as a C extension for Python, write the bits that aren't that critical in plain Python.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Sooo if you have significant CPU & RAM constraints, like when working in the embedded world, pick a tool that works for it (e.g. MicroPython, ha).
The fear of the unknown future is not a great argument against today's problems, we shouldn't write great programs faster because in the future we might not be able to just buy more RAM.
If you honestly want everyone to write everything in assembler and optimize both CPU & RAM use (which, as I explained earlier, is impossible) for everything written, you can expect the software world to not move anywhere.
There aren't enough working hours in the world to do that.
Sensible people pick the battles that are important and focus on those: Some specific bit is taking too much CPU/RAM on Python? Write that bit as a C extension for Python, write the bits that aren't that critical in plain Python.