The stuff Hacker News actually recommends.

Boards and maker kit

Espressif ESP32 vs Espressif ESP8266

Hacker News owners slightly favor the Espressif ESP32.

Espressif ESP32Espressif ESP8266
Owners with an opinion24952
Positive verdicts82% of 20285% of 40
Positive/negative since 202479/2114/2
Happy after 3+ years23
Longest happy owner5 yrs6 yrs
Praised forperformance and valuereliability and ease of use
Criticized forreliability and ease of useperformance
Newest comment

Updated

What owners wrote about both

Espressif ESP32: Doesn’t like itEspressif ESP8266: Likes it
Nice write-up and a nice outcome, but speaking as a reasonably successful home/amateur woodworker, this is very over-thought and over-engineered. I say this not to criticise the creator as I appreciate that they are new to this, but to help others considering such pursuits. Some constructive feedback: * There is no need for the extruded aluminium frame - some cheap wood would have sufficed as a frame * The CNC'd hanging brackets are totally unnecessary - a couple of holes, one either side, with a keyhole hanger over each would have sufficed * The balancing and 3d-printed endcaps is unnecessary assuming you've got reasonably well-placed hangers * The fancy ESP32 board could have been replaced by a commodity ESP8266. (You could get rid of the ESP altogther and just buy pre-wired LED strips, but then you lose the opportunity to program nice lighting effects.) As a result, the bill of materials is multiples of what is could have been. I estimate that you could replicate this in a single weekend for ~80-85 EUR (15 EUR countertop, 10 EUR wooden frame, 5-10 EUR plexiglass, 40 EUR LEDs + PSU, 5 EUR ESP8266, 1 EUR for two keyhole hangers) assuming you have a few screws and some wood glue available, plus whatever the cost of the markerspace is. Everything could be sourced from your local DIY store, plus an order from Aliexpress for the electrical components.
Espressif ESP32: Doesn’t like itEspressif ESP8266: Likes it
I’ve used both, and I’m actually more productive with the ESP8266 because it is so limited - I can usually squeeze in a minimal implementation of one or two things and that’s it. With the ESP32 there’s always other options, and it means I have to make more decisions, so I end up getting bogged down in irrelevant stuff
Espressif ESP32: Recommends itEspressif ESP8266: Doesn’t like it
I'd recommend staying away from the 8266s at this point. The chip is EoL and the ESP32 offers double the speed, more than double the IO pins, and bluetooth. The 8266 is limiting with its single ADC pin, and single hardware serial and inability to define other pins for I2C/SPI. I started with the 8266s thinking I wouldn't need the extra features, and most of my applications don't need it, but the few times I needed to work around the limitations weren't worth the aggravation to save $1-2.
Espressif ESP32: Likes itEspressif ESP8266: Doesn’t like it
AFAIK, the WiFi isn't all that intensive, but requires special considerations. With the ESP8266, you had to be careful to call yield() every few seconds, or the WiFi would hang. So it made it harder to write processor intensive tasks. The dual core of the ESP32 did away with that.
Espressif ESP32: Likes itEspressif ESP8266: Doesn’t like it
Yea, I would assume a large percentage of startups that use Wi-Fi adopt esp32 since it's much easier and cheaper to get up and running compared to the competition. More established companies don't need to adopt it but I assume it will change as time goes on. Kind of like how Webview or React Native was scoffed at in the beginning but now it's pretty commonplace even at large companies. Or like when Twilio IPO'ed it had to start targeting larger firms by building out their sales department because at the time it was mainly a hobbyist platform. Esp8266 doesn't have Flash Encryption, or Secure Boot, whereas Esp32 does and Espressifs SDK ESP-IDF is maturing. So it's definitely production grade mcu. Nordic just announced its Espressif Competitor which will be interesting but haven't released the cost yet. Espressif seems to be throwing things at the wall to see what sticks (S2, S3, C6, H2, etc). I think their IPO definitely helped them raise more cash to do more things. Also, Espressif just had a virtual conference with a bunch of talks if you're interested: https://www.youtube.com/@EspressifSystems
Espressif ESP32: Doesn’t like itEspressif ESP8266: Likes it
I built one of these before, it was lots of fun to learn how to apply PID to motors. I started with an ESP8266, which worked great, then an ESP32 which hung when wifi and the encoder read happened at the same time, and then ended up porting everything to Python running on a raspberry pi. It's definitely impressive to see a non-realtime computer doing realtime-enough to keep itself balanced. From what I can tell, if you get it working well, you can "drive" around, including turns, with just simple mods to the control settings.
Espressif ESP32: Likes itEspressif ESP8266: Doesn’t like it
If you must use ESP8266 for some reason, then completely agreed. ESP8266 is obsolete now though, there are far more capable ESP32 variants, some of them specifically designed and marketed to replace the 8266 and to make transition as easily as possible. Not to mention the benefits of a now quite mature ESP-IDF SDK. Arduino is a great onramp to embedded, but it really needs an offramp.
Switched from the Espressif ESP8266 to the Espressif ESP32Espressif ESP32: Likes it
Thanks for that, I was going to point out its the public key, and cert validation that is going to be the problem more than the actual data encryption. I had this problem a couple years back with a project on a esp8266, which was taking on the order of 5 seconds at 160Mhz to setup a TLS connection. And it got worse with longer key lengths, and validating a cert chain. So, ballpark it probably takes multiple minutes, and probably consumes most of the RAM for the intermediate steps with longer keys. OTOH, I switched to an ESP32 because it has RSA offload, and something like that could be attached to an apple ][ fairly easily, to provide a connection offload accelerator.
Switched from the Espressif ESP8266 to the Espressif ESP32Espressif ESP32: Likes it
I moved to the ESP32-C3 after using the 8266 for a while, and the C3 is a great chip. It's small, power-efficient, has bluetooth and wifi onboard. It's got USB pins so you can connect it up to USB and program it, and connect to Serial (no USB device though, sadly) It's got a really full feature set, and a really strong Arduino community to boot. Probably best of all, it's inexpensive and in-stock. While so many other chips have been unavailable, the C3 can be had just about anywhere at very reasonable prices. And if the chip isn't quite your thing, the modules available are _excellent_.
Switched from the Espressif ESP8266 to the Espressif ESP32Espressif ESP32: Likes it
I had been using the 8266 in a personal project and this past year moved it over to the c3. I was excited to use a RISCV chip. That doesn’t really make a difference in the end, but I’m really pleased with it, especially after I stopped fighting the Arduino IDE and moved to PlatformIO - I had been reluctant to do so, but it’s really matured. Hunting around for answers about how the c3 works can be rough. There’s still not a lot of info about its quirks written up yet. But once you get into it, it’s great. And quite affordable.
Switched from the Espressif ESP8266 to the Espressif ESP32Espressif ESP32: Likes it
The analog thermostat of my fridge broke, a replacement thermostat didn't work reliably. So around two or three years ago I replaced it with an ESP2866, a relay and an ds18b20. It worked great, except that the logic was outside the fridge on a home server, it was a a Python script which also logged the data into InfluxDB. The issue then was that sometimes when the server was down, the fridge stayed on or off. Last week I started to reorganize my WiFi, which devices access which APs, and since then it had constant disconnects, so I decided to finally fix this issue. Now it's an ESP32 with the logic in code which now only posts to the server for InfluxDB-logging and is upgradeable via OTA and parameters can be set via http://fridge.home/esp?data= {"set-fridge": {"max":7,"min":5.5... } It's been fun doing this and extended the lifetime of the fridge for a couple of years. But I also would never buy an internet connected fridge or any type of appliance, unless it could be flashed with some OSS to make it cloud-free.
Espressif ESP32: Likes itEspressif ESP8266: Likes it
I use both as well and see no reason to pick only one or the other. The USB stick hubs are very cheap and Home Assistant does all the heavy lifting seamlessly. Having both gives me pretty much unlimited flexibility. For devices I usually pick whatever standard has the device I want at a more reasonable price or is on sale. So far I've yet to run into a scenario where I wish I had chosen the other standard for a specific device. I also have a ton of devices on WiFi via Esphome on both esp8266 & esp32. Fantastic project, years of them running completely trouble free.
Espressif ESP32: Doesn’t like itEspressif ESP8266: Doesn’t like it
The ESP32 and ESP8266 are significantly more complex and come with a bunch of downsides that make an already difficult venture into the "hardware land" even more so. Watchdog timeout or some other exception, you'll get a stacktrace that requires a fragile Java piece of software to decode, and it only does that to some extent. It's seriously not pleasant. In my anecdotal experience the ESPs are also not as robust against mistreatment as the AVRs are. According to the datasheet they shouldn't survive as much as they seem to. So while the hardware might be better, and there is always better hardware out there, it's sometimes worth to avoid the complexity.
Espressif ESP32: NeutralEspressif ESP8266: Neutral
This depends - my projects are usually small and spontaneous, my attention span is short, and not having parts to at least start means the project is dead right there. I do most of my stuff on microcontroller boards though, and I keep a small stock (maybe $30 worth of ESP32, ESP8266, and something-that-can-pretend-to-be-a-USB-keyboard dev boards).
Espressif ESP32: NeutralEspressif ESP8266: Neutral
I currently use OSC on ESP32 and ESP8266 microcontrollers to build electromechanical instruments and controllers, but I'm considering switching to this O2 protocol to make my components more open to rearrangement. Just sharing this and curious if anyone else is implementing O2 into their projects.
Espressif ESP32: Likes itEspressif ESP8266: Likes it
The micropython support is interesting; most activity is on circuitpython but micropython supports older chips (the ESP8266 and the very first OG original ESP32 are two examples of hardware I have on my desk). They both work, its just the odds are vastly higher of finding a library for circuit rather than micro and there's probably ten circuit python users for every micropython user. Although I "have to" use both. I thought that was interesting to throw in support of the less popular but wider range of hardware choice for microcontroller python and not even mention the other more popular option. (Side note what's up with UF2 firmware upgrades not working on ESP32-S2 chips, works on everything else, must be an interesting story behind that)
Espressif ESP32: Likes itEspressif ESP8266: Likes it
I have quite a few running at home: Irrigation system driving valves through H-bridges Relays driving ceiling fans IR blasters (actually an additional feature of the previous relay drivers) PIR sensors Expansion of a smoke detector to send a push notification to my mobile Garage door opener Security cameras (Quite a few are ESP8266 rather than 32's, depending on power and i/o lines required)
Espressif ESP32: NeutralEspressif ESP8266: Neutral
Instead of trying to directly integrate for example Prolog and Python I set up services in whatever language/hardware and communicate between then using JSON messages transported via MQTT. With this method I've got Docker containers running Java, Python, and Prolog code interoperating with ESP8266 and ESP32 devices I programmed in C++ and anyone can talk to anyone. I also wrote a Java server that interfaces with an Insteon gateway so my little MQTT cluster can respond to devices turning on/off or send a MQTT message to control a device. The pieces don't know or care what language the other pieces are written in. On the Prolog side of things with not that much framework code here is a trivial example: message(['Smarthome','Notify','brain','ping'],_):- publish(['Smarthome', 'Notify', 'brain', 'ping_response']). This code receives a MQTT message with a topic of Smarthome/Notify/brain/ping ignoring the message body and then publishes a return message on topic Smarthome/Notify/brain/ping_response I even have a container that runs nothing but cron with a mqtt client installed that sends mqtt messages at various times of the day and all Prolog has to do is subscribe to those topics and handle those messages.