> If you can get the resources you need in a microcontroller you can afford, and you prefer programming in Python... why not?
Particularly when you consider that the "bloat" here has no secondary side-effects: it doesn't waste resources that other software could be using, because no other software is running.
I am a long-time web developer who has always intellectually understood the interest in microcontrollers but never had much of the need. I do now.
I'm not even a fan of Python but MicroPython is a surprisingly productive development experience and I've learned a lot in a very short time with a Pico W.
I will probably use TinyGo at some point in the future, particularly as I try to use smaller devices, and I'm not averse to porting to C, but I really rate the MicroPython ecosystem highly in terms of actual coverage, though mainly just the intent of it, which is unimpeachable IMO.
Particularly when you consider that the "bloat" here has no secondary side-effects: it doesn't waste resources that other software could be using, because no other software is running.
I am a long-time web developer who has always intellectually understood the interest in microcontrollers but never had much of the need. I do now.
I'm not even a fan of Python but MicroPython is a surprisingly productive development experience and I've learned a lot in a very short time with a Pico W.
I will probably use TinyGo at some point in the future, particularly as I try to use smaller devices, and I'm not averse to porting to C, but I really rate the MicroPython ecosystem highly in terms of actual coverage, though mainly just the intent of it, which is unimpeachable IMO.