Microsoft is adding a new key to PC keyboards for the first time since 1994

Copilot key will eventually be required in new PC keyboards, though not yet.

Ars Technica

Seriously, if Apple copy Microsoft with a stunt like this, that'd be my cue to buy a Framework laptop and switch 100% to Linux for work.

(Which would be enormously painful as Scrivener isn't supported on Linux and it's been my work platform for the past 15 years.)

NB: only distributions with X.org ranther than Wayland and sysv init instead of systemd need apply.

@cstross why not wayland
@graphite Because Wayland AIUI isn't compatible with all previous X apps. And I want compatability. (Also, it's needless change for change's sake, just like systemd.)
@cstross @graphite > (Also, it's needless change for change's sake, just like systemd.)
I'd disagree on that aspect.

X11 has some definite limitations (and resulting problems) that cannot be fixed without making a new protocol version (not all of the problems are implementation-specific Xorg problems), and I have little hopes for any such new revision (which would have to /remove/ from the older ones, not just add). Using another protocol entirely sidesteps that (which has its own issues).

Similarly, sysvinit has a bunch of limitations that are annoying and effectively require a separate daemon manager if you want something halfway sensible (some PID 2 to its PID 1, I suppose).

(I also profoundly dislike the use of shellscript for anything that has to be reliable and isn't absolutely trivial.)

There are also problems with both of the newer options though, I'll grant that without reserve.

@lispi314 @graphite @cstross
I hate how they both seem to be forced on people while metastasising to envelop everything they can.

I wonder how long it'll be until mainstream linux distros are Linux kernel+systemd+wayland plus a few apps and nothing else.

@kirtai @lispi314 @graphite Same. The whole point of the UNIX/Linux philosophy was small, focussed tools that did one thing and did it well and could be glued together to build larger systems. The big monolithic approach embodied by systemd and wayland messes up this approach and makes the entire system harder to understand.
@cstross @graphite @kirtai So systemd should've been implemented as such a system on top of and relying on the other pre-existing init systems?

@lispi314 @graphite @cstross
iirc it was originally touted as a better init system and it should have stuck with that.

A better init system replacing weaker init systems is perfectly fine.

An init system trying to control the whole of userspace is not on. Those should have been separate, modular projects