There's all kinds of fun things that could be done with the franchise. An isekai where an Otaku gets reborn as Shinji and tries to do it right would be great.

In insurance you expect to come out behind in the average case, unless you're an insurance company.

If you don't need ipv6, best just to turn it off and forget about it.

I only read the Book of Atrus and it's worth a read. Can't vouch for any others tho

I don't like code reviews. If need be I might try to bs my way (paychecks come quicker than permission to fire) into a coding job and those would be a showstopper.

Ipv6 is a lot like a bios update - best avoided unless absolutely necessary. Potential mess with no upsides for end users.

And by that analogy, the previous BIOS version was released in 1981, and modern networking is hamstrung by its design which assumed "4 billion addresses ought to be enough for anybody" and that it needed to be manageable by an 8-bit OS with 64KB of RAM.

IPv4 is a brilliant protocol for having been published 43 years ago. There aren't a whole lot of technologies that old still widely used. I mean, I'm glad my NVMe drive doesn't have to shove bits through an ST412 interface.

While I had an "ST412 reference" on my bingo card yesterday morning, sadly I do not have it today. Opportunity lost.

> And by that analogy, the previous BIOS version was released in 1981, and modern networking is hamstrung by its design which assumed "4 billion addresses ought to be enough for anybody" and that it needed to be manageable by an 8-bit OS with 64KB of RAM.

I'm not sure if it makes the analogy better or worse, but this is what happened; BIOS was born in ~1981 (I think), had severe shortcomings that were partially mitigated over time but you can only mitigate so much, UEFI is a better replacement, BIOS->UEFI was a somewhat rocky migration, that migration was made worse by extra stuff getting bundled in (secure boot), and this led to a significant chunk of the population deliberately avoiding it at least for a while. The only real difference is that UEFI has long since become standard, while IPv6 is still fighting for adoption.

Fighting for adoption? The majority of Internet traffic is now IPv6 and we're almost starting to see eyeball networks without any IPv4 at all, so I hope your boss is aware you're blocking potential customers from visiting your website.

I really wanted to disagree with you but sadly that's how it was treated in secure environments a few years ago: "ipv6.disable=1". Everything that's not in needed would be disabled. Nobody wanted to be the first to "need it" and learn all that stuff, if it works with ipv4, stick with it.

Sure, one can figure out the split DNS, tunneling/no tunneling, DHCPv6, multiple addresses per interface, additional filtering rules, or just you know "ipv6.disable=1" and worry about in a few more years perhaps.

I suspect you haven't read the errata sheets for any modern EFI or even worse BMC? There is so much buggy crap in there that users are likely to run into that patching your firmware is a good idea just for stability and performance before you even consider integrity and privacy.

A useful gizmo but bang for your buck seems esp32 is the way to go

Biggest advantage of the ESP32 for me is that it can connect to WiFi networks with enterprise encryption with X.509 certificates. ESP8266 doesn't have the CPU horsepower to manage this.

The other big advantage is nonvolatile storage. The ESP32 can store the state of modules between restarts.

Every ESP8266 module I've ever used had a chunk of flash memory you could use for persistent storage that survived reboots/poweroff too. It's used to store WiFi credentials in a lot of frameworks, but you can stick other data in there. I guess it's not integrated into the chip, but don't most people use the integrated modules even in custom designs? All mine have.

Also IIRC it's not as well known, but the RTC also has a very tiny amount of memory you can use to pass state between deep sleep cycles. That one won't survive a power loss, but it's handy when sleeping and doesn't wear out like the flash memory.

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

ESPHome completely solves that for me.

The ESP32 line is the natural progression. Specifically the ESP32-C3 is the successor to the 8266.

If you're looking for a "successor" for the ESP8266, then it's clearly the ESP8684, part of the C2 line - even Espressif says so.

The ESP32-C is a RISC-V, unlike the others.

All the new ESP32 parts are RISC-V

Isn't the C3 the only one so far?

ESP32-C2, ESP32-C5, ESP32-C6, ESP32-H2, ESP32-H4 and ESP32-P4 are also RISC-V. Xtensa are ESP8266, ESP32, ESP32-S2 and ESP32-S3.

i reach for an esp8266 for the same reasons i try to design a 2 layer pcb instead of 4 layer: the challenge

and maybe just maybe if i have to make a thousand, i'll be ahead of the game

This guide is from 2017, before the ESP32 essentially took over.

It totally depends on the usecase, but I find that esp32 is so powerful, it's not power efficient. Al lot of IoT application run on batteries with a single task usually, and this where ESP8266 shines.

The ESP32 has series tailored for different purposes: https://www.espressif.com/en/products/socs (eg. the ESP32-H is for low-powered applications). I don't know how it fares against the ESP8266 in power consumption but as a hobbyist I would pick an appropriate ESP32-XX first and only look at alternatives if it's really lacking.

See also: https://products.espressif.com/#/product-comparison

It's almost problematic how many variants there are these days. I'm sure they all have their particular application but I sure don't know the difference anymore without spending a lot of time comparing. I feel like a few years ago you just went for an Esp8266 with x amount of flash. I thought the only difference was that and the form factor, but I might just have been oblivious of all variants back then.

I used to work for an engineering services company, and by default, our quotes would include a minimum of 40 hours just for finding and sourcing appropriate components.

Even for an experienced EE, it can be ridiculously time consuming. And it's one of those "hidden tasks" that has to be done but is rarely explicitly accounted for.

I mean, if it's for a task where I know my program will fit in 512K flash and 80K ram, then an ESP8266 is still cheaper. One of those is powering my DIY thermostat right now :)

I have to imagine that in most hobby (as in, one off) use cases the $1-$2 difference makes no real difference.

And at one point (years ago) I was able to buy ESP32s for practically the same price on Aliexpress.

Space and power savings shouldn't be discounted either. Especially if you're going to run it off a battery ;)

Any resources on how you made your diy thermostat? :)

If you've done any basic electronics before it would be relatively straightforward. I didn't follow any specific guides, just spent a lot of time reading the datasheets for components that sounded like they might work. My ESP8266 is connected to a GPIO expansion board from Adafruit over I²C, which controls 3 TRIACs through TRIAC opto-isolators. HVAC control wires use 24VAC so TRIACs are the silent option for switching, although relays would have probably worked just as well. After that I just programmed the ESP8266 in Arduino to listen to the MQTT broker on my network to send the values from its temperature probe (also an I²C board from Adafruit) and receive commands. It also has a basic thermostat mode programmed in if it stops receiving commands for too long.

Unfortunately it relies on an outdated GCC 5 toolchain that will never get an update

You click the filename twice to rename. More efficient than two clicks and a menu perusal.

You could also hit F2, but thats not the point here. The point is that a command that is used a lot is buried in 2 layers of menus.

I find it ironic that people, like the parent poster, who are actually trying to be helpful and informative are being downvoted for it.

Windows is an adequate operating system if one bothers to learn to use it properly.

The downvoters are most likely the same marketers posting this trash on HN. If there's help in the comments, people won't click on the ad trap they've posted here.

Disagree. They gave up a legitimate moral claim when they posted whatever on the public facing internet.

i think you're misundersatnding what it is that does not work here

What? This is about HDMI being a licensed connector owned by the HDMI forum. You need to pay them a fee if you want the HDMI OUT or IN inside your electronics