So you are left with not-perfect cross-platform choices:
And you don't really want to spend money to help people migrate off of your own platform onto a competitor's. Then there's the issue that these APIs on OSX can be brittle and Apple isn't very good at backwards compatibility, so you get to redo your hacks with every major release (and sometimes minor release and hotfixes), racking up a high maintenance cost.īasically, it's a tremendous amount of money and work for very little gain on a platform whose owner would be against you doing it anyways.
Of course, there's not going to be a nice clean mapping, so you also have to write hacks upon hacks to get it functioning exactly the same. While some things are fully managed and would not require porting, most things are wrappers around the Win32 API (windows, controls, gdi+, cryptography, active directory, COM, enterprise services, device access, sound, video, codecs, winforms, etc, etc).Įvery single one of these would have to be abstracted in the backend and remapped to equivalent native libraries on OSX. You spend hundreds of millions of dollars and several years porting.
The best answer is probably that you don't 'just support'.
