> the resulting solutions need an order of magnitude more resources to accomplish the same tasks
Okay, and? It's 2024, even a $2.50 toy devboard had multi-megabit flash & ram. I really don't care if my code takes up 10k or 100k. If Python makes it easier to develop and eliminates entire categories of vulnerabilities in the process, it doesn't make any sense to use bare C instead. I paid for the entire chip, why shouldn't I use the entire chip?
C is fine if you have to do high-speed bitbanging or have to squeeze every last byte out of a chip, but for most applications that's simply not the case anymore. A decent fraction of embedded systems is absolutely trivial on today's hardware. It's time we start treating them like the mini-computers they are, because remaining in a 2000s mindset is going to result in a lot of compromised network-connected devices due to some developer fat-fingering a buffer size.
Okay, and? It's 2024, even a $2.50 toy devboard had multi-megabit flash & ram. I really don't care if my code takes up 10k or 100k. If Python makes it easier to develop and eliminates entire categories of vulnerabilities in the process, it doesn't make any sense to use bare C instead. I paid for the entire chip, why shouldn't I use the entire chip?
C is fine if you have to do high-speed bitbanging or have to squeeze every last byte out of a chip, but for most applications that's simply not the case anymore. A decent fraction of embedded systems is absolutely trivial on today's hardware. It's time we start treating them like the mini-computers they are, because remaining in a 2000s mindset is going to result in a lot of compromised network-connected devices due to some developer fat-fingering a buffer size.