Mhm, fair point. Although… I would say the steam deck’s popularity and proof of viability as a gaming device is doing an immense amount of work on its own. I built a gaming PC ~2 years ago, and even as a long time developer and someone comfortable with a UNIX terminal I opted to get a copy of Windows for gaming, and had to awkwardly get to grips with it and find tools to get it playing the way I wanted.

It’s only ~1 month ago that the prevalence and maturity of the steam deck (combined with Windows recall re-emerging🤮) finally had me at ease enough to give Bazzite a shot, and since jumping myself and expressing how happy I am with it, 2 of my long term “on the fence” friends have asked me questions and are starting to try Linux themselves.

Larger Linux market share, regardless of how it gets there, gives broad confidence in Linux, and also pushes developers and Steam itself to maintain Linux support and tools like Proton, which reinforces the cycle, even if it doesn’t help us “kill Windows” for as long as users don’t understand how to install it.

Interesting. I’ve been using XeSS lately, after seeing better results in DOOM TDA, but now I’m curious if this is worth using instead, and figuring out an FSR replacer on Bazzite to use this.

My guess here is that it isn’t Denuvo, it just seems like it’s not designed for Open World games. These issues all also exist on console, where Denuvo isn’t a problem (although it certainly isn’t helping either). Dragon’s Dogma 2 exhibited a lot of the same poor performance and stuttering nearly a year before MH Wilds came out.

By then, I assume the game was too far into development to change course, with it’s ambitious design and a lot of AI that has to always run in each area adding to the engine issues.

Honestly… I’m not sure how much better they can make it, given how much time they’ve had to work on it, and that DD2 never really escaped its issues too. It feels like RE Engine was just… fundamentally not designed for this, no matter how great an engine it is in its niche.

Might be a good use case for Anubis, in addition to the URLParam passwords mentioned elsewhere. Enough protection to prevent trivial brute force scraping, while also being basically invisible to users.

Ugh, this is what our legacy product has. Microservices that literally cannot be scaled, because they rely on internal state, and are also all deployed on the same machine.

Trying to do things like just updating python versions is a nightmare, because you have to do all the work 4 or 5 times.

Want to implement a linter? Hope you want to do it several times. And all for zero microservice benefits. I hate it.