Antergo

You're missing the additional list mentioned later on, also includes Lenovo and some others

I understand you may be from a field where supporting software from the 70s is required, however someone is probably paying big bucks for that software as well. Replacing the software you work on might cost millions, replacing a thermostat costs 300 usd.

I would love to live in a world where software support lasts 70 years. But consumers don't look at software support, so it's not budgeted in the price, and thus doesn't happen in the consumer space. Getting 16 years in a consumer device is long.

In the field you're working, stability, longevity, and robustenes is probably a requirement, not a nice to have.

AA much hate this might be getting, they're offering discounts on a new product, and 16 years is a hell of a lifetime. Imagine having to support software written in c99 maybe even c89, with some homebrew UI full of bugs.

You can use wireless ADB, or try to set the battery limit to 80% and only set charging to only start below 30%. Wireless ADB settings can be found in the developer options. battery options don't always include the option to require battery level to drop below X% before charging starts again, and if it is, it is usually branded as battery saver feature or smth like that.

I drew the arrow one way, just because you want to invert the arrow doesn't mean it's correct 🤷

Thats not how economics works, if the cost of a product goes up one way or another, the price goes up, one way or another

I mean, the dilivery company will have to pay for the damages. It's just scratches, probably a conversation starter of someone sees it haha

Every car maker did, VW took the blame but the whole industry was lying

Paper and cutting boards come from the exact same trees. However when I tell you to use a cutting board instead of cutting on the table, somehow everybody knows that they shouldn't use paper

I can really appreciate the performance is (should) be the same, makes a lot of sense

Gtk 3->4 made a lot of internal changes, and at least some were related to making wayland work. Wayland "worked" in gtk3, however it was very much an afterthought, and half the toolkit was useless under wayland. Other changes are usually required for changes related to rendering, gtk4 had vulcan rendering which may require some breaking changes. Another thing is just general breaking changes that are good, sometimes you realise some decision was bad, and a new major release is just a way to make these.

From the end users perspective nothing much changes, it maybe looks a bit different, but not much besides that. But a vulcan renderer and being fully wayland compatible are major improvements that also improve the user experience, even if you don't notice directly.

It doesn't, it's just a "solution" to make cars "better" without fixing anything. But some people think that "if we just make cafs cars better" they will eventually become good