Efficient software starts with choosing an efficient tool for t he job. it seems like more and more cli / system /utilities software is written in nodejs, react, python or ruby. While these languages are good for fast developer experience they force the user to manage the headache of dependencies, and insert the interpreter on top of the cpu. I do hope with the increased spread of AI that we'll start to see people choose more appropriate (compiled) languages for building tooling. Interpreted languages are great imo for scripting or prototyping but should be avoided for anything that will become a larger long lived application. Eg why the heck did Microsoft decide to write the start menu in Windows 11 in react?!?

What we should do is cut Saturday delivery, put up prices on businesses sending Local postal customer flyers that are not targeted and just the physical equivalent of spam. Then over time reduce the USPS costs and look at other revenue streams. Honestly I'd pay an annual fee to have no local postal customer letters delivered. If you look into how little these business pay to get inserted into everyone's mail it's actually very small. The citizens are the ones paying crazy postal costs to subsidise the businesses low rates. Companies like spectrum who spam paper (or in this case plastic) advertising need to go under. I left spectrum (only choice at the time) for google fiber on July 15, since then I've got weekly plastic advertising trying to get me back. People don't want this. Give people a choice on what goes into their letterbox. Personally I've used all the techniques seen on Reddit to reduce my postal mail. I now only get one or two items a week, have informed digest (which is awesome) and only clear the box weekly unless something important is coming in.

If you're going to vibe code apps - why not vibe code them in an efficient compiled language.

Why not also put the recycling code into the QR code too.

I guess not very much is going on in the state of Queensland.....

What could be done is conversion to a new instruction set, while using the invalid instruction interrupt to emulate legacy instructions. This would be a good way to those extra instructions out of the core. While software is not as efficient, and would be very slow, it would allow the progression over to the new instruction set very easily. Windows has the ability to have drivers for the CPU, so this could simply be built into there. Linux could be recompiled - which fixes a lot of the problems. Clearly running 16bit segmented code would be very tricky, and would run abysmally slow, but it would still run, until updates were available.