In a lot of modern work flows this is incompatible with the development pattern.

For example, at my job we have to roll a test release through CI that we then have to deploy to a test kubernetes cluster. You can’t even do that if the build is failing because of linting issues.

I recently was in the market for a new dishwasher.

I compared the EU eco labels (which are based on water and energy use).

Buying the worst possible eco label currently on the market, and comparing it against the best two:

• A label dishwashers cost almost twice as much (up to €400 more)
• ombined energy and water costs saved over the lifetime of the device (which I optimistically set for 10 years at three cycles a week) is less than €100 euros
• If you’re not into money, but more concerned about the planet, think about it this way: how much damage could €100 in energy and water spread over 10y really be causing our planet?
• These savings are only achieved if you use the most ecological program, which fails at it’s primary job, which is cleaning dishes.

If I could find a decent 90s model for which parts were still widely available, I’d buy that instead. I truly doubt that burning through these poorly made newer devices are sufficiently more ecological than just using a old machine for a longer time.

It’s not a bad idea and it is often done, just not in a browser/webapp context.

I have an Ryzen+Radeon Zephyrus G14 from 2022. It’s been great, battery life and performance wise. I run Linux but I’m sure Windows is no worse in this regard.

The only thing I can say is that I misjudged the 14" form factor and regret not getting a 16" model, and the mechanism for lifting the laptop of the table with the lid works great on a table but makes the laptop largely unusable on your lap in the couch.