The_Decryptor

systemd maybe, but people are already running Wayland on FreeBSD and OpenBSD

They’ve done some amazing work.

It’s “FEX”, Valve have apparently been testing it with Proton.

The Asahi Linux team have their own packaging/tooling around it, but theirs is slower at runtime because they have to run the games inside a VM as well.

They’re investing in “green metal”, using their own renewable generation to produce hydrogen.

Whether or not it works out is another matter, but he (Andrew Forrest) seems to believe in it and is willing to put his money where his mouth is.

deleted by creator

Hmm, for me it just says “This item is not available for purchase in your region”, not sure I know that currency.

What you see in stuff like Google Maps or OpenStreetMap isn’t plain Mercator, it’s a variant called “Web Mercator”

And the US DoD doesn’t like it because it introduces even more deviations than plain Mercator.

Then don’t get me started about how the www subdomain itself no longer makes sense. I get that the system was designed long before HTTP and the WWW took over the internet as basically the default, but if we had known that in advance it would’ve made sense to not try to push www in front of all website domains throughout the 90"s and early 2000’s.

I have never understood why you can delegate a subdomain but not the root domain, I doubt it was a technical issue because they added support for it recently via SVCB records (But maybe technical concerns were actually fixed in the decades since)

Chromium had it behind a flag for a while, but if there were security or serious enough performance concerns then it would make sense to remove it and wait for the jpeg-xl encoder/decoder situation to change.

Adobe announced they were supporting it (in Camera Raw), that’s when the Chrome team announced they were removing it (due to a “lack of industry interest”)

They’re “file like” in the sense that they’re exposed as an fd, but they’re not exposed via the filesystem at all (Unlike e.g. unix sockets), and the existing API is just mapped over the sockets one (i.e. write() instead of send(), read() instead of recv()). There’s also a difference in how you create them, you open() a file, but connect() a socket, etc.

(As an aside, it turns out Bash has its own virtual file-based wrapper around sockets, so you can do things like cat a remote port with Bash, something you can do natively in Plan 9)

Really it just shows that “everything is a file” didn’t stand up in practice, there’s more stuff that needs special treatment than doesn’t (e.g. Interacting with TTYs also has special APIs). It makes more sense to have a better dedicated API than a generic catch-all one.

RFC 3339 is a simplified profile of 8601 that only covers YYYY-MM-DD style formatting, if you only ever use that format and avoid the things like “2024-W36” they’re mostly interchangeable.

Plan 9 even extended the “everything is a file” philosophy to networking, unlike everybody else that used sockets instead.

Existing JPEG files (which are the vast, vast majority of images currently on the web and in people’s own libraries/catalogs) can be losslessly compressed even further with zero loss of quality. This alone means that there’s benefits to adoption, if nothing else for archival and serving old stuff.

Funny thing is, there was talk on the Chrome bug tracker of using just this ability transparently at the HTTP layer (like gzip/brotli compression), but they’re so set on pushing their AVIF format that they backed away from it.

His personal LLC is called “Excession”, considering some of the plot points in that book I doubt he enjoyed it at all, it’s just “nerd set dressing”.

At the time it was just an ad-lib by Jason Issacs, guessing he wished on a monkey’s paw for it to make sense in context.

1. If your ISP doesn’t do IPv6, then you’re fine (But should look for a better ISP)
2. If your ISP does do IPv6, then you should install the patch now (Unless you’re not using IPv6 on the LAN, in which case you’re fine but get a better router/sysadmin)
3. If your ISP does do IPv6, but you can’t install the patch for whatever reason, only then should you disable IPv6

The problem is people recommend disabling IPv6 for random unrelated reasons (Like gamers claiming it decreases your IPv4 latency), so yeah MS is going to be insistent that users not fiddle with things they don’t understand because it’s really unlikely they’ll go back and restore that config when it doesn’t actually help.

Ideally you don’t directly ship the code it outputs, you use it instead of re-writing it from scratch and then slowly clean it up.

Like Mozilla used it for the initial port of qcms (the colour management library they wrote for Firefox), then slowly edited the code to be idiomatic rust code. Compare that to something like librsvg that did a function by function port

c2rust: Am I a joke to you?