sigh
Once upon a time, the Mac was a great development platform...
sigh
Once upon a time, the Mac was a great development platform...
Node is my current dev environment of choice, but I'm mostly doing service level things or web-based applications. So it fits well for that use case. Of course it also shapes my choices if I did do desktop stuff as I'd more likely reach for ReactNative or Electron. Even if I'm very interesting in getting my feet wet with go and rust.
It still is.
XCode, Cocoa Frameworks, Swift, Objective-C, Instruments are there and doing great.
I don't care one second about UNIX underpinnings.
More vendor lock in on Apple platforms is hardly needed nor a positive thing.
There's a Vulkan-on-Metal implementation[1], and I'd have absolutely no complaints about the platform if there was simply an open source equivalent (well, maybe geometry shaders).
The biggest hurdle I can think of is geometry/tesselation shaders. Newer versions of Metal support tesselation shaders, but they work rather differently than Vulkan's (they're based on a compute shader, instead of the Hull/Domain split other APIs use). Geometry shaders aren't supported at all.
Most people doing graphics have to implement an abstraction layer anyway for handling DirectX, vulkan or old OpenGL.
Once you have it, it is not so much work adding one additional back end.
I now believe competition is great and one of the things that made Europe for example to prosper while China stagnated for 5 centuries.
If you say for example: "We only support text shaders because it is simple and works well enough" and someone else uses and API or DOM and it goes 200 times faster, I want the option to let the first guys down and pick the 200X improvement version, not having to stand the original "because it is the standard and we don't care".
Yes, it is. I would have been able to develop Pathfinder a lot faster if I didn't have to write and debug the "compute-shader" abstraction.
> If you say for example: "We only support text shaders because it is simple and works well enough" and someone else uses and API or DOM and it goes 200 times faster, I want the option to let the first guys down and pick the 200X improvement version, not having to stand the original "because it is the standard and we don't care".
Vulkan exposes more of the hardware than Metal does. Having separate tessellation evaluation/tessellation control shaders is important to the way that Pathfinder works.
It's one thing to have a vendor-specific API that's better than the standard. It's quite another to have a vendor-specific API that's worse...
This basically sums it up regarding my lost years with OpenGL.
If anything, Apple needs competition with themselves. There's no route to a modern graphics API on macOS (or iOS for that matter).
Vulcan is unsupported
Where? Windows, Linux, Andriod, Intel, AMD, and Nvidia have rolled out supportApple is the only people who haven't because of Metal.
Windows support is done by GPU vendors, not Microsoft and is only supported on Win32, not UWP applications.
Sony doesn't plan to support Vulkan, PS* APIs are much better.
Nintendo did introduce support for the Switch, but they are so confident on it, that they also have NVN, which offers much better control over the hardware.
> NVN, which offers much better control over the hardware.
Can you cite specific reasons? Vulkan is about as low-level as you can go.
https://blogs.nvidia.com/blog/2016/10/20/nintendo-switch/
"NVIDIA additionally created new gaming APIs to fully harness this performance. The newest API, NVN, was built specifically to bring lightweight, fast gaming to the masses."
The rest is behind the SDKs NDA.
They've gotten partway there with things like D3D12 descriptor heaps, but hardware-specific APIs just don't have those limitations.
It isn't cross-platform, so it lacks the most important of all of Vulkan's features.
However, I can't help but seeing it modeled on the Direct X vendor lock-in model that starved Apple of games (and users because of those games). While it may not be a sign of change in Apple, it is a sign to me I shouldn't depend on them to provide products that meet my needs as a cross-platform developer. All those years I invested in a neglected OpenGL I should have devoted instead to directx; perhaps I would be less bitter now.
But from the documentation, it looks like quite a nice and simple API that also exposes the modern capabilities of shaders. It would probably make a great base for a new webgpu API.
This existence of Metal isn't really an issue. The real issue is that apple has silently shifted to a mode of only supporting Metal, not implementing vulkan and neglecting opengl.
Like this?