3 ms·
"Electron, .NET, Java" so you're skipping over Win32, which has to be the largest slice of all. Photoshop falls into this bucket. It's on the C++ side and does
by Eric_WVGG 6y ago
"Electron, .NET, Java" so you're skipping over Win32, which has to be the largest slice of all.
Photoshop falls into this bucket. It's on the C++ side and does "some funky things" in the way of SIMD to eke out more performance. If memory serves, it took them about eighteen months to get an Intel native version out the door after the PPC/Intel transition started.
Any serious audio apps are going to have an equally hard time, they do a lot of hardware tricks in order to lower latency, and since they're not mainstream apps like MS Office or Adobe CS, they have much smaller teams of developers. That whole industry is very slow moving.
Finally you've got CAD and 3D stuff. Obviously that requires good drivers. In fact, that's another way in which Microsoft will have a much harder time with this transition. Apple only has to write a driver for the one audio device that's in every Mac, the one GPU, etc.
- nicoburns 6y ago> Photoshop falls into this bucket. It's on the C++ side and does "some funky things" in the way of SIMD to eke out more performance. I wonder how much of that codebase is shared between Windows and macOS though. It's quite possible that Microsoft could take advantage of a lot of porting work that has already been done for Apple's M processors. If you support Windows/x86 and macOS/arm then it's probably not much more work to create a Windows/arm port. Unless there are compatibility issues with the Win32 APIs themselves?