The_Decryptor

I imagine the stones would survive it, just fall out of the vanishing gauntlet. It’s not like the stones were a part of it, they were just being held in place by it, but then there’s the question of whether or not the contents of people’s pockets got snapped as well, we know the pager Fury had didn’t count as “part of him”.

And no, they used the ant man tech to go back in time, no stones there.

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

It’s a tad out of date, but the Second Doctor claims he received a medical degree after studying under Joseph Lister in 1888.

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.

I think it’s unfortunately a given at this point.

And they’ll take credit for “stopping” it once they no longer need to hype it up of course.

We have so many more problems than not being able to show some types of drug use in video games.

Well there was Joseph Staten, worked on CE/2/3/ODST, went with Bungie when they became independent, then rejoined MS and ended up being “Head of Creative” on Halo Infinite.

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.

At the kernel level you’re not going to be using package managers, or anything with a GC (rip D)

I don’t think C is particularly good, but it’s “good enough”, and nothing obviously better at these use cases has come along to displace it. It’s been around long enough that it “just is” the tool of choice for stuff for people.

Which of course leads to things like the Linux situation where it’s big enough that nobody actually understands how it all works or fits together.

It supports it, but it’s opt-in by apps.

Enabling compression is another option (Though with a speed and size penalty), it’s user visible at least.

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.

There are different kinds of solar power generation, the photovoltaic panels that generate electricity directly that we all know and love, and thermal solar. You’ll commonly see a small-scaled version of this used on homes as a hot water system.

Scale it up though and you’ve got a system that can generate energy 24/7, as long as you’ve got enough thermal mass, and sunlight.

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.

I quite liked the locale in FC5, but the (nearly?) unavoidable captures the game would force on you when you did too much open world stuff annoyed the hell out of me.

Then I had the ending spoiled for me and I just got too annoyed at the story planners and never touched it again.

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.