made you look
I’ve seen zero RISC devices in the wild
Ever seen an Nvidia GPU? They’ve been using them for years. One estimate is they shipped 1 billion cores in 2024.
Not as end user programmable chips of course, but the “end user devices” market is only a small part of the total industry.
Can you explains the knitpicking? They specifically decided that only objects orbiting our star can be Planets. It wasn’t an oversight but intentional. How can that be explained? Why do that?
Because we’re not going to be visiting any exoplanets anytime soon, so it’s not like we can actually check how much they’ve cleared their orbits.
Really good network stack. Linux is catching up surely but places like Netflix run a ton of stuff on BSD simply for that stack.
Depends on the specific BSD, OpenBSD for example is only just now catching up to Linux.
Edit: Slide 28 for a graph
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.
Firefox uses literally the Chromium sandbox on Linux, they have for years.
They don’t do that anymore in new versions, but you still need to actually use the new version to get that behaviour. It’s a bit of a pain since the “fixed” version is in the MS store, the broken one is a base system component.
It also hits the people who use the terminal the least, anybody who uses it regularly will just install the new shell at the same time they install the new terminal and always get the new clean behaviour.
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.
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.
Ehh, I’d pass on Ladybird. I’ve been donating to Servo myself.
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/
Other way around, you can convert a “web safe” JPEG file into a JXL one (and back again), but you can’t turn any random JXL file into a JPEG file.
But yeah, something like Lemmy could recompress uploaded JPEG images as JXL on the server, serving them at JXL to updated clients, and converting back to JPEG as needed, saving server storage and bandwidth with no quality loss.