We're definitely on the lookout for what will replace FCP.
X wasn't even about a preference of using it in a professional workflow- at first it absolutely COULDN'T be used in a professional setting. Things like OMF/EDL/XML import/export, sharing projects, no limitations on file/scratch/network locations, professional external monitoring support (no, not just another computer monitor, but actual video out to broadcast monitors) individual track export, full support for third party plug-ins/hardware like Blackmagic, etc. etc. etc....
These are all things that can't just be "Aw shucks, I'll just wing it without that." It simply meant the application was unusable in a studio setting. People aren't just editing in a vacuum, everything is part of a workflow that involves integration with steps before and after the edit phase. When X first came out, it was like it was designed by kids who'd never set foot in an actual edit bay; it was a bad joke to even call it Final Cut Pro at first. The iMoviePro label it got slapped with by frustrated pros that just witnessed Apple puke all over their careers and tool of choice was well-deserved.
Yes, I understand they've come along way since to bring in a lot of the professional features back, but I hear it's still not on up to snuff for many pro settings. Apple blundered just enough by sending a message that "We don't care about you" to professional editors, that they'd rather make apps for people to do standalone YouTube videos with. The ball had to start rolling early for people to plot a replacement strategy- a production can't wait around for Apple or anyone else to get its crap together. So many studios have already looked into or are now implementing a switch to Avid, or Premiere (CS6 was actually far better than I thought it would be, including complete import ability of even the most complex FCP7 files) or whatever else.