Charlie StrossJan 4, 2024
NO FUCK OFF GET AWAY FROM ME YOU CREEP— https://arstechnica.com/gadgets/2024/01/ai-comes-for-your-pcs-keyboard-as-microsoft-adds-dedicated-copilot-key/
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
Show threadCharlie StrossJan 4, 2024

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.

Show threadalex  now on shonk.phite.roJan 4, 2024
@cstross why not wayland
Show threadCharlie StrossJan 4, 2024
@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.)
Show threadLisPiJan 4, 2024
@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.
Show threadKirtai 🏳️‍⚧️Jan 5, 2024

@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.

Show threadLisPi
@kirtai @cstross @graphite The strong coupling between parts that should instead have defined interfaces is indeed a concern and annoyance.

I don't see what's so problematic in the kernel+systemd+wayland specifically in that before it was stil kernel+$thing+xorg. And basically always Xorg. Still a monoculture with its idiosyncracies.

The problem with systemd is that its interfaces and scope are ill-defined and it keeps sprawling, while what should happen instead is that a specific scope is considered, junction points are pre-determined, and then when it's done? It's done. Implement something else for interacting with those junction points if you need to.
Jan 5, 2024 at 12:58amWeb
Show threadKirtai 🏳️‍⚧️Jan 5, 2024

@lispi314 @graphite @cstross
My annoyance with the kernel/systemd/wayland thing is how they crowd out or force other choices.

e.g. systemd *requires* GNU libc, so if you want to use musl or another alternative libc, too bad.

Show threadLisPiJan 5, 2024
@kirtai @cstross @graphite Yeah, that's also a factor resulting from another problem.

Some parts of the C community have no notion of portability between compilers & core library implementations. Foundational interfaces/libraries should be portable, much like with compiler intrinsics, their extensions shouldn't be used directly. Compatibility libraries that paper over the differences should be used.

That systemd doesn't do that is a bug, plain and simple. It's a major code smell.