[Bill Davis] "If its true that the very first decision was to "zero out" the existing code base and write on an entirely new foundation - re-examining every design and implementation decision in light of where the hardware, software, and even the market has evolved - then it has to be fair to allow the same amount of time for this code base to evolve and stabilize that all other programs have needed to mature."
I don't really get the concept of it "being fair to allow the same amount of time." It is perfectly fair to reject the software for its immaturity. Apple chose to trade maturity (and everything that comes with it) for a new architecture (and everything that comes with it).
Also, remember that Apple allowed FCP7 to get crufty in the first place. While FCP7 was still throwing KGCore errors (Key Grip!), Avid had written Media Composer piece by piece and Adobe had rewritten Premiere Pro twice.
My clients expect me to improve myself on my own time. I'd be punished in the marketplace if I started offering less tomorrow than I do today with the promise of more next year -- and I'd deserve it.
[Bill Davis] "This constant need to compare X to Legacy and lament the change (talking of others here, not you.) is understandable - but getting old."
Likewise, I feel the constant comparison of FCPX to FCPv1, while interesting in terms of history, is off-target in terms of practicality. None of us (Apple and its competitors included) are in the same positions we were in back in 1999.
Also, FCPX is simply not competing against FCP1. It's competing against Premiere Pro, Media Composer, maybe Edius, Vegas, and Lightworks, and existing seats of FCP7. FCPX is rightfully compared to any of these products as they exist today, not their launch versions.
For those who need features or workflows that FCP7 supported and FCPX does not, Apple has taken two steps backward and one step forward. Ostensibly, Apple plans to take additional forward steps in the future, and it may be exciting to think about how far they may go. That said, looking at FCPX practically as it exists today, it's still just one step backwards.
[Bill Davis] "I'm simply saying that after this long, those remaining fixated on what Legacy "used to be" are in danger of getting stuck in the past. Someone experiences an unwanted divorce and yes, grief is natural and accepted. Maintaining the shrine in the back bedroom and visiting it daily - once inevitability is fully established - is a sign one is having trouble moving on."
I half-agree with this. FCP7 is a dead platform with no future, and I think it's foolish to build a business on a hopeless platform.
On the other hand, some editors have a very good reason to stay with FCP7 for the time being -- it does have some unique features and strengths, and it may help them provide value to clients and earn money better than anything else on the market.
Walter Soyka
Principal & Designer at
Keen Live
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
RenderBreak Blog - What I'm thinking when my workstation's thinking
Creative Cow Forum Host: Live & Stage Events
