I've seen someone used the entire raspberry pi zero(dual core 1Ghz cpu with hundreds of MB ram) just to do some http request and display on a simple LCD, with python no less. All can be done with a simple esp32.
But hey, as long as it works, right ?
I've seen someone used the entire raspberry pi zero(dual core 1Ghz cpu with hundreds of MB ram) just to do some http request and display on a simple LCD, with python no less. All can be done with a simple esp32.
But hey, as long as it works, right ?
1. It’s so much easier using RPis for that work. It can be done with no soldering at all and there are tons of easy to use libraries. Not having to solder is a huge plus IMO and I have a workstation with iron, hot plate, air gun, etc. ready and waiting.
2. Why hate on doing it Python? Even ESP32 embedded development ecosystem treats Python well with CircuitPython and MicroPython.
3. At least they are making something!
4. Even a simple ESP32 is overkill for what you described, so why are you hating on people using an RPi when your suggestion is just as laughable when taking your hardcore embedded stance?
As someone who has been working on embedded work since RadioShack was a good source of components - let’s not gatekeep makers.
2: What i mean is the main reason they use Rpi because it can run Python(at least easy, this was before CP/MP mature). If they had spent some effort in C, they can get away with not using rpi.
3: I agree with that, but i really do wish they step out of their comfort zone a little more discovering what is possible.
4: I dont think esp32 is overkill, it's the cheapest and easy to acquire wifi MCU, if you have better suggestion i would like to learn, there is esp8266, but the cost different is not that much.