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.
::: spoiler spoiler made you look :::
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.
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
Hmm, for me it just says "This item is not available for purchase in your region", not sure I know that currency.
although I’m not sure what USB4 Gen 3×1 is, but it’s only x1 so can’t be that good, right?
It's the initialisation mode of USB 40Gbps, luckily not something users will have to deal with
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.
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".
Unfortunately WebTorrent isn't compatible with normal BitTorrent, so unless you're using a client that specifically supports it, you're not helping out any PeerTube clients
You can't do normal BitTorrent in browsers, there's no support for plain sockets that you'd need to communicate with other peers, WebTorrent is technically a new protocol that implements the BT semantics over stuff the browsers do provide (So you can proxy between the different swarms, that's the "hybrid" nodes in the image on the WebTorrent page)
But it turns out it's all a moot point, since PeerTube removed WebTorrent support anyway in favour of their own P2P system
Edit: Ok so I misunderstood, and it seems like it's a bit complicated. The server can (it's disabled by default) use WebTorrent to import videos, the client still uses the WT trackers to find peers but uses a different protocol to actually share the video data.
There's this tool that provides the ability to automatically seed videos, but development has stalled because no up to date client will ever make use of it.
I think the one remaining use is the "download as torrent" option, but even then that's just using a web seed, so it's just an alternative way to download the video.
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.
They've done some amazing work.
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.
What’s the problem with that, though? Systems like that are pretty much guaranteed to be isolated from the internet.
Because things break down eventually, and when it comes time to buy replacement parts you discover that they're effectively impossible to find. Then instead of having a nice, planned transition period you've got like a weekend to cobble together something to get it working again.
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.
c2rust: Am I a joke to you?