if you want it to go away, everyone who is working on it and making it work right now disagrees with you
I’m sure most people wouldn’t like losing their jobs.
made you look
if you want it to go away, everyone who is working on it and making it work right now disagrees with you
I’m sure most people wouldn’t like losing their jobs.


They’re called “selections”, the main ones being PRIMARY and CLIPBOARD, and it’s effectively a form of IPC mediated by X. When you select something, that goes into the PRIMARY selection, while when you copy something, it goes into both PRIMARY and CLIPBOARD.
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.


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”


Ahh, yeah that’s a bit harder, CSS multiline stuff is pretty flaky from what I can recall. You need to drop down to block layout, e.g. making the containing element a flex parent (Better term than that?) and then making the icon centered within that can work, but then we’re back to square one with sizing the icon.


<p><svg class="icon">...</svg> Text</p>
p .icon {
--size: 1.25em;
vertical-align: calc(0.5cap - 0.5 * var(--size));
height: var(--size);
width: var(--size);
}
Done.


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.


Git itself (Or any other VCS for that matter) really should treat symlinks as special, similar as to how btrfs stores everything as “reflinks” internally. They be stored as special references to other tracked objects (so it’d be impossible to commit a symlink that pointed at anything other than a checked-in file, and ensure they always match), and git can materialise them as needed.


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.


Pretty sure that’s just high-frequency trading.
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.


Webp is a smaller file size than jpeg for the same image quality in almost all circumstances
For lower quality images sure, for high quality ones JPEG will beat it (WebP, being an old video format, only supports a quarter of the colour resolution than JPEG does, etc.) JPEG is actually so good that it still comes out ahead in a bunch of benchmarks, it’s just it’s now starting to show it’s age technology wise (like WebP, it’s limited to 8bpc in most cases)
It also doesn’t hurt that Google ranked sites using WebP/AVIF higher than ones that aren’t (via lighthouse).
Edit: I should clarify, this is the lossy mode. The lossless mode gives better compression than PNG, but is still limited to 8bpc, so can’t store high bit depth, or HDR images, like PNG can.
Edit 2: s/bpp/bpc/


Well, all websites are written in JS (on the frontend)
Not true anymore unfortunately, some sites are using frameworks compiled to WASM instead.
e.g. X is apparently using Yew now.
Edit: Ok the “apparently” is doing heavy lifting, since now I can’t find the original source I read about it. Turns out “X” is a garbage name with no searchability, only an idiot would use it.


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.


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.


Windows doesn’t even have basic package management like every Unix-like OS does so you don’t have to individually update applications and go find them on the Internet
Funny thing is that it does (winget), but it’s a terminal app. Windows users who look down on Linux users for “needing” to use a terminal don’t want to bring it up, so Linux users also aren’t aware of it and never point to it as a counter example.
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.
Depends on the specific BSD, OpenBSD for example is only just now catching up to Linux.
Edit: Slide 28 for a graph