Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)CO
Posts
0
Comments
1,532
Joined
2 yr. ago

  • ProtonDB is your friend. I haven't had to tweak many games, but you can find useful information there. ProtonUp-QT is also sometimes helpful. It streamlines adding proton GE, which is sometimes needed for codecs steam can't package. I personally install everything I can through steam, though some prefer heroic or lutris for other stores.

  • It works perfectly fine for me for almost anything that doesn't have a rootkit packaged with it on steam deck.

    My desktop I've had a couple more issues because I use Nvidia and their drivers are less supported. But it's still not that bad.

  • No, I know with certainty that it's fucking malware, that it's a massive security hole, and that there is abundant precedent that customers inherently cannot consent to unreasonable EULA terms.

    There's a reason that no abusive EULA term has ever been accepted or enforced by courts. The idea that all that shit is automatically ignored, but somehow consenting to extremely invasive malware is OK is completely batshit.

  • I'd wait, at this point. The switch was nice as the first legitimate handheld that could play real 3D games, but the steam deck exists now and the switch is just my Nintendo machine. And even that's largely because I'm too lazy to rip my games and saves over. The stuff I've tried plays better on deck.

    I could see a lot of the enthusiasts that drove their early sales on the Switch just not bothering and making it look rough until an OLED version comes out. It's not like they've never had consoles flop because they're out of touch with what people want.

  • Because it's not consent.

    No one is choosing "yes, I think installing this malware is a reasonable thing to do". Ignoring that the reality is that they don't communicate it and no one knows, which means every single person involved should be in a prison cell until the end of time, they would be abusing their market position to get that consent.

    It's the entire reason every EULA term is thrown out every time. It's not possible for a consumer to actually form a contract because of the imbalance of power.

  • This is to block cheating shit, right?

    I'm very anti-rootkit anticheat on PC, because it's a PC, and I think it should be literally impossible for customers to consent to it. But consoles are an entirely different beast, and not having control is the point of what you're buying. I have no issue with blocking this shit there.

  • Try it?

    I haven't really needed to virtualize anything lately, but my understanding is that some of the options on Linux are pretty light weight. Frpm discussion I've seen, I think distrobox could resolve the issue with minimal overhead if you have issues natively, though I haven't personally experimented with it or its limitations.

  • We have identified several clusters where users have granted Kubernetes privileges to the system:authenticated group

    lol if that's the whole thing, blaming Google is laughable, unless they default to that somewhere or have faulty documentation. That's not a security flaw with their tools.

  • Exactly. You'd think with the two things they're really competitive on being raw flops and memory, they'd be a viable option for ML and scientific compute, but they're just such a pain to work with that they're pretty much irrelevant.

  • How do they expect developers to make apps for it without actually having it available? This is the dev-kit. Yes, they fake it in software so you can do the basics on a MacBook. But that's not really testing. The device in your hands is testing.

    I recognize that it's expensive. Being an early adopter isn't cheap. But it's sincerely priced insanely aggressively. The resolution is a huge difference from everything else available. It's the difference between 10 seconds of text making your eyes bleed and actually being able to work on a screen with text. You can't get just that for meaningfully less than the Vision Pro.

    The passthrough, same deal. Your alternatives are higher latency while also massively compromising the image quality just to get something passed through at all. And that's before the fact that it has a genuinely powerful SoC in the mix, and high enough quality cameras and processing to be controlled fully with gestures.

    There's a reason all the tech enthusiast "media", who have their hands on a lot of these devices regularly, talk about the rest like they're not anything special, but had their minds blown by the Vision Pro. It's a huge step. And, because of their great development tools and relationships with big players, there will be a richer ecosystem than any of the others. Solo developers already could, and have, made real apps with ARKit for phones. They'll make real apps for Vision Pro, too.

    Other platforms are "more open", but nobody democratizes app development like Apple. I understand the complaints about the arbitrary limitations they place, and don't like all of them, either, but the bottom line is that they really do make it perfectly reasonable for a single dev or small team to get something high quality published and support themselves on, and all of that vibrant ecosystem is going to add a lot of value to Apple headsets.

    Just not day one. Because people need hardware to develop for.