They've done some amazing work.
The_Decryptor
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.
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.
They're super useful, and it's easy to get a US model in case you come across region locked blu-ray disks
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.
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.
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.