2 ms·
I do see the problem with it not being Cocoa. The thing is, I also see a problem with throwing out huge swaths of your existing, mature codebase to make a minor
by chc 15y ago
I do see the problem with it not being Cocoa. The thing is, I also see a problem with throwing out huge swaths of your existing, mature codebase to make a minor project superficially nicer. They're both real problems, and which matters more to you depends on how strongly you adhere to the philosophy that "real artists ship."
When the iPhone came out, it didn't have cut and paste or any third-party apps. When OS X came out, it didn't even have DVD playback or CD burning and it was agonizingly slow. All of those decisions were far more "perverse" than leveraging an existing codebase to bring a new product to market. OS X as it exists today is the product of countless iterations on the promising-but-lousy OS X 10.0. To miss that fact is quite literally to miss what made OS X so great.
- frou_dh 15y agoI agree that this makes business sense for JetBrains. AppCode is clearly never going to be iterated in to a good Mac app without a rewrite.