made you look
Rust has no stable inter-module ABI, so everything has to be statically linked together. And because of how “viral” the GPL/LGPL are a single dependency with that license turns the entire project into a GPL licenced one.
So the community mostly picks permissive licenses that don’t do that, and that inertia ends up applying to the binaries as well for no real good reason. Especially when there’s options like e.g. MPL.
AMD did nothing to make their drivers better, Vale did.
That’s literally the point of open source though, both AMD and Intel rely on open source drivers, so anybody can fix a flaw they encounter without having to rely on the company to “consider allocating resources towards a fix for legacy hardware”
KHTML and WebKit is a historic mess but it’s debatable at best if Apple actually violated license terms.
There’s no requirement that a downstream fork needs to contribute their code back to upstream, they just need to release it, and they always did that.
The lead developer of systemd has said multiple times that we should be fine with break POSIX if it means developing faster.
I mean, so does GNU.
A lot of this is also a post-hoc justification, UNIX didn’t get shared libraries until some point in the 80s (Can’t find an exact year), so before that your options were to either statically compile the needed functionality into your program or keep it as an entirely separate program and call out to that.
It’s a perfect mix, in a time where enterprise storage was measured in single digit megabytes, and the only efficient way to created shared functionality was via separate programs, and you’ve got an OS that happens to have “easily pass data between programs” as a core paradigm.
And now people invoke it to attack an init program for also monitoring the programs it starts and not just spawning them.
Something easily turned off is distinctly not opt in. They’re still lying to everyone.
It’s just that nobody can agree what “opt-in” actually means, apparently.
There’s also xml5ever, for if you hate XML.
Well we’ve recreated namespaces, and JSON already has a completely useless type system, so it’s pretty much already there.
It’s a shame you’re getting downvoted since you’re actually right, and distros are in the process of moving to “kmscon”, a userspace console, rather than the old kernel console (Which iirc isn’t actually intended to be a general purpose console, it’s meant for boot messages)
That said, the fonts the kernel uses are old style bitmap fonts, extremely limited “attack surface” as they’re not doing stuff like opentype/font shaping, it’s just setting pixel values directly.
Windows Terminal is the terminal emulator that hosts the shell (cmd or PowerShell, or anything else really). It’s the modern replacement for “conhost”.
It’s also a fantastic app, some of the devs are on Mastodon too.
Landrun as well, takes the restrictions on the command line. Can look messy, but does make it entirely standalone, so you can e.g. drop it into a service file as the readme shows easily enough.
Yeah, but that’s still not a lot of data, like LTR/RTL shouldn’t be varying within a given script so the values will be shared over an entire range of characters.
Going by the store page, the frame is using UFS, aka a hardwired SSD.
Yeah, it’s got 256GB or 1TB of internal storage, so you can just use the microSD card to move the game from i.e. the deck to the frame.
Valve uses SDL for their own games, so this stuff would have been worked on internally and developed alongside the hardware itself.
But that’s the benefit of open source in the end, when done well everybody wins. Valve gets to ensure that any game using SDL can function perfectly with their hardware (Deck, Controller and Frame), any devs using SDL in their games knows they get first-party hardware support, and gamers get the benefit of both.
These days a steam console would be much more attractive.
And you’re right, I want one.
They had the “Steam Machine”, but effectively nobody bought it. Maybe now with the Deck people would be more open to it, who knows.
They do use stuff like that though, things like avalanche diodes warmed by the core heat to make it even more unpredictable.
But sometimes things don’t work the way they’re supposed to.
They’re called “selections”, the main ones being
PRIMARYandCLIPBOARD, and it’s effectively a form of IPC mediated by X. When you select something, that goes into thePRIMARYselection, while when you copy something, it goes into bothPRIMARYandCLIPBOARD.The problem is that “middle mouse click” isn’t actually paste, it’s “insert primary selection”. As long as they’re in sync you won’t notice any issue (Ctrl+V and MMB will both insert the same content), as soon as they’re out of sync you’re suddenly exposed to an implementation detail of the X11 protocol.
And it’s easy to go out of sync, simply copy something and then select unrelated text, now Ctrl+V and MMB will output different things. It can be useful, e.g. if you’re having to copy a bunch of different pieces of text from one window to another, you can simply select and MMB, no keyboard needed, but it’s not intuitive IMO, and conflicts with modern usage of the middle mouse button (Get it wrong when trying to open a link in a new tab and you’ll dump whatever text you last selected into the site instantly)
Also, these selections aren’t a thing under Wayland, it’s been re-implemented as a normal paste operation there. The question is actually whether the middle mouse button should be treated like any other mouse button or have this special behaviour by default. My vote is to expose it via the mouse settings applet and leave it up to users, like any other special mouse button.