3 ms·
but for something that Apple uses in house to build pretty much all of their software products how can it be this bad? Probably because the Xcode team
by aaronbrethorst 11y ago
but for something that Apple uses in house to build
pretty much all of their software products how can
it be this bad?
Probably because the Xcode team doesn't dogfood their own tools. I forget exactly when and where this was, but I once talked to someone who interned on Xcode. He stated that almost no one who worked on Xcode actually used it, and most of them were, instead, vi users. Grain of salt, and all that, but it certainly fits.
- ians 11y agoIf true that makes a lot of sense.
- _RPM 11y agoWhy does that make a lot of sense? I'm curious.
- kitsunesoba 11y agoThat’s funny if true, because I’ve heard that other parts of the company dogfood to an extreme extent. As a sidenote, I’m rather surprised that there’s no open source Cocoa IDE aimed at Apple platform development. TextMate 2 would make for a great starting point, covering the source editor and file tree portions. LLVM provides all of Xcode’s syntax coloring, error checking, etc, so that’s taken care of too. The three big pieces that’d need to be written are XIB/Storyboard editing, project editing (clang flags, code signing, etc), and integration with clang, iOS simulator, etc. It’s a big project for sure, but far from insurmountable. If it’s written with Obj-C/C++ and Cocoa/Foundation, many of its biggest users would also be its best contributors and the project could go far quickly.