5 ms·
Congratualations! It's a major step forward. Note this however: > “Vulkan takes cross-platform performance and control to the next level,” said Bill Hollings
by shmerl 11y ago
Congratualations! It's a major step forward.
Note this however:
> “Vulkan takes cross-platform performance and control to the next level,” said Bill Hollings of The Brenwill Workshop. “We are excited to be working through Khronos, the forum for open industry standards, to bring Vulkan to iOS and OS X.[1]”
Of course Apple had to remain the jerks they are and not support Vulkan natively, forcing developers to write translation layers[2]...
[1] https://www.khronos.org/news/press/khronos-releases-vulkan-1-0-specification https://www.khronos.org/news/press/khronos-releases-vulkan-1...
[2] https://moltengl.com/metalvk/ https://moltengl.com/metalvk/
- Harimwakairi 11y ago"They have every logo on here except Apple," was the first thing I thought upon seeing the page.
- ksec 11y agoYou can still use OpenGL on OSX / iOS. If the Flowchart is true, then it wouldn't matter for 80% of people, for the rest, there is Metal.
- shmerl 11y ago> for the rest, there is Metal. The question is why Apple can't support Vulkan, or rather why wouldn't they. The answer is quite obvious - they like lock-in. > If the Flowchart is true Flowchart is not true, because using OpenGL is not a good proposition going forward. Some will develop more tools and higher level frameworks to make using Vulkan easier. But jerks like Apple, MS and others will put roadblocks for developers preventing them from using the new API on their platforms.
- bryanlarsen 11y ago"because using OpenGL is not a good proposition going forward." Why? Khronos has publicly stated that development of OpenGL will continue, and that OpenGL and Vulkan will continue to co-exist.
- shmerl 11y ago> Why? Because it's inherently stuck in the outdated model of using huge state machine where state is shared. It doesn't allow using parallelism efficiently. > Khronos has publicly stated that development of OpenGL will continue They are free to continue it, but I don't see a benefit of using it instead of Vulkan for anything new. The main drawback of Vulkan now is that it's low level in comparison with OpenGL. That gap will be filled in with frameworks on top of Vulkan which will provide higher level abstractions implementing a lot of common boilerplate while using Vulkan's approach of avoiding massive state machines. And those who need that low level directly can always go there. So why would you use OpenGL exactly?
- bryanlarsen 11y ago"So why would you use OpenGL exactly?" Because I care about working on phones, and on crappy old video cards and iOS and OSX. Because the only times Vulkan provides any benefit over OpenGL is when I'm CPU bound, and that only happens on high end video cards, which are handling my workload without a sweat, so why would I bother optimizing those? Because Vulkan is a low level API that's not easy to program for. OpenGL isn't exactly easy to use, but it's a heck of a lot easier than Vulkan, from what I can tell. Because the work I do is more closely related to the CAD market than the video game market, and I know that there's enough money in CAD, and that OpenGL is not going anywhere for CAD, so I'd bet that OpenGL will be around for ~25 years in some form or another. I wouldn't place that bet on Vulkan.
- shmerl 11y ago> Because I care about working on phones, and on crappy old video cards and iOS and OSX. Sure, OpenGL will remain useful for supporting both legacy applications and legacy hardware. > Because Vulkan is a low level API that's not easy to program for. OpenGL isn't exactly easy to use, but it's a heck of a lot easier than Vulkan, from what I can tell. I answered that above. It's not a reason to use OpenGL, it's a reason to write something on top of Vulkan to make things easier. > Because the only times Vulkan provides any benefit over OpenGL is when I'm CPU bound It provides a benefit of using your hardware to full potential. You can't even properly saturate the GPU with OpenGL with parallel workload, unless you use AZDO and other such things which turn it inside out trying to bypass its limitations. > Because the work I do is more closely related to the CAD market And why exactly Vulkan can't be used in the CAD market?
- webjprgm 11y agoMy first thought on seeing Vulkan is that it is basically Metal for everyone else. Is that not so? Then why would you expect Apple to support Vulkan given that they already have Metal?
- shmerl 11y agoIt's like saying that Apple shouldn't support JavaScript in the browser and should use AppleScript or anything else as long as it's incompatible (remember browser wars?). Why they should use it is quite straightforward - because it reduces duplication of work. Why they don't use it is clear as well - because they want to tax cross platform development with that extra burden. I.e. they use development tools as lock-in tactic. That's simply crooked. Some history can also help. It all started from Mantle. Basically AMD grew tired of current APIs being behind the curve, and designed one from scratch that matches modern hardware approaches. Then Apple and MS used those ideas to push their lock-in off-shoots (they copied most of the ideas verbatim, working closely with AMD). Meanwhile, AMD simply opened up Mantle (they voiced this intention from the beginning) and gave it to Khronos as an initial proposal for Vulkan. The rest you probably know. So why exactly MS and Apple didn't get behind the shared effort? Because they are lock-in jerks. That's all there is to it.
- chc 11y agoThis seems cognate to "Web standards are basically an alternative to the way IE 6 works, so why would you expect Microsoft to support Web standards?"
- AlphaSite 11y agoMore likely, they committed to Mantle and now they have have to maintain it. The manpower to maintain 3 separate graphics back ends probably wasn't worth it, especially since big portions of the OS libraries now support metal.
- outworlder 11y agoYes, the crappy OpenGL version that they ship. Which lacks things like compute shaders. We are already seeing issues because of that: even though Elite: Dangerous runs on the Mac, the expansion does not and will not, as it requires compute shaders.
- binarycrusader 11y agoNo, you really can't. Not only is the version available on OS X significantly out of date, it isn't even fully functional for the level of OpenGL it claims to support.
- jjtheblunt 11y agoThat's crass: Apple has Metal, and has had it for a few years now, so perhaps a healthier attitude is to give it time.
- shmerl 11y agoApple knew where things are going all along. See my other answer: https://news.ycombinator.com/item?id=11112078 https://news.ycombinator.com/item?id=11112078 So it doesn't excuse their lack of support for Vulkan in any way.
- oldmanjay 11y agoThey don't need excuses when they don't behave as you wish, as they aren't subject to your whims.
- shmerl 11y ago> They don't need excuses Sure, I'm not saying they are looking for excuses. They are just lock-in jerks and never really hid the fact.
- eridius 11y agoApple doesn't have infinite software engineering resources. In fact, given how slowly they adopt new OpenGL stuff, it's probably safe to say that they're pretty constrained on software engineering resources when it comes to low-level graphics technologies. So it's not surprising at all that they've chosen to focus on Metal instead of implementing Vulcan. As for why they did Metal, they most certainly started work on it before the Vulcan project started. Wikipedia says[1] that the Vulcan project was started in July of 2014 (and then announced publicly at SIGGRAPH, which appears to have been in August). But Apple released metal with iOS 8 in September of 2014, and they'd obviously been working on it for more than a couple of months. In an ideal world, Apple would support both. But it's not an ideal world and supporting Vulcan would take resources away from their work on Metal, and that's not something that makes sense for Apple to do. [1] https://en.wikipedia.org/wiki/Vulkan_(API)#History https://en.wikipedia.org/wiki/Vulkan_(API)#History
- flipgimble 11y ago> Apple had to remain the jerks they are and not support Vulcan natively Thats a rather immature view of the technology world that smacks of the tired old tribal warfare notions that only internet forums believe in. Apple had a technical problem of slow, bloated and battery-draining OpenGL API and they solved it using Metal more than 18 months ago, when no other viable alternative was on the horizon. Are they jerks because they didn't saddle their users with a technically inferior solution for even longer? Khronos has let OpenGL evolve into a byzantine beast of an API with GPU vendors effectively segmenting it into multiple complicated variants of best practices (like AZDO and others). Vulkan was announced more than two years ago, but unless you were in a select inner circle of developers, there was no actionable information available, until today. In the meantime, major commercial engines already have official support for Metal (or Unity will have it soon). Popular games like World of Warcraft already have betas using Metal. I can download free IDE, documentation, sample profiling and debugging tools for developing Metal applications. Sad truth is that Kronos and the Vulkan group took too long to evolve OpenGL and to give developers any actionable specifications for Vulkan.
- izacus 11y ago> Are they jerks because they didn't saddle their users with a technically inferior solution for even longer? Em no, they are jerks because they never updated OpenGL implementation on OS X (which still is generally 30% or so slower than Windows implementation on same hardware, not to mention lacking of full 4.2, 4.3, 4.4 and 4.5 OpenGL support) then implementing a new proprietary API on the desktop with huge fanfare and marketing about being "30%-50% faster" (or in other words - as fast as OpenGL is on Windows). Meanwhile, OpenGL implementation is still rotten as of 2016 at 2010 OpenGL 4.1 levels with no update. Leaving an open implementation of a 3D standard to rot in performance limbo and then bringing in a new proprietary standard which has to be used to get competitive performance does bring the word "jerks" to mind.
- shmerl 11y ago> Thats a rather immature view of the technology And you think lock-in is a mature approach to technology? It is not. And lock-in is the only reason why Apple pushed Metal instead of joining the Vulkan effort. Unless you are trying to claim that they just couldn't plan things and ended up with their own NIH despite Vulkan emerging in the background. But that doesn't fly, since they could have corrected it when they realized where things are moving. So "no ill intent" reasoning here doesn't sound convincing.
- Htsthbjig 11y ago"Of course Apple had to remain the jerks they are and not support Vulkan natively, forcing developers to write translation layers[2]..." We write programs that use DirectX,Metal, OpenGL/OpenCL, and now Vulkan and I disagree. We believe competition is great. OpenGL/CL was in theory a standard but over the years we had to funnel way more resources to make that work than with DirectX or Metal combined. Why? Because of the "design by committee" mentality of OpenGL/CL. The only reason they had to react with Vulkan was competition from private companies and even then the reaction was slow and painful for those that were forced to support the bloat software for years. We could do the same thing in OpenGL/CL with 5 different ways,one modern way and 4 obsolete but not pruned from the standard because some company of the committee that had obsolete legacy code banned the removal. This made the codebase so big and hard to maintain, and expensive for developers to support. If Microsoft and Apple runs circles around those people, they are forced to act and develop a better standard. For us it is easier to develop translation layers that support OpenGL/CL messiness.
- shmerl 11y ago> We believe competition is great. Competition is great, sure. But Apple are anti-competition here. Competition would mean choosing between using Vulkan or Metal on their system. Where is that choice (wrapper is a workaround, but besides)? All those lock-in proponents are actually scared of competition. So we are not in disagreement. Competition is indeed good. Lock-in however is not, and lock-in is anti-competition. > The only reason they had to react with Vulkan was competition from private companies It's the other way around. The only reason MS and Apple suddenly woke up is because AMD was planning to open up Mantle (which resulted in Vulkan). Except they reacted in their usual manner. Instead of helping the shared effort they pushed for more lock-in.
- Htsthbjig 11y agoI am not scared about Apple getting a monopoly. They are not going to sell as much as Android because they only care about the high margin stuff. I am more worried about Microsoft though, with Windows and Xbox they force millions of people to use DirectX. Yeah, we agreed on that . It took millions for our company to support OpenGL/CL only because we did not want to make our code dependent on just one provider. It was tough to justify that decision (financially). Decision that only started to pay back with Android popularity.
- beefsack 11y agoWhat Apple are doing with Metal feels eerily similar to what Microsoft did when they launched DirectX back in the day. If we're lucky, it won't be as successful; decades of graphic stack fragmentation hasn't been pleasant to live through, both as a developer and a gamer.
- pjmlp 11y agoThen it is up to the community/Khronos to provide the same tooling and support games developers enjoy from Apple, Microsoft, Sony and Nintendo. GPU vendors don't care much about API support tooling, as long as their hardware gets sold.
- mort96 11y agoI really doubt Apple will ever be big enough for many big game developers to consider making exclusives for Macs. They don't even sell any computers remotely targeted at games, and often sacrifice price and cooling for prettier design.