Milpotel

> It's such a shame the fashion is the other way for so many web developers, largely the younger and less experienced ones.

I don’t care about what’s trendy, but using outdated, insecure browsers to surf the web is just plain stupid. Even more, expecting developers to waste time working around all the bugs in those old browsers is just insane. I do the opposite: as soon as a browser reaches EOL I drop the support. Don't encourage lazy admins and bad habits.

> None of them work on older browser

There are older browsers which still get security patches?

Why? Is it some form of Stockholm syndrome?

Same here. I don't use flatpaks, only a single electron app (Obsidian) and can't even name 5.

> If you just want something stable and boring, Linux is just not it.

What? I get the other arguments but I use Linux because it's stable and boring. I don't want the hassle of updates to Windows 8, 9, 10, 11 (or whatever is current now) or OS X updates breaking things ("Yay, they've removed another feature!").

I don't trust the battery usage screen. When I debloated my phone, battery life increased from 1,5 days to 5 days and those were all apps I don't use.

> GrapheneOS recommendation to this was to have fewer apps

Sounds reasonable. People tend to install way too many apps on their phones and than blame the phone about short battery life or too many notifications.

What's so hard? A developer finds a bug, fixes it, publishes a new release at some point, done. Versus someone else finds a bug, maybe opens a CVE, bug gets fixed, maintainer might notice it, backports patch and fixes (or breaks) the package. The latter CVE case is the rare case, hence all the crashes. E.g. Busybox is famous for that. They have a plethora of security issues documented in their bug tracker. Sometimes they even get fixed but most of them never get a CVE, issues stay open and you can guess if it's vulnerable or not (usually it is, don't use it).

Nope, it hasn't because developers fix bugs along the way without notifying package maintainers.

> It’s not horribly broken any more than your toaster is for not needing constant updates.

I don't know where this sense of "stable" in the community comes from. Software isn't perfect and gets fixed all the time. Yes, there are packages with different maintained stable branches that you can pin for your LTS distribution but this is by far the minority. For the other stuff you constantly have to work around missing features or existing bugs. E.g., why do I have to compile "jq" by myself just because the outdated package crashes on certain inputs?!

> Depending on the particular distro, only certain core packages are likely to get updates on LTS releases.

All LTS distros fix only some core packages sporadically as no one is able to back port all the patches esp. since most packages do not use CVEs and just fix bugs on the go. "Stable" for non-rolling distributions simply means "horribly broken and outdated".

Fascists torturing communists... seems familiar.

Options -> change projection helps a little bit.

Many years ago in Germany.