Having spent ~1hr getting acquainted with the MoltenVK SDK, I have to say that it’s quite straightforward to use, if verbose (because Vk). Here’s a cheeky little cube (3.2kLOC):pic.twitter.com/oCVYJmaqfv
-
3.2kLOC?!! Wtf! Even allowing for a lot of “pointless, but doing it by the book” code, thats… a lot past a lot. Comparison: My entire Metal-based IDE with UI, multipass rendering and such is 2,755 LOC.
It’s just this with all of the platform-specific stuff stripped: https://github.com/KhronosGroup/Vulkan-LoaderAndValidationLayers/blob/master/demos/cube.c … I think it could be tersified down to, perhaps, 700 LOC, but not much less.
-
-
Would be interesting to see how far it can be squeezed. Be surprised if it can’t be done in ~20 lines in metal. Doesn’t give me much faith in VK, its giving so much extra scope for bugs and performance issues to creep in :(
-
It’s ~75 lines in Metal if you lean on MetalKit and Model I/O. That’s without golfing down to the bare minimum.
-
10:1. To me, a good API is clear and concise. Vulkan is failing very hard at concise :( Which tends to have a negative effect on clear too. Then again, it shows how nice Metal is!
-
Turns out 700 was overly optimistic. I was able to whittle it down to about 1500 sloc: https://github.com/warrenm/HelloVulkanMac/blob/master/HelloVulkanMac/Renderer.m …
-
Oof. I can see there being some benefits, but imagine your productivity levels, trying to code something non-trivial like that!
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.