I dunno, I expect the Deck to last far longer than the average console if anything. It’s a PC, so the games are pretty much guaranteed to keep coming for decades to come, as they have for decades past.

The hardware will fall behind, so I think the point where the newest Triple A games won’t be playable will come within a few years, but I bet whatever visual novels or pixelated indie games release in 2035 will still run just fine on it.

Plus, it’s designed to be repairable, unlike most consoles. And even if Valve stops maintaining SteamOS for the Steam Deck, you’ll still be able to install other distros, so software support isn’t something I’m very concerned about either.

No romhacker or homebrew developer worth their salt will touch any of this. Using leaked material is legally significantly more dangerous than REing. I look forward to seeing the TCRF pages, though.

What exactly does Valve stand to gain at all from funding a CUDA compatibility layer targetting mainly machine learning software? They’re a video game company. Arguably the most gaming-centric thing CUDA is used for was explicitly discarded in the blog post (“Raytracing is gone”).

Machine learning is massive now and there are many companies who could be interested in funding this kind of project. I’m pretty skeptical it’s possible to make any good guesses with what little info we have.

Japan also has heavily subsidized agriculture afaik.

History:

1. ZLUDA starts as a project to make CUDA work on Intel GPUs, with funding from Intel.
2. Intel pulls funding, author manages to get funding from AMD instead.
3. Development of a new version targetting AMD GPUs happens under closed doors with the informal agreement that the source code will be publicly released if AMD pulls funding.
4. After a couple of years, AMD pulls funding and the source code for the new version is released.
5. Development continues in the open for a few months, albeit at a slowed pace.
6. AMD goes back on their word, claims previous agreement wasn’t legally binding and asks that ZLUDA source code be taken down.
7. Author reverts codebase to its pre-AMD state, looks for new source of funding.
8. ZLUDA’s Third Life
9. Anything regarding NVIDIA involvement is pure speculation and should be treated as such.

I downvoted it because conservatives constantly make this exact same “joke” about how poor people actually deserve to be poor because they pay for Netflix or clothes or anything that isn’t food or rent. It’s not funny when they do it and because I’m not a hypocrite I don’t find it funny when leftists do it either.

Normally I would have just downvoted and moved on with my day, but apparently that makes me a “coward that refuses to stand and be counted”. Because attacking people for downvoting a joke they didn’t like is apparently 100% okay with Lemmings and totally not toxic behavior. Does not liking literally all of the comedy that comes out of the left make me a ‘bad-faith both-sides “leftist”’? If so, guilty as charged. I do not see the left as a monolith and feel no shame in criticising or disagreeing with what other leftists say.

Huh, just realized Yuzu was GPLv3. That’s weird. Citra was GPLv2 and Yuzu is a Citra fork. Some of the Citra devs were Yuzu developers, but not all of them, so I wonder how they handled the relicensing. Yuzu had a CLA attributing copyright to the creators, so that wouldn’t have been a problem, but Citra had not such thing.

I mean, all of these emulators are already very well archived and available from several sources, not to mention downloaded to the devices of millions of people. I highly doubt we would be in danger of losing any of them even if Nintendo were to sue literally all of them overnight. Well, except for things like Github issues and pull requests, nobody bothers to archive those unfortunately.

But yeah, IMO the danger is moreso that the attacks are leading to a massive chilling effect and loss of developer talent in the emulation community.

Well, Steam and Proton both already run on top of FEX or Box64 on ARM Linux, but it’s nice to see an official effort from Valve.

Also, does ARM still have better battery life when all of the machine code has to be translated from x86? That adds a not insubstantial amount of CPU overhead, which does hurt battery life.

And perhaps most importantly, is there any ARM chipset out there that can deliver performance on par with the Steam Deck’s CPU (even after factoring in the overhead of the x86 JIT) at a viable price for a Steam Deck successor?

Obviously. ES6 isn’t out yet. The point is that there are many things ES6 could improve over Skyrim if they tried.

Servo is not the old name for Gecko. Gecko existed long before Servo was started and Servo continues to be developed independently of Mozilla. It was a research project to develop a web rendering engine in Rust taking advantage of parallelization. The parallelization stuff mostly made it through the Quantum project several years ago, which did indeed help performance. That’s about it. As of right now, Gecko’s code base 55.4% C++, 22.6% JavaScript, 4.5% C, 4.3% Kotlin and a mere 3.8% Rust. If Servo had indeed been integrated into Firefox, over half of this would be Rust. 53.2%, if the current Servo repository is anything to go by.

laying off the servo staff at least was a mistake

first screenshot doesn’t look like aero at all tbh. second one more so. this is the most accurate port I know of tho https://gitgud.io/wackyideas/aerothemeplasma

devault has a site called sourcehut. that’s about all I know