Office on iPad Pro

<blockquote><em><a href="#359560">In reply to rob_segal:</a></em></blockquote><p>The other problem is a lot of that legacy code is in Assembler. That was one of the reasons that it took so long for Office for Mac to transition to an Intel based codebase. A lot of the VBA and macro code, and functions, especially in Excel, were written in PowerPC assembler on the Mac and vast swathes of it had to be re-written for Intel.</p><p>I'm guessing it is the same on Windows, that a lot of the code is in assembler, that is a lot of work to convert to a new architecture.</p><p>This is probably one of the reasons why UWP is/was also taking so long.</p><p>It makes much more sense to re-write it with managed code than to try and convert it, but it also means that it comes across to new platforms piecemeal. So that basic formatting will get there quickly, but full automation, VBA etc. will take a very long time to appear.</p><p>I don't know what Adobe have done, but given the lethargic mess of legacy ridden code that was Photoshop, I would assume that, although they are claiming it is fully featured, they actually have re-written it for iOS, again, I doubt the devs had waded through 30 years of assembler subroutines and ported them to ARM – does Apple even allow direct assembler in their code for iOS? I think probably not.</p>