Quoting: ShmerlThey didn't have anything even planned, let alone released.

DX12 came out in early 2014 (my mistake, it came with Windows 10 in 2015; it was announced in 2014). Vulkan wasn't released till early 2016.

View this comment - View article - View full comments

Quoting: ShmerlHe became the head Xbox / gaming division in MS in 2014. That's before Vulkan was even announced and during the important period when Mantle was presented by AMD to the industry as a prototype design of a common GPU API. So he totally was in charge of making the decision whether to collaborate or to push lock-in. And we know what MS did.

Even if you say someone else (shortly) before him decided to make DX12 from Mantle, he totally could scrap that and make MS collaborate with Khronos on Vulkan which was still in development phase. He didn't.

So you've worked for Microsoft for, what, 25 years? Microsoft have a product already released that's they think is pretty good, and you're put in charge of the department whose primary function is to push that product. And you decide, before a competing product is even released, to say, "you know what? Our product is bullshit. Scrap the whole thing."

That seems reasonable to you?

View this comment - View article - View full comments

Quoting: ShmerlGiven Phil Spencer is probably the reason MS didn't back Vulkan but pushed DX12 lock-in instead,

Not really. DX12 was a thing before he got put in charge of Xbox, and Xbox being a thing to push DirectX ("DirectX box") was a thing long before he was in charge.

it's interesting that he has some positive comments about Steam Deck which relies on breaking that very lock-in.

It's the only good move. If they say nothing about the new gaming hotness then they look out of touch with gaming. If they say something negative about their competitor then they make themselves look bad and give their competitor good publicity. By saying something positive they have an opportunity to cast themselves as the good guys while promoting their own product. Sweeney did exactly the same thing.

View this comment - View article - View full comments

Quoting: einherjarIf we have an Incident in our company, we mean something is faulty.

In that context it's a euphemism to avoid assigning blame: it's not anybody's fault, it's an incident.

View this comment - View article - View full comments

Quoting: PhiladelphusThat gave me a funny thought, how long until someone installs macOS on a Deck for the sheer novelty? :grin:

Deckintosh.

View this comment - View article - View full comments

Quoting: HoriIf you think about it... Proton games should cost less because you don't get support, so why pay for that?

I mean... I don't. I'm pretty sure everyone's tired of me saying so. It would be good for someone from the mainstream gaming press to strongly suggest specifically waiting for a deep sale before buying a game for the Deck from a developer that won't support it. "We didn't bother to test, and we won't fix any problems you have. Money up front." is terrible customer service by any measure.

View this comment - View article - View full comments

Quoting: GuestTypical deflectionary response from someone who probably has a lot of creative talent but is either too intellectually lazy or unksilled technically to think outside of his comfort zone.

There are an untold number of game devs that never consider or mention Linux at all. Garry isn't one of those: he specifically lashes out about it.

My strong suspicion is that he did actually try Linux at some point, but then went all Windows Power User and messed it all up. Since it couldn't have possibly been his mistake (because he knows that he does computers good), it must be Linux that's to blame. It's a fairly standard pattern.

View this comment - View article - View full comments

Quoting: lejimsterHas any of this Futex stuff ever made it upstream? It seems like every year there is some attempt, but it never makes its way into the Kernel.

The kernel cadence is a new version every two months, so more often than that 😝

I can see their point that they want to get their use case sorted for their use case, particularly before December, and they don't want to be bogged down by the kitchen sink nice-to-have stuff that people want, but I hope the design of the changes that get made doesn't prevent the kitchen sink stuff in the future. We don't want to have to have a futex3.

View this comment - View article - View full comments

Quoting: NeverthelessInteresting! Maybe I should try Kubunto, or Manjaro..

There's certainly no harm in trying. I think I probably had to use nomodeset for the installer (Pop having an installer with the Nvidia driver already installed is a great idea) but that was it. My (Intel) laptop had Cinnamon on (which I'd been using there for quite a while), but that got swapped out for KDE almost immediately after I'd tried KDE on my desktop.

View this comment - View article - View full comments

Quoting: NeverthelessI would be maybe.. but somehow I have the feeling KDE and Nvidia aren't friends...
Even the installation of Fedora KDE crashes all the time for me.

KDE on Nvidia's been perfectly fine for me since I started using it ~three years ago.

View this comment - View article - View full comments