3 ms·
Are there any signs of this souring? During the PPC-Intel transition, Adobe compatibility was almost a running joke. Along the lines of the infamous "You can
by soneil 2y ago
Are there any signs of this souring?
During the PPC-Intel transition, Adobe compatibility was almost a running joke. Along the lines of the infamous "You can always count on [..] to do the right thing, after they have exhausted all the other possibilities] quote.
I was surprised at how quickly Adobe adopted aarch - it didn't feel sour.
- wtallis 2y agoMy recollection is that Adobe was slow to migrate from 32-bit to 64-bit x86 because they were still dependent on many of the Carbon APIs (Mac OS 9 compatibility) and those APIs weren't carried over to 64-bit. They dragged their heels about transitioning to Cocoa (NeXT derived) APIs for their UI, and it showed.
- WillAdams 2y agoIt still kills me that Altsys/Aldus/Macromedia let their NeXT codebase for Altsys Virtuoso whither (v2 was essentially Freehand 4 w/ a couple of unfixed bugs) so that when Rhapsody was announced they weren't ready for it. In some other timeline, I am using a Mac w/ a current version of Macromedia Freehand running on Rhapsody and I am a _much_ happier person. As it is, I'm about to give up on interactive vector drawing and just code everything either using METAPOST or OpenSCAD, or some mix of both.