(That is not to say that the FCC change will move the needle on the underlying issue of router security; as some of the ancestor comments have said, lax security practices are common industry-wide, irrespective of country of development/manufacture.)

The car saw this dude coming from way down the street, flying, and was like “yeah, better stop.” Probably saved the biker from serious injury, or worse. I wouldn't have seen him if I was driving.

Where'd you see they're exiting pro/flagship tier stuff? Everything I can find says they're continuing to hand-make their higher-end stuff in Germany. One such source: https://www.whathifi.com/headphones/100-year-old-headphone-b...

Glad to see them setting a great example here instead of letting these speakers become expensive paperweights.

I worry that we are edging closer and closer to a similar phenomenon with macOS as well. Apple seems intent on squandering every bit of stability and sanity that macOS used to represent. Maybe now that Alan Dye is gone, we will at least see the abomination that is Liquid Glass fixed…somehow.

For boilerplate stuff like generating tests against a well-defined API, in a compiled language, maybe 2-3x. Far less in languages and frameworks like Ruby/Rails where the distance between generating the code and figuring out if it’s even valid or not is large.

Mechanical refactors that are hard to express via e.g. regex but easy in natural language: maybe 5x.

HTML and CSS, where I know exactly what I want and can clearly articulate it: 2-5x.

For anything architecture-y, off the beaten path, or where generating a substantial amount of code is required: near 0%. Often in the negatives.