• 2 Posts
  • 220 Comments
Joined 1 year ago
cake
Cake day: November 28th, 2023

help-circle

  • 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.



  • The official Homestuck site will still let the original SWF files load as long as you have something that can play them. Ruffle works fine. You can also use one of the few browsers that still supports PPAPI plugins (like Falkon) with the official Flash plugin.

    But personally I’d say to just use The Unofficial Homestuck Collection, which is more pleasant to read through than the original ever was.







  • 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.


  • 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 did look it up afterwards and found out it could also be Arizona, but still wasn’t sure. I figured porn sites would also be capable of mysteriously mistaking an Azerbaijani IP for a Texan IP. I also figured internationally obscure ISO 3166-2 subdivision codes were much less likely to come up than ISO 3166-1 country codes given that people are much less likely to know what they are, plus they are much more likely to overlap with each other and cause ambiguity. But it is very American to assume everyone else knows the US’s subdivision codes and Lemmy probably has far more Arizonans than Azerbaijanis, so I wasn’t completely sure either way.







  • 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.