Amikke @Amikke@qoto.org

@robbie assuming a specific definition of "works". Electron UIs tend to be unstable and break constantly, lag and freeze on weaker machines, not to mention consuming ridiculous amounts of resources even when they don't and integrating with the rest of the desktop about as well as a website. Cause y'know…

@nixCraft

@pwm @mw1cgg it's the morally highest ground to take, but usually it's not enough to even save everyone that wants to not allow bad treatment from said treatment. You get lost in the crowd of people ignorant, spineless or desperate and lose quality of life for no noticeable positive effect.

I don't like resorting to prohibiting things, but sometimes it just results in effectively the same outcome if everyone suffering grew a spine and engaged in boycott together anyway, but without requiring that to take place. (It generally never does.)

Would I want my gov to take away existing workers' rights so that workers fight for them themselves? I'd have to be insane. We know how it'd end.

@pwm @mw1cgg some years ago I'd agree, but you probably know as well as I now do that as long as it's not prohibited, the majority of people that don't know enough or don't care enough will allow it and as such dictate the market reality to the minority that does. It's happened with privacy, it's happened with owning your music/games, it's happened with intrusive advertising, it's happened with virtually every aspect of workers' rights and it will keep happening.

@mw1cgg honestly baffling that's legal in the USA at all. Try that in an EU country and whatever local branch of the government enforces workers' rights will happily explain to you how much you need to fuck off. Not to mention that if you get away with it and try to enforce it, you'll be laughed out of court, likely also starting a separate case of breaking employment laws.

Employers borrow a portion of your time, not take ownership of your life. Stuff like this should never happen in a country that claims to be civilised.

Javascript is an excellent language to present language design problems, because
1. it's widely known
and
2. if something is possible to fuck up, there's a good chance js fucked it up.

@icedquinn @SuperDicq smart. I wonder if there's already a universal enough utility that would only have to have the QR generation added.

@icedquinn @SuperDicq oh I guess with the code you would have the benefits of both a fancy screenshot and computer-readable text.

@icedquinn @SuperDicq I don't really see a use for the QR code that isn't fulfilled by just copying the stuff to clipboard or taking a screenshot, but I guess it would be cool.

Also TIL that the KDE clipboard utility has a "generate QR code" option. Looks like there's no option to copy that to clipboard though lol, and even if there was it's ofc not as straightforward as having it be generated by the info tool directly.

@icedquinn @SuperDicq basically the system info tool that DEs often have by default, but with a QR code generator?

@OpenComputeDesign @Linux_in_a_Bit the latter usually don't actually pass. Their attempts to pass them are pretty damn annoying though, not gonna lie.

@jgillich @galdor especially the newer version where a lot of the bizarre gotchas were cut out. Not that many parsers support it lol

But besides that I often use YAML and recently had to quote "no" in the list of nordic countries. Funny stupid gotcha but easy to remember, beats quoting everything including identifiers in JSON.

@progo something like that xD

@progo I know, but for us in all of the other countries that use gregorian calendar it is 9/11 so we might as well post related memes.

@bersl2 Sure. But with the *nix focus on modularity instead of a giant overarching server, the thing we'd end up with would be wayland with a mustache and a fake nose. Cutting out everything except the protocol between the "server" that displays windows and "client" windows is the correct approach, leaving the server implementation and everything else modular. Restricting the ability for one program to snoop on another requiring building up other APIs (as protocol extensions or otherwise) for that is also correct imo.

This doesn't mean that we can't have a unified server module using common APIs for things traditionally handled by X and its extensions either, a lot of wayland compositors are built on wlroots and alike, which is functionally the equivalent of leaving everything except the WM and compositing to the common server, like in X. The only thing we lose is time required to adapt to this new standard and build up the ecosystem of protocol extensions and tools we've grown used to.

@icedquinn seems about right, no support means you can't use a controller at all and having sensible bindings is full support, so it makes sense that badly emulating a mouse would count as partial support. On the worse end, but still.

happy 9/11

#meme