I would doubt this is the case, Orca Slicer exists since 2022 and is very popular. This is not a "somebody just noticed a thing" situation.

69 had two things going on for it, the war was not news and on its first signs of being scalled back, Nixon had announced a retraction of force for September (but ended up extending the whole thing to 75) and this would be the first moon landing, there was nothing like it.

From 1969 to today, we're waaaaay better. But from 6 months ago there is clearly an elephant in the room taking a lot of attention.

Lots of developers don't even say they are JS devs but React devs or something. This is normal given that the bandwidth and power of targets are so large nowadays. Software is like a gas, it will fill all the space you can give it since there is no reason to optimize anything if it runs ok.

I've spent countless hours optimising javascript and css to work across devices that were slow and outdated but still relevant (IE7, 8 and 9 were rough years). Cleverness breads in restrictive environments where you want to get the most out of it. Modern computers are so large that its hard for you to hit the walls when doing normal work.

Security gets outsourced to audited layers and Ai does the stupid boring jobs of gluing them together. Some developers become more specialised and niche, some pivot to product, some pivot to other areas.

There are plenty of people who joined software for the payout and hate it. Plenty of people who grown to hate it over time.

I've been enjoying using it to figure out toy projects but paying an API and depending on a service to code is very sour. I really hope hardware specialises and local models become good enough. Gate keeping development on centralised services would be a loss for everyone and ripe for dystopian outcomes.

Wave was fine, I liked it for the short time it lived and I am happy that google docs carry some of its collaboration legacy.

The insistence on choosing who shows up where by algorithm and "intelligence" made it impossible to create muscle memory, you had to look and/or search every time.

Other than that, pretty fun!

It's mostly my photos

One of the FAQ questions is: Will an American company soon be able to view my data?

This tells a lot about US street cred atm. This was added to the website not because of niche political activism but by a sizeable concern of the population.

Im confused by this line, standards are meant to promote compatibility, not design. They're a way to, well... standardise processes and things. Its almost a given that you'll have to compromise on design to be able to include enough variance to appease the majority of use cases. It is also desirable, I think, of a standard to not give in to edge cases and niche uses and stay as simple as it can to the general use. There will be other niche standards for those and that is a good thing.

Standards survive and die for the same reason they're created, they make things cheaper, faster and easier. Once they fail at those, they give in to newer entrants. Physical standards can also make things safer, but safety must be enforced as people often are bad at judging risk and prefer the other features to a fault.

Second line: You presumed that out of feeling? I did not write anything hinting at that.