it’s opt-in, per app. Meaning unless old apps are patched and recompiled, they will be inaccessible.

it means that you have to manually reposition every single window, every single time. for any and all apps, by design

you mean it doesn’t work when the device is turned off? weird! /s

by issues I mean breaking existing users’ workflow, possibly literally locking them out (I personally use a yubikey with my keepass db, for example).

There is a very simple solution he could have done: not rename the existing package. Just give his fork a new name. That’s it, everybody is happy.

So yes, he is the one causing issues. Because the issue isn’t in the features he removed, but by breaking the users’expectation that the package they installed yesterday, is the same one they’re updating today.

well it is that one person causing issues

when in need, cry out for mommy!

there is the keepassxc-cli command. And it also supports ssh keys with integration with ssh-agent. So yeah

one of the extensions has the description: “an easy flow to update passwords”

If that has to be an extension, then this sucks

markdown is standardized? I haven’t found two parsers that parse the same file the same for any but the most trivial documents

nah man, gotta be more specific. When those stuff work on every application.

A screen reader protocol for blind people that requires the app to be recompiled and opt-in to being accessible to accessibility tools, is not a replacement for one that worked for every application. Old apps will become impossible to use for some people with accessibility issues. Though wayland fanboys would tell you to shut up and be happy that a protocol exists, while failing to acknowledge that the protocol is literally removeding useless by design.

have you used android? As a dev, I mean

quit removeding saying that! I still get random flickering on the desktop and flickering in games on a 1080. X11 is the only thing that lets me actually play games onmhe thing

yes, if i combare kicad with blender, neither is broken because they have different features. But also, nobody is telling users that kicad’s days are over and it should be replaced by blender. If they did, and a user wanted to design a circuit board, the user is out of luck. The user is told that it is a replacement. From the user’s point of view it most definitely is not.

The probeem isn’t just that wayland doesn’t do everything x does. But that users are told that it will replace x, deal with it and quit complaining.

We have to keep in mind that the fact that we know what wayland is in the first place puts us squarely into the “technical user” category, not regular users. Regular users are the ones who don’t even know (nor should they have to care) what wayland even is

“that thing you used to do is now impossible to do consistently across different implementations, if at all. But it’s all ok, because we have decided it’s not our responsibility!”

That is not what users want to hear. From a user’s point of view, it is broken.

it’s pretty much just arch without systemd then. which is enough of a dealbreaker for me, as I think that systemd is the best thing to happen to linux since sliced bread.

mandrake was my first linux distro. I got it from a german magazine in 2004

cat isn’t the one writing to the drive there.

and arm do not manufacture chips. Usually tsmc or samsung do. The fact that chips exist is orthogonal to the argument of who ends up manufacturing them

i was replying to the point that all hardware is made by large corporations. That will not change, irrelevant of whether the isa is open source or not.

pretty hard to do computation on a pdf. which is what risc-v is. You need someone to design and build a chip according to what’s in those pdfs