

I was talking about being compatible, not performant. Proton is very often more performant, but WoW64 is seamless and extremely compatible. If we were to pick say 2000 windows 32-bit apps, selected at random released over the last, say, 25 years do you think WoW64 or the combination of Proton/WINE will correctly execute the largest number of them without requiring tinkering? How many if we limit the tinkering to something really basic, like picking the windows version it was made for off a list?
That’s what I’m getting at that I’ve been downvoted for - this “hybrid” console will almost certainly have better compatibility than Proton/WINE for regular windows software (let alone XBox software) and that’s going to be it’s draw. For stuff that’s also compatible with Proton you’ll likely get better performance out of Proton, but effective and seamless compatibility layers are a strength of MS - most regular users don’t even realize that when you run a 32-bit windows app in x64 windows that there’s a compatibility layer involved at all.



…and how do you ensure your fork does not contain a single commit involving even a single line written by Claude? If you can’t, then isn’t your fork slop by default?
Sure, it learned to code by reading lots of code, most of it just publicly available online for anyone to read and for anyone to learn from but not explicitly licensed for a machine to read it and learn from it. I doubt it’s possible to teach an ML system (or for that matter a human being) how to code without reading lots of example code. And any code you’ve ever read has an impact on any code you write afterward (same as any other creative endeavor), that’s why clean room design as a defense against copyright infringement is a thing that exists.