Yes, it would seem that Microsoft is ahead in these things. But I don't think Google taking control of the graphics API would solve that problem. Granted, doing it would be a clear statement of intent which would most likely be accompanied by increased effort put into API infrastructure. However, nothing really prevents them from doing the latter without the former. Comparing Apple to Microsoft, and OpenGL ES to Metal, it seems doubtful that there's a strong correlation between control over the API and quality of developer tools.
It's a myth that if a company is just big enough they could achieve anything by just throwing resources at it.
More propaganda to diminish Windows and glorify SteamOS from our Mighty lord and savior Gaben with his holy Steam OS which is one of his might endeavors to counter MS from eventually creating a viable competitor to Steam.
Why do you say that?
Both consoles still use HLSL based shader languages. In order to get more widespread Vulkan adaptation (for cross platform games), we need HLSL->SPIR-V compiler (with full 12_0 feature set). It is pain to port and maintain both HLSL and GLSL versions of the same shaders, especially complex compute shaders (such as modern tiled lighting).
Google should think about Android fragmentation dementia first due OEMs whimpering..
Whimpering about what?
A lot of OEMs on Android are like childish kids on fulling the phone with tons of craps settings and "personalization", even on the driver side. Stupid company politics I guess, the world is full of that...
I get all that, but what does it have to do with Vulkan? Can't google support it in Android easy enough? I didn't think something so fundamental as the rendering API was subject to OEM shenanigans. I thought that was reserved to crapware and UI "improvements".
