News for hackers. Stuff that matters.
Re:No Man's Sky: Update 1.03 by fsloth on Tuesday August 09, 2016 @02:38AM (#12252968)
Sorry, - strawman was not intended. As a person with some experience in the graphics industry, the way I see it: if one uses hardware accelerated real time graphics capability, one is always effectively locking some parts of the rendering codebase in to some specific hardware platform. No matter what the API used to program the platform, you are effectively locked in to very few vendors. There really is no rational reason to highlight Microsoft as especially bad player in this market - on the contrary (as long as they are not the only game in town, of course).
Re:No Man's Sky: Update 1.03 by shmerl on Tuesday August 09, 2016 @02:45AM (#12252996)
> There really is no rational reason to highlight Microsoft as especially bad player in this market - on the contrary (as long as they are not the only game in town, of course).

How are they a good player, if they could back Vulkan instead of pushing lock-in DX12, but they didn't? It's clearly bad.

Re:No Man's Sky: Update 1.03 by fsloth on Tuesday August 09, 2016 @03:05AM (#12253046)
If they would actively block good Vulkan implementations on Windows - yes, that would be a dick move. Is that the situation, though?
Re:No Man's Sky: Update 1.03 by shmerl on Tuesday August 09, 2016 @03:44AM (#12253168)
They actively block it on Xbox.
Re:No Man's Sky: Update 1.03 by fsloth on Tuesday August 09, 2016 @04:55AM (#12253357)
Ok, fair enough. Although I don't see the benefit of opening multiple graphics API:s on a closed hardware platform that is the Xbox console.
Re:No Man's Sky: Update 1.03 by shmerl on Tuesday August 09, 2016 @10:56AM (#12254910)
That's what "closed" here means :) I.e. they block competition.