15 years on and developers are in a very different place, mostly with modern code using apple tools etc. Which was just as well as Adobe really dragged their feet in getting their code ported. I remember back in 2006 when this was happening, things like MS word/Excel and the likes of Adobe Indesign, ran better on the Intel Mac via Rosetta than they did natively one the PowerPC. Rosetta, the rather cleaver Apple tech they very successfully used in the PowerPC to Intel transition that enabled PowerPC apps to seamlessly run on the new Intel based machines, is back for this transition in the form of Rosetta 2. Do they sell enough on the Mac to justify a team of engineers etc. That then becomes a management decision for resource allocation and cost/benefit. At a glance though, the way the UI appears, and buckets of code fragments that litter around with the install, my guess is no, and some considerable rework on their behalf will be required (to me, Fusion feels like a bare min port of the Windows code base).
If the Mac version is based on modern Mac frameworks, and they are all in with the 'Apple way', then I suspect the port over will be relatively straightforward for them. Things like OpenGL dependancy etc, which apple really are not supporting, and for good reasons, it's had its day.
How much legacy code is in there, what tool sets they might be using, and how much generic, lowest common denominator code, they have that is shared between the various platforms they sell to. I guess the timing of a transition for Fusion may depend on several factors.
0 kommentar(er)
