I understand the frustration when an OS doesn’t have the features you use in an upgrade, I’ve been there myself.
My comment is really aimed towards the OS versions we are likley to support. There has not been a decision yet on which these are, so don’t read into it too much. We want to support as many users as we possibly can - but it is fair to say that we’ll be making sure it will run on the latest versions of macOS.
In short: Jumping to another OS is a big move for us. Jumping to another OS on a different architecture is even bigger.
We still need to tackle many of the same challenges for both, so it makes sense for us to bring it to as many users as possible.
Comparing against Wine isn’t really something we’re doing right now, mainly because we would be comparing Metal against a DirectX 9 codepath.
We also don’t have a number of optimisations in place right now: both on the rendering side, and for the rest of the client code. That will come in time 
It’s fair to say that we are aiming for parity with the Windows DX11 client in the future.
There is some assembly kicking about, yep, but it’s not just that. There is a number of areas in not only the codebase, but the systems around it that will need to be adjusted. Getting the native Intel based client working is a huge step towards the Apple Silicon version though.
I hope to do a devblog with some more details in the future.
Hi folks
We have just posted the exciting news that we have been working on a native Mac client over on our news page.
I have started this thread to discuss the news. I will try to answer questions where I can, but as development is ongoing, I will not be able to answer everything.
Here are the answers to a few common questions that I expect to come up:
Q: Why a native client?
A: The native macOS client w...
Read more
devtrackers.gg
