News for hackers. Stuff that matters.
Re:Ray Tracing with Metal [video] by mtgx on Sunday June 16, 2019 @10:02AM (#20195474)
It's very disappointing that Apple hasn't adopted Vulkan. It's not like they are completely against standards either. I believe they even joined the FIDO Alliance recently.

With Apple adopting Vulkan, it may actually stand a chance against DirectX and the majority of game developers might start developing for Vulkan first. And Apple would benefit greatly from that, just like every other Vulkan supporter would.

Re:Ray Tracing with Metal [video] by Someone on Sunday June 16, 2019 @12:24PM (#20196275)
Ignoring both technical merit and politics, both of which I’m not qualified to judge on, one reason they didn’t adopt it may be that it didn’t exist when they switched away from OpenGL.

https://en.wikipedia.org/wiki/Metal_(API):

”Metal has been available since June 2, 2014 on iOS devices powered by Apple A7 or later”

https://en.wikipedia.org/wiki/Vulkan_(API):

”The Khronos Group began a project to create a next generation graphics API in July 2014”

Of course, Apple could have changed direction later on, but they must have had a large investment in Metal by the time it became clear Vulkan would become a long term thing.

Re:Ray Tracing with Metal [video] by bangonkeyboard on Sunday June 16, 2019 @01:44PM (#20196807)
Johan Andersson (then of DICE) was a presenter at Metal's unveiling. Andersson was one of the prime movers for Vulkan and Mantle before it, dating to 2013. Apple was very aware of Mantle/Vulkan while designing Metal, just as Apple was very familiar with CUDA when it released its own ill-fated OpenCL alternative.
Re:Ray Tracing with Metal [video] by Someone on Sunday June 16, 2019 @05:22PM (#20197976)
”its own ill-fated OpenCL alternative.”

https://en.wikipedia.org/wiki/OpenCL:

”OpenCL is an open standard maintained by the non-profit technology consortium Khronos Group.”

And yes, it started life that way. https://en.wikipedia.org/wiki/OpenCL#History:

”OpenCL was initially developed by Apple Inc., which holds trademark rights, and refined into an initial proposal in collaboration with technical teams at AMD, IBM, Qualcomm, Intel, and Nvidia. Apple submitted this initial proposal to the Khronos Group. On June 16, 2008, the Khronos Compute Working Group was formed with representatives from CPU, GPU, embedded-processor, and software companies. This group worked for five months to finish the technical details of the specification for OpenCL 1.0 by November 18, 2008. This technical specification was reviewed by the Khronos members and approved for public release on December 8, 2008.”

Apple first shipped OpenCL in August, 2009.

So, OpenCL may be ill-fated, but I don’t see why Apple would have to have gone with CUDA, which is Nvidia-exclusive, both in actual hardware, and, AFAIK, license-wise.

Re:Ray Tracing with Metal [video] by shmerl on Sunday June 16, 2019 @03:17PM (#20197332)
That's not really a valid reason, since not only Apple knew all along where it was heading (from Mantle times, to a common open low level API), nothing stopped them from supporting Vulkan once it became official. With Apple's resources, it's peanuts for them. So it looks like a completely political, nasty lock-in stance.
Re:Ray Tracing with Metal [video] by morio on Sunday June 16, 2019 @10:48AM (#20195714)
Why would Apple care about how DirectX is doing? They support 'Standards' and 'Open Source' to the extent that it benefits them and that's it.

Vulkan is not designed to be used by game developers directly but rather as a basis for games engines like Unreal or Unity. So I don't see how game developers would benefit from its widespread support as the majority of game developers will never have to deal with it directly.

That said Vulkan is an unmitigated disaster, though less so than classic OpenGL. Any API which fiddles with void* in 2019 should be put right back in a box. Security is mentioned exactly twice in the entire spec. Type-safety is mentioned twice also. And that is in a spec which is 900 pages long and incredibly complex.

Re:Ray Tracing with Metal [video] by johncolanduoni on Sunday June 16, 2019 @11:05AM (#20195814)
> Vulkan is not designed to be used by game developers directly but rather as a basis for games engines like Unreal or Unity. So I don't see how game developers would benefit from its widespread support as the majority of game developers will never have to deal with it directly.

Vulkan has significant benefits even if you're not writing Unreal or Unity. One of the biggest is that it removes a lot of the heuristics and guesswork that OpenGL drivers do (e.g. with regards to when to move things in and out of GPU memory) that cause a lot of the bugs and incompatibilities on different IHVs/cards/platforms. Its validation layers also leave the halfhearted, vendor specific debugging extensions in the dust.

> That said Vulkan is an unmitigated disaster, though less so than classic OpenGL. Any API which fiddles with void* in 2019 should be put right back in a box. Security is mentioned exactly twice in the entire spec. Type-safety is mentioned twice also. And that is in a spec which is 900 pages long and incredibly complex.

Metal overtly has statically checked memory safety via ARC, but the reality is that the IHV libraries will segfault in response to semantic mistakes, just like Vulkan. A big difference is that Vulkan has cross-IHV validation layers that catch most of these mistakes during development, and they're only getting more comprehensive. It's totally trivial to write a wrapper over Vulkan that fixes the type/memory safety of the C interface; it's not trivial to create a validation system of anywhere near the quality of Vulkan's for Metal.

Re:Ray Tracing with Metal [video] by flohofwoe on Sunday June 16, 2019 @02:38PM (#20197138)
From what I've seen so far, Metal's own validation layer also does very thorough checks, to a point where it almost replaces the documentation (as far as the quality of the validation error messages goes).
Re:Ray Tracing with Metal [video] by banachtarski on Sunday June 16, 2019 @05:46PM (#20198105)
> That said Vulkan is an unmitigated disaster, though less so than classic OpenGL. Any API which fiddles with void* in 2019 should be put right back in a box. Security is mentioned exactly twice in the entire spec. Type-safety is mentioned twice also. And that is in a spec which is 900 pages long and incredibly complex.

OK are you a graphics professional? Have you written renderers in Vulkan? Do you have any idea of what you're talking about? What "void*" pointers are you referring to? Are you aware that type-safety is very much a design goal of the API? Are you aware that the spec ships with a formal memory model which is a godsend for graphics engineers that had to deal with implicit guarantees in other APIs for years? I'm not someone that authored the original spec, but reading your comment is somewhat rage-inducing given how off-base it is.

Re:Ray Tracing with Metal [video] by leoc on Sunday June 16, 2019 @10:25AM (#20195589)
FWIW there have been one or two (apparent) Apple employees on here who seemed sincerely convinced that Vulkan was a mess compared to Metal. I have no idea how true that is or how much difference it actually makes, but there it is.
Re:Ray Tracing with Metal [video] by pjmlp on Sunday June 16, 2019 @10:39AM (#20195666)
Metal, nice OOP based tooling with several frameworks to support handling textures, fonts, materials, GPU live shader debugging, code completion on Xcode with static analysis, C++14 based shaders.

Vulkan, plain old C style API, full of extensions just like OpenGL, leading to several code paths, just the bare bones pixel drawing, go fish for random libraries for anything else, try your luck with RenderDoc or GPU specific debuggers, enjoy Notepad++ + UNIX shell style tooling support.

Re:Ray Tracing with Metal [video] by bilbo0s on Sunday June 16, 2019 @10:46AM (#20195701)
I believe this is a deliberate misrepresentation of the current state of affairs on Vulkan. Likely for the purposes of spreading disinformation about a specification that legions of smart, dedicated, hardworking engineers came up with after countless hours of debate and consensus.

I mean be real...

there is no way that any programmer who actually used Vulkan would find it as pleasant to work with as you imply in your comment.

Re:Ray Tracing with Metal [video] by pjmlp on Sunday June 16, 2019 @11:05AM (#20195808)
Here is the list of Vulkan extensions with device coverage.

https://vulkan.gpuinfo.org/listextensions.php

Clicking a bit around, gives the Vulkan support version per device, which on Android is a mess, unless one only cares about flagship devices.

https://vulkan.gpuinfo.org/listdevices.php?platform=android

Now regarding the tooling, since I am spreading disinformation, can you please provide us with the SDK tooling that matches the offerings from Apple, Sony, Nintendo and Microsoft, regarding their own APIs?

Because what LunarG offers is pretty bare bones, and the OEM SDKs pretty much just provide the basic stuff as well, with C samples.

I guess that someone that rather goes hunting for glm, uses sbt for textures, writes their own font rendering engine, compiles shaders from the command line, only knows about RenderDoc is capable of,... will feel very uncomfortable with the available set of Metal tooling and Frameworks.

And this is one of the best tutorials available for Vulkan beginners, https://vulkan-tutorial.com

Re:Ray Tracing with Metal [video] by johncolanduoni on Sunday June 16, 2019 @11:14AM (#20195858)
Most of the extensions are for what are currently pre-production or fringe features, and the WG showed they're not afraid of pulling important (and even not so important) extensions into minor version releases much faster than OpenGL has put things in core with Vulkan 1.1 (I was glad but honestly surprised that the cross-process resource sharing made the cut).

You're definitely right about significant parts of the toolchain being weaker. In particular sorting out how glslang -> Vulkan works in practice is pretty trial-and-error, and if you want to use HLSL it's even more poorly documented. You have to expect to be going through the Vulkan spec (which I will say is much easier than directly using the OpenGL spec). However the Vulkan validation layers are incredible, and leave the equivalents for Metal, DirectX, and especially OpenGL in the dust.

Re:Ray Tracing with Metal [video] by bilbo0s on Sunday June 16, 2019 @01:04PM (#20196532)
I think you missed the joke.
Re:Ray Tracing with Metal [video] by nothrabannosir on Sunday June 16, 2019 @03:49PM (#20197517)
It was a joke. Read the comment to the end.
Re:Ray Tracing with Metal [video] by johncolanduoni on Sunday June 16, 2019 @11:22AM (#20195896)
I think the supposition that pjmlp is knowing mischaracterizing Vulkan is both likely to be false and excessively uncharitable (and I say that as a big fan of Vulkan).

I think it's just a matter of not having had much experience with it. It is natural to look at the shape of the API and have PTSD about wrestling with OpenGL for the past few decades.

Re:Ray Tracing with Metal [video] by mrec on Sunday June 16, 2019 @12:12PM (#20196195)
I'm pretty sure the comment you're responding to is just a switcharoo-format joke. Unless the last sentence is missing an "un" before "pleasant".
Re:Ray Tracing with Metal [video] by johncolanduoni on Sunday June 16, 2019 @12:13PM (#20196204)
Yeah I assumed that was the omission but that makes a lot more sense lol
Re:Ray Tracing with Metal [video] by Reelin on Sunday June 16, 2019 @06:06PM (#20198220)
My understanding is that Vulkan is specifically supposed to be as low level as possible in order to facilitate device manufacturers creating new hardware and to give developers fine grained control over things if they want it.

I believe the stated strategy is to let third party middleware handle the higher level abstractions so that different approaches that appeal to different people can coexist. This also theoretically reduces driver complexity and thus (hopefully) bugs.

I have absolutely no idea if this is actually a good idea, or if it's working out in practice. In case anyone wants to poke around the ecosystem: (https://github.com/vinjn/awesome-vulkan).

Re:Ray Tracing with Metal [video] by derefr on Sunday June 16, 2019 @03:29PM (#20197400)
Okay, but none of that was true in 2014. If Apple had been building an ecosystem of Vulkan tooling instead of an ecosystem of Metal tooling, presumably Vulkan would have the frameworks, the Xcode support, and (maybe) some of the debuggability (since Apple could have their drivers' Vulkan shader pipeline target LLVM IR, and then do LLVM-internal stuff from there to enable debuggability.)

So what made Metal a better technical choice than Vulkan, back when the options were "Metal without Apple's support built yet" and "Vulkan without Apple's support built yet"?

Re:Ray Tracing with Metal [video] by pjmlp on Sunday June 16, 2019 @06:15PM (#20198270)
Being almost two years older than Vulkan.
Re:Ray Tracing with Metal [video] by daenz on Sunday June 16, 2019 @11:14AM (#20195860)
>seemed sincerely convinced that Vulkan was a mess compared to Metal

Oh god I hope not. I come from the API mess that was OpenGL over 3 major versions, and I was hoping all the lessons learned from that were applied to Vulkan.

Re:Ray Tracing with Metal [video] by thrower123 on Sunday June 16, 2019 @05:56PM (#20198163)
I think the lessons learned are being applied, but those are the lessons on how to maximize fragmentation.

Graphics APIs are not good when designed by committee.

Re:Ray Tracing with Metal [video] by mbroncano on Sunday June 16, 2019 @10:11AM (#20195516)
Although not an ideal solution, MoltenVK [1] does a great job at bridging that gap

[1] https://github.com/KhronosGroup/MoltenVK

Re:Ray Tracing with Metal [video] by tomxor on Sunday June 16, 2019 @10:05AM (#20195489)
Yes, I find it difficult to imagine developers that are enthusiastic about "metal", I mean who wants another platform specific API for graphics cards. If Apple really think we need something other than "vulkan" then they should push to make "metal" a competing open standard- But I doubt they think that, and It's quite easy to imagine ulterior motives, M$ had exactly the same motives.
Re:Ray Tracing with Metal [video] by flohofwoe on Sunday June 16, 2019 @02:41PM (#20197148)
I'm quite enthusiastic about Metal, and I'm not even much of an Apple fan. Compared to Vulkan or even OpenGL, Metal's API design is much more elegant and developer-friendly. It can be used just fine without a "sanity layer", which can't be said about Vulkan.
Re:Ray Tracing with Metal [video] by pjmlp on Sunday June 16, 2019 @10:41AM (#20195674)
All of us that rather use productive SDKs, with higher level languages, instead of a C API that only knows about drawing pixels.

The same devs that rather use DirectX, libGCM, libGNM, GX, GX2, NVN.

Re:Ray Tracing with Metal [video] by tomxor on Sunday June 16, 2019 @10:44AM (#20195692)
I am talking about principles of openness vs lockin, I am not personally interested in technical merits until I can depend on it existing beyond Apple's back garden.

My point was I am surprised others do not care about this aspect, you are obviously one example - So my question to you (as someone who values it technically) is: does this not bother you?

Re:Ray Tracing with Metal [video] by pjmlp on Sunday June 16, 2019 @10:52AM (#20195742)
APIs win on technical merits and market tooling, not on feels good kind of thing.

Not at all, as someone that learned to program graphics when demoscene was all the rage, it is all about taking advantage of the hardware.

Professional game studios are more than used to have a thin layer to abstract each 3D API, which is a very small codebase from any game engine/middleware.

Re:Ray Tracing with Metal [video] by tomxor on Sunday June 16, 2019 @11:05AM (#20195807)
> APIs win on technical merits and market tooling, not on feels good kind of thing.

Ok, but the technical merits for metal stop at Apple, you can abstract away differences in your translation layer if you care about your game existing outside, but you have to leave any merits of metal behind. Doesn't this dull your enthusiasm over improvements and features specific to metal?

I get that the original demoscene you were using unique hardware, and unportable demos that squeezed everything they could out of that specific piece of hardware felt natural, but Apple computers use the same GPUs everyone else is using... doesn't that make a proprietary low level graphics API seem more artificial.

Re:Ray Tracing with Metal [video] by pjmlp on Sunday June 16, 2019 @11:23AM (#20195903)
Not every developer feels like they have to support every computer in existence.

Many game studios are quite happy being Apple experts, just like many other game studios release exclusives or sell themselves as experts on a given platform, including selling consulting services.

For those, vendor tooling is very much appreciated.

The ones that care for portable code, they also care about having the easiest way to start coding on each platform.

If Khronos cares about adoption, they should improve LunarG SDK to be more than just a set of bare bones libraries.

Re:Ray Tracing with Metal [video] by tomxor on Sunday June 16, 2019 @12:07PM (#20196157)
So in short, to answer my own question: a developer can have enthusiasm for metal if metal covers all of their target platform (Apple).
Re:Ray Tracing with Metal [video] by frou_dh on Sunday June 16, 2019 @11:21AM (#20195891)
Their most important platform uses in-house GPUs these days.
Re:Ray Tracing with Metal [video] by frou_dh on Sunday June 16, 2019 @10:36AM (#20195647)
> If Apple really think we need something other than "vulkan" then they should push to make "metal" a competing open standard

Metal predates Vulkan by years. They were already using Metal in shipping products before Vulkan existed.

Re:Ray Tracing with Metal [video] by tomxor on Sunday June 16, 2019 @11:22AM (#20195894)
Why does that mean they shouldn't make it an open standard?
Re:Ray Tracing with Metal [video] by derefr on Sunday June 16, 2019 @03:32PM (#20197418)
"Metal" is a vertically-integrated software stack that goes up into Objective-C runtime land. An open standard based upon it would require that there be an open-standard Objective-C runtime and toolchain to use in working with it.

Unlike Vulkan, the lowest-level, C-ABI, non-type-safe parts of Metal aren't exposed as public APIs, AFAIK. You could maybe standardize those, but Apple presumably wants to reserve the right to change them while just keeping the higher-level ObjC ABI stable.

Re:Ray Tracing with Metal [video] by astrange on Sunday June 16, 2019 @07:42PM (#20198645)
> Unlike Vulkan, the lowest-level, C-ABI, non-type-safe parts of Metal aren't exposed as public APIs, AFAIK.

They don't even really exist. Most Metal APIs are defined as protocols (id<MTL...>) for a reason; if you look at the objects you get back, they're directly implemented by the GPU driver.

Re:Ray Tracing with Metal [video] by frou_dh on Sunday June 16, 2019 @11:32AM (#20195951)
cos randomers don't get to dictate the scope of the project after-the-fact
Re:Ray Tracing with Metal [video] by tomxor on Sunday June 16, 2019 @12:01PM (#20196122)
If "randomers" are developers who are repelled by the proprietary nature of their graphics API "randomers" may well dictate the scope of the project.
Re:Ray Tracing with Metal [video] by klum on Sunday June 16, 2019 @10:24AM (#20195581)
As someone pointed out, it probably has to do with controlling the stack all the way from hardware to userspace. Increasingly, Apples UIs run on top of Metal and I get the impression they want complete control, not just "good enough". Which makes sense, it's what makes Apple worth it for many people. I totally get the inconvenience from a developers (or gamers) perspective, though.
Re:Ray Tracing with Metal [video] by Const-me on Sunday June 16, 2019 @11:28AM (#20195928)
You can't adopt stuff which doesn't exist.

Apple was the first to release next-gen 3D API, Metal was released in 2014. Then came MS, DX12 was launched with Win10 in 2015. Vulkan was too late, initial release in 2016.

Re:Ray Tracing with Metal [video] by vetinari on Sunday June 16, 2019 @11:54AM (#20196085)
Metal 1.0 was ultra-limited; it was more MVP than anything else.

It was done exactly for the Apple to be "first". The initial Vulkan release was more comprehensive than Metal 2 in 2017.

Re:Ray Tracing with Metal [video] by bronxbomber92 on Monday June 17, 2019 @01:25AM (#20200158)
Metal 1.0 reflected the capabilities of mobile GPUs at the time. Apple is not in a race with Khronos.
Re:Ray Tracing with Metal [video] by vetinari on Monday June 17, 2019 @08:37AM (#20202248)
Yet you will find several comments on this same page, that Apple won the race.

Nowhere was mentioned, that Metal 1 and Vulkan 1 were not comparable by a long shot. Exacly, precisely because it was MVP focusing on specific mobile GPU.

Re:Ray Tracing with Metal [video] by knolan on Sunday June 16, 2019 @11:36AM (#20195976)
What about AMD’s Mantle?
Re:Ray Tracing with Metal [video] by Const-me on Sunday June 16, 2019 @06:05PM (#20198214)
I don’t think Apple could adopt Mantle. They needed a GPU API to spawn across PCs and phones/tablels. Phones & tablets earn them most profits i.e. more important for them, but mantle was a PC-only tech.
Re:Ray Tracing with Metal [video] by dmitriid on Sunday June 16, 2019 @04:22PM (#20197669)
Created by AMD and supported in only a subset of AMD's cards. Appeared in 2013 (so, a year before Metal, and by that time Apple had probably already invested millions in Metal), and abandoned in 2015.

So. What about Mantle?

Re:Ray Tracing with Metal [video] by knolan on Sunday June 16, 2019 @05:30PM (#20198022)
Mantle lead to Vulkan. Your point about Vulkan simply arriving too late for Apple is not as clear cut as you make it.
Re:Ray Tracing with Metal [video] by dmitriid on Monday June 17, 2019 @02:15AM (#20200353)
Someone else answered about Mantle/Vulkan/Metal timeline in a different thread: https://news.ycombinator.com/item?id=20200116

(Note: I in no way imply that you spread false narrative etc. It just happens that this linked comment is such a reply)

Re:Ray Tracing with Metal [video] by whywhywhywhy on Sunday June 16, 2019 @10:26AM (#20195593)
sorry at this point we need to stop wishing Apple would adopt standards or wishing Apple would stop reinventing the wheel in their own bespoke stacks and just support what we believe in elsewhere.
Re:Ray Tracing with Metal [video] by atq2119 on Sunday June 16, 2019 @11:15AM (#20195863)
Pretty much all of the major game studios already have Vulkan implementations for their engines because of Stadia, Google's game streaming platform. Obviously we've yet to see how much staying power that will have.
Re:Ray Tracing with Metal [video] by ksec on Sunday June 16, 2019 @10:41AM (#20195677)
Vulkan is on Android, Direct X is on Windows, Metal is on macOS and iOS.

I don't see anything wrong with it. Just like Windows did't adopt Vulkan. And that is assuming Vulkan is good in the first place.

And most of the gaming development are now done with Middlewares like Unity and Unreal. The way I see it, more and more people will develop with Middlewares in mind, those API won't be touched by a shrinking amount of developers.

Re:Ray Tracing with Metal [video] by leddt on Sunday June 16, 2019 @10:49AM (#20195718)
Vulkan runs on Windows.
Re:Ray Tracing with Metal [video] by tambre on Sunday June 16, 2019 @11:08AM (#20195831)
And Linux.
Re:Ray Tracing with Metal [video] by bronxbomber92 on Sunday June 16, 2019 @02:10PM (#20196957)
And macOS. And iOS.
Re:Ray Tracing with Metal [video] by master-litty on Sunday June 16, 2019 @02:50PM (#20197182)
Exclusively with the use of MoltenVK, which uses Metal under the hood...
Re:Ray Tracing with Metal [video] by grovesNL on Sunday June 16, 2019 @04:04PM (#20197593)
Not exclusively -- gfx-portability (https://github.com/gfx-rs/portability) is another option.
Re:Ray Tracing with Metal [video] by master-litty on Sunday June 16, 2019 @05:47PM (#20198114)
Wasn't aware of that, thank you!
Re:Ray Tracing with Metal [video] by thrower123 on Sunday June 16, 2019 @02:48PM (#20197173)
And anybody who is not a masochist and cares about compatibility across all those platforms will use Unity or Unreal or one of the lesser-known others.

DirectX 12 is the easiest of these APIs to use, and it's not exactly fun.

Re:Ray Tracing with Metal [video] by pjmlp on Sunday June 16, 2019 @06:30PM (#20198373)
Only on classical Win32 mode.
Re:Ray Tracing with Metal [video] by vondur on Sunday June 16, 2019 @10:14AM (#20195531)
Does any OS natively support Vulcan? Or do you get the drivers from a third party?
Re:Ray Tracing with Metal [video] by pjmlp on Sunday June 16, 2019 @10:43AM (#20195690)
Only Android, and on Nintendo Swift as 2nd tier API (1st tier is NVN).

Even on Windows, you need from get the drivers from OEMs, and they only work in old Win32 desktop mode, not on store/UWP.

It remains to be seen if Windows sandbox will allow for anything else other than DirectX.

Re:Ray Tracing with Metal [video] by syjer on Sunday June 16, 2019 @10:37AM (#20195658)
If you consider that window, normally use third party drivers (by amd, intel, nvidia) which bundle by default vulkan.

Linux distributions and the more recent android versions?

Re:Ray Tracing with Metal [video] by shmerl on Sunday June 16, 2019 @03:21PM (#20197350)
Pretty much every OS, except heavy lock-in oriented ones, where OS is controlled by some entity which prevents providing graphics drivers. In such case it's up to that entity to produce them, and in most cases their lock-in idea is against it.
Re:Ray Tracing with Metal [video] by Avamander on Sunday June 16, 2019 @10:17AM (#20195544)
Pretty sure AMD on Linux can do Vulkan with just second-party stuff.
Re:Ray Tracing with Metal [video] by shmerl on Sunday June 16, 2019 @03:23PM (#20197358)
AMD hardware has two drivers on Linux, radv by Mesa and amdvlk by AMD themselves. Not sure what you call "second party", but both are very competitive today.
Re:Ray Tracing with Metal [video] by ken on Sunday June 16, 2019 @01:41PM (#20196790)
The "second party" is the user. I don't think any users are writing their own Vulkan drivers.
Re:Ray Tracing with Metal [video] by Avamander on Sunday June 16, 2019 @08:38PM (#20198874)
My mistake, thought about from the user perspective.
Re:Ray Tracing with Metal [video] by auggierose on Sunday June 16, 2019 @10:10AM (#20195514)
Given they make their own hardware, it makes sense to push their own standard, especially with the kind of market penetration they have. Now if it would only be possible to run Metal in the cloud ...