I actually am opposed to bans on traditional incandescent bulbs but vastly prefer LEDs and have no desire to go back to them.
Using LEDs was a shock to me initially mostly because, as you point out, with traditional household incandescents there wasn't a whole lot of options. So suddenly when I had to pay attention to color profiles and so forth more carefully, I wasn't expecting it.
But I don't see that as a bad thing, I really love all the options, and the better precision in labeling color versus power versus brightness.
One problem I've noted, that others in the thread are pointing to, is that a lot of shoddy manufacturing has taken advantage of many of the claims of LED technology to push unacceptable products. One of my pet peeves is how I've suddenly seen fixtures with integrated bulbs take over lighting departments, poorly constructed and forcing you to remove the entire fixture rather than just the bulb, when it dies after a year, much earlier than promised. But I guess even there it's just moved me to more selective lighting stores where I can still buy better fixtures separately from the bulbs.
I do think there's something to be said about declines or fraud in lightbulb manufacturing quality compared to what is possible, but I see that as a scourge of our age and not something unique to LEDs. I have as much trouble finding a quality lightbulb as I do a quality pair of pants.
The one weakness of the Instant Pot is that most models won't go to 15psi and there is the odd recipe where a longer cooking time can't compensate. For example, there is a Modernist Cuisine recipe for pressure cooked root vegetables that uses a bit of baking soda to help bring a caramelized flavor to the party. Works great in a 15 psi cooker but is a disaster in an instant pot: the veggies just taste like baking soda. I suspect that stocks made in the Instant Pot might not be as good as well for similar reasons but haven't tried that yet.
Nah.. it was pretty easy to jump. Life is beautiful.
BTW, for anyone who is comfortable with RPNs, MacOS added the mode to their built-in calculator recently-ish. it's not terrible either. I've switched to it for my default experience. (even though nothing beats the HP 48g, as it's what I'm the most familiar with).
Also, on the article, really cool that someone added this on mobile. I love hearing about devs developing something that fills a niche and does so well. I feel like I'm out of ideas most days. Good for her!
Danger was bought by Microsoft, however, right around the time the NetBSD phone was going to market. AFAIK the tech didn't continue much past the Microsoft acquisition. (Source: worked at Danger on the NetBSD project, but left shortly before the Microsoft deal.)
I agree with "delay", but why do you say setup and loop are the worst imaginable way to write embedded software?
Because there's neither abstraction nor ways to combine things. Say you have a device that needs to do two things, and you look up some examples of how to do each thing. Each example is going to have its own loop() function--but how do you combine them? There's no notion of tasks or threads. There's no abstraction for device drivers. Arduino is a system that paints you straight into a corner.
[edit to add] Any reasonable software environment needs to provide three things, quoting "Structure and Interpretation of Computer Programs" here [1]:
* primitive expressions, which represent the simplest entities the language is concerned with,
* means of combination, by which compound elements are built from simpler ones, and
* means of abstraction, by which compound elements can be named and manipulated as units.
Arduino only provides the first.
[1]: https://mitpress.mit.edu/sites/default/files/sicp/full-text/...
It's not the highest of quality hash functions (see the SMHasher benchmarks), but it is fast. A great alternative is XXH3 (https://cyan4973.github.io/xxHash/), which has seen far more usage in practice.
Aside: when storing hashes, be sure to store the hash type as well so that you can change it later if needed, e.g. "xxh3-[hash value]". RFC-6920 also has things to say about storing hash types and values, although I haven't seen its format in common use.