Tearing and hidpi is why I left Linux for Windows between 2012 ans 2022. Once wayland was good enough I returned. Tearing is awful, and should be opt in (which wayland provides), not opt out.

Conversely, I much prefer lowest latency at the cost tearing; when I'm forced to use windows I generally disabled the compositor there too whenever i could (I certainly don't use one under Linux and that's one of my reasons for being there). I find macOS unuseable, even on brand new top-end mac studios the input lag and slow reaction of the OS to... any user input, is frightening when you're used to your computer reacting instantly.

No, that's every bit of software out there. Dynamic linking really does cause that problem even though allegedly it has security benefits as the vendor is able to patch software vulnerabilities.

NixOS actually is a bit better in this respect since most things are statically linked. The only thing is that glibc is not because it specifically requires being dynamically linked.

This issue also applies to macOS with their Dylibs and also Windows with their DLLs. So saying that this is an issue with Linux is a bit disingenuous.

Until everybody standardizes on one singular executable format that doesn't ever change, this will forever be an issue.

I know you are trying to make a point about complexity, but that is literally what NixOS allows for.

There is always the analog hole. Even HDCP can be worked around. Even if they do manage to stop all computers from doing direct bit copies, there are still old things such as Kinescopes which they used to use to broadcast television from film. There of course is a quality loss, but that's kind of irrelevant to the point.

When you benchmarked Postgres did you disable WAL for the cache table? That may minimize the difference.

Unlogged table, yes. 1ms is more than fast enough so I didn't bother to look further.

Golang at least gives you the option to easily vendor-ize packages to your local repository. Given what has happened here, maybe we should start doing this more!

This doesn't really help you. I assume Go records the sha1 hash of the commit it grabs, so it doesn't really matter if you vendor it, or download it every time.

The problem comes when you want to upgrade your dependencies. How do you know that they are trustworthy on first use?

Go uses the hash of the source code, not the commit ID. So there's no difference between vendoring and using the central repo.

npm has always downloaded to the current directory.

That isn't the same as vendor-izing unless you are committing node_modules to your VCS, which would be insane.

Absolute lies, where I live it is one party consent. I can still record with another device on speakerphone.

I think the person you were replying to might have intended sarcasm.

Yes this was sarcastic, I should have put a /s

I also live in a one party consent state.

You could not be more wrong. Kde is the last vestige of interfaces are powerful, pretty, and that don't their users like idiots.

You have your GNOME and simmilar ilk, be content with that and leave KDE alone.

Their anti-DRM stance is arguably their only compelling feature as opposed to just buying steam.

I remember the old game launcher that was called Desura?, which a lot of those third-party keys sites would sell keys for, and it's no longer around. So one of the main concerns with these online platforms is them disappearing and losing all your stuff.

Quite frankly, I am happy that GOG exists for this niche. It would be less "sabotaging" if consumers would actually vote in their own interests. However, this has been shown time and time again to never happen, sadly.

I would assert that iChat evolved into messages. There are a few more icons that could be added in that category.

I agree, I also would argue that this counts as an earlier incarnation of the System Settings icon: https://i.imgur.com/cqtpKhI.png

It most definitely did.