Metal isn't new, it's older than Vulkan, and by some metrics I would consider it better.
For one, the learning curve is much smoother: you can get something up on screen quickly, but only later discover the advanced features like argument buffers, manual hazard tracking, etc.
We are talking 4 years old (3 for desktop) years old vs 2 years old, you're kidding yourself if you think either is established by virtue of being old vs new. That comparison was only fair with OpenGl.
Erm, not really. I have implemented a reasonably serious PBR renderer in Vulkan on Mac on top of MoltenVK, and the C API is not at all an obstacle. Swift/C interop is fairly straightforward, and Objective C is a superset of C so that is a total non-issue.
The ability to easily integrate the wealth of C libraries directly into your high-level code (as opposed to, say, the verbosity of implementing a JNI) is one of the strengths of Swift.
What's a C++14 shader? Metal uses MSL last time I checked...
> manually compilation of shaders
The toolchain for this in Vulkan is pretty solid. It's actually nice to be able to write shaders in a high-level language, and then compile them down to SPIR-V which is more likely to be interpreted consistently across drivers than a high-level language.
Yes but there's nothing surprising about the Walled Garden Company promoting their own snowflake version of Vulkan and insisting everyone who wants to run software must do things their way. This is the same company who has totally locked down the tooling to create and publish iOS apps to only be possible on their hardware.
To be fair, Metal is more than a "snowflake version of Vulkan". For one thing, it was in production before vulkan, largely to address the issue of OpenGL's overhead on mobile devices, and basically it achieves that goal. Also there are certain things which are exposed in Metal which are not in Vulkan, for instance more control over the tile memory which mobile GPUs use. So it's not as if there is no reason for Metal to exist (of course I would be happier if Apple contributed to Khronos to get those features in Vulkan instead).
But the walled garden approach seems counterproductive here. In the days of Microsoft's dominance Apple made an effort to make windows formats usable on Apple because that meant it would be easier for consumers to switch to Apple without worrying about losing all their stuff from Windows. With regard to applications in which graphics API's are relevant (i.e. games) Apple still has a minuscule market-share, and it seems like they would be well served by adopting the dominant technology. Lock-in only works if you're already winning.
Some devs are so obsessed complaining about Metal that most aren't aware that UWP and Windows Store are DirectX only.
An advantage of all proprietary 3D APIs is the amount of out-of-box infrastructure code, debugging tools and having progressed beyond C, while Khronos APIs are still mostly C, and requiring creating mini-engine from scratch after fishing for libs.
I don't really see the issue with C APIs. IMO C is a fantastic integration point for a library which wants to have the widest reach possible. Interoperability with C is a solved problem in a wide variety of languages, so C APIs tend to be easy to integrate. Also since C is a fairly thin abstraction on top of what a computer actually does, good C APIs tend not to be opinionated about how they should be integrated.
I would consider working with C APIs to be a basic programming skill.
> With regard to applications in which graphics API's are relevant (i.e. games) Apple still has a minuscule market-share, and it seems like they would be well served by adopting the dominant technology. Lock-in only works if you're already winning.
Except Metal is the dominant API on almost all Apple platforms. Metal supported-iOS devices are at 700 million (last year's WWDC stat) and majority of games are using Metal on iOS. You can't ignore that market, iOS games are very profitable.
Well as you say, Metal is really for iOS. And I think the evidence points to Apple caring much more about iOS than the Mac. So it makes sense from that perspective.
