However, even though its unpopular for many reasons, Metal is a very good compromise as a starter API. It's design is very close to Vulkan/DX12, but its complexity is much lower. It can even be said to be less complex than OGL in the way that memcpy is less complex than glSubBufferData.
No, I'm bit familiar with OpenGL, again not at the level of graphics-pros, more like overall knowledge, and my DX knowledge goes pretty much to DX8 or DX9, but instead of learning DX11 or 12, I think Vulkan might be a better choice.
I've returned my company laptop week ago, as I left it, and now I'm stuck with my chromebook + crouton, looks like Vulkan is good there (almost).
I certainly don't want to get stuck in Metal.
I wrote up a recommended path from nothing -> OpenGL -> Vulkan here https://www.reddit.com/r/GraphicsProgramming/comments/6hcri4...
I honestly haven't worked with Vulkan yet, but I hang out with pros from different companies who do and they complain about Vulkan a lot. A whole lot. Part of it is that it is very difficult even for pros to avoid undefined behavior and timing issues. Another is that the only semi-solid shading language front-end for SPIR-V is glsl. Lots of people prefer to work in hlsl and really would like to see Metal's shading language everywhere.
This article is literally advocating the opposite. 'So how did I finally break through that wall of understanding? ... "But Vulkan is the hardz" I hear you saying. "Shouldn't I start with something easy like OpenGL?" Emphatically I say NO.'