3 ms·

I'm personally not interested in MicroPython either, but... > the resulting solutions need an order of magnitude more resources to accomplish the same tasks wh

I'm personally not interested in MicroPython either, but... > the resulting solutions need an order of magnitude more resources to accomplish the same tasks when compared to writing an equivalent system in C. I mean, yeah... but that's true when you're writing Python code on a normal computer as well. It's not really an argument against writing Python except in cases where you're actually running into resource constraints. If you can get the resources you need in a microcontroller you can afford, and you prefer programming in Python... why not?

bemusedthrow75 3y ago
> 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.
- AzuraIsCool 3y ago
  Not sure why you got down voted. > it doesn't waste resources that other software could be using, because no other software is running. While this is interesting observation it is not always true. A lot of devices are low power, and depend on battery.
  - bemusedthrow75 3y ago
    Oh gosh. You are entirely right :-) If that is why I was downvoted then I'd go along with it for sure.

bemusedthrow75 3y ago

> 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.

AzuraIsCool 3y ago
Not sure why you got down voted. > it doesn't waste resources that other software could be using, because no other software is running. While this is interesting observation it is not always true. A lot of devices are low power, and depend on battery.
- bemusedthrow75 3y ago
  Oh gosh. You are entirely right :-) If that is why I was downvoted then I'd go along with it for sure.