> The drivers for Windows also need a manual download for each

The emphasis makes it sound like this is anything out of the ordinary for windows, lol

View this comment - View article - View full comments

Quoting: tfkJust read some post on the Steam forums. They got drivers now but are still complaining.

It's a small difference in attitude I'm observing here.

We get native Linux support for something, we say thanks and start to give feedback on any issues we encounter.

They get Windows support for something, they're like "About time!". And when there are issues they're like "It won't work! You suck! I'm selling my device!".

I can see why Valve had this on low priority.

You might not like hearing this, but most projects that treat Linux users as second class citizens have the exact same complaint, that Linux users are entitled and don't appreciate what they got.

People are people, Linux users are no better or worse than any other people.

View this comment - View article - View full comments

Quoting: PyrateStadia failing is a net positive, who knows what will happen to gaming if cloud streaming got accepted this early (it's probably inevitable, but the later it happens the better).

Cloud gaming is happening right now anyway, Stadia's failure didn't change that. Except cloud gaming is now turning windows based, engines are no longer doing Vulkan, and _many_ Google developers who were working on Vulkan no longer do. We're lucky Google accepted to let some of those developers continue working on Vulkan (like the devs of SPIR-V Tools (maintained by Google, originally because of Stadia)), but we lost so many others.

I realize these things are not easily noticeable, I see them because I work at Google and closely work with Vulkan (at Khronos) and its ecosystem (SPIR-V Tools, CTS, etc). And I'm telling you, Stadia's downfall was a *major* blow to Vulkan. And that in turn majorly affects Linux gaming.

View this comment - View article - View full comments

Quoting: PyrateI'll continue to crap on them, keep em on their toes.

You think you're keeping them on their toes, they see Linux users as entitled and annoying. These companies aren't supporting Linux because of *you*, they are doing it because they have large customers who pay them for it. And they support Linux to the extent needed by those contracts.

Sorry to be blunt, but sales coming from Linux users is not significant enough to them, and we don't statistically matter. So maybe instead be nice and the developers who are doing the work would be more motivated to take extra care of you despite the business decisions.

View this comment - View article - View full comments

Folks here like to crap over Nvidia, but you have no idea how valuable their contributions to Vulkan are. Same with Google, people were celebrating Stadia's downfall while in truth it was a _massive_ setback for Vulkan and its ecosystem.

It's disappointing.

View this comment - View article - View full comments

Quoting: TheRiddickStill needs multi-VRR and DLSS FG support. For such a MASSIVE corporation you'd think they be able to do that real fast, yet AMD is outpacing NVIDIA when it comes to Linux driver support. A truly fascinating paradox.

AMD isn't doing any better than Nvidia, quite worse actually. Radv is good because of mesa's _users_, like Valve and ChromeOS. The WSI part of mesa is common, so _that_ part is good thanks to even more companies like Intel and Collabora.

In their proprietary drivers, Nvidia is actually far ahead of AMD, they literally ship a driver with support for almost every Vulkan extension the day after they get released. AMD takes a long time to ship some very important extensions (in their proprietary driver).

Nvidia's WSI with Linux is lagging because sadly they don't care much about Linux, and AMD probably cares even less.

Case in point is VK_EXT_swapchain_maintenance1. When I was writing that, Hans-Kristian from Valve implemented it in mesa so that was available right away on Linux. It took Nvidia more than a year to ship it (because WSI), and AMD (proprietary) still hasn't shipped it.

View this comment - View article - View full comments

Would be real nice to release it on Steam too, just for the convenience

View this comment - View article - View full comments

People seeing other people use something is _really_ effective. Seriously, every time I play with my Deck outside someone asks about it and they had never heard about it, they assume it would be expensive etc.

Get your Steam Deck, Linux laptop, etc *out* and let them *see* someone use it.

View this comment - View article - View full comments

Nice little game I keep going back to occasionally on my Deck. Recommended!

View this comment - View article - View full comments

Quoting: Purple Library Guy

Quoting: LoudTechie

Quoting: 14And it's immune to CrowdStrike.

only [External Link] as a racing stripe. [External Link]

Apperantly Linux servers also encountered this issue, but for linux it was caught by the admins before it could cause an outage.
In conclusion:
Linux is pretty secure, cool and stable, but Linux servers are all those things 10 times more than Linux causes them to be, because they're being managed by Linux users.

Looking at that, it would appear that Linux was vulnerable . . . if it was running virtualized Windows with Crowdstrike on it, using VMWare. I'm not sure a vulnerability that only shows up if you're running Windows counts as a Linux vulnerability.

Why wouldn't it? Linux should protect itself from whatever garbage may be running in a VM.

View this comment - View article - View full comments