This can, as I see it, only lead to giving more power to the big companies and shafting the indie developers and linux gamers... So in general, fuck those people!
This can, as I see it, only lead to giving more power to the big companies and shafting the indie developers and linux gamers... So in general, fuck those people!
http://www.gdcvault.com/play/1022018/
This is being spearheaded by Valve so the idea that they want to do anything to harm indie developers or linux gamers is simply incorrect.
- The day The Khronos Group releases the Vulkan specifications is when they plan to open-source their Intel Linux driver.
http://www.phoronix.com/scan.php?page=news_item&px=LunarG-Vu...This is exactly the same as OpenGL - OpenGL is an open standard, and has an open-source implementation by the name of [Mesa](http://www.mesa3d.org/).
As other people have said, OpenGL is to Vulkan as C# is to C. For large-scale engine developers, it's quite clear which you'd want to use, under-the-hood.
Besides, just writing the C# runtime environment in C makes an awful lot of sense.
I think that's kind of misleading. Mesa lags years behind any current OpenGL standard.
Today, GPU vendors write big, complex, closed-source drivers offering high-level APIs that as a result are buggier and harder for FOSS-developers to keep up with and make FOSS replacements for.
With Vulkan, GPU vendors should write smaller/simpler drivers, in theory making it easier/cheaper for them to provide good drivers and probably reducing the amount of work needed to produce a replacement FOSS-driver.
The complexity and the high-level APIs is supposed to move out of the driver and into libraries and engines, and many such will be FOSS and probably more portable than the FOSS kernel drivers can be. Please correct me if I'm wrong, though, as I'm not a graphics guy, but I was happy for FOSS when I first read about Vulkan.