Single Status Update
You kids and your damn object-oriented virtualized sanitized BDSM languages and APIs:
Incidentally, although Final Cut Pro X has been fully rewritten as a 64-bit Cocoa application, it was missing a significant number of features found in the discontinued Carbon version.
Everybody's forced to upgrade to the 'newest thing' but the newest thing is too much of a fuckin' pain in the ass - so slow, so abstracted, so bothersome, so bloated, so Brobdingnagian - that when something finally does get rewritten, it's a half-assed shell of what it once was.
Respect your elders. We wrote assembly on bare metal and instructed the machine in its own language. But our programs worked and did not sacrifice functionality for gloss or hipster bullshit like social media integration - the program WAS the functionality. And we sure as hell didn't pay $100 a year to kiss the ass of some self-proclaimed god of the platform for the right to code, and our programs didn't ship as encrypted, signed, DRM'd interpreted bytecode either.
Actually, I'm being (mostly) sarcastic/facetious/cantankerous for the sake of it ;)
- Show previous comments 2 more
May be besides the point, but Apple code is still native, it would be dumb to use layers of portable bytecode when their code is designed to run just on some types of computers; FCPX was probably dumbed down just to be cheaper. I don't have first-hand experience with it though. All this (about professional Mac users having less and less choice) is a big can of worms that's better treated on Mac forums.
- Show next comments 6 more