1) Does XCode crash at least once a day the way Visual Studio 2005 does?
2) Does XCode refuse to bring up Interface Builder for a certain screen, citing some cryptic object instantiation message, either when code has not been rebuilt before bringing up these classes, or perhaps even when the code has been rebuilt, seemingly for no discernable reason whatsoever, the way the Visual Studio 2005's Designer does?
3) Does XCode go ahead and recompile a bunch of code anyway, even after prompting you, when you try to run, if you want to rebuild code, and you answer No the way Visual Studio 2005 does?
4) Does XCode go off and daydream while you are trying to scroll, or trying to bring up an information tab which scrolls painfully slowly in order to open, stopping at several points for no visible reason whatsoever, the way that Visual Studio 2005 does? (probably because VS 2005 is primarily a single threaded application and can't take advantage of that 8-way Mac Pro you just bought)
5) Does the code database feature of XCode often disclaim that it has no information about a routine or type on code that just compiled, or when you go to the definition of a routine take you to an identically named routine in a different file the way that Visual Studio 2005 does?
6) Does the routines menu in XCode often take 10-20 seconds to open up the first time for a file, sitting there doing nothing and giving you no indication that it even is responding to your click the way that Visual Studio 2005 does?
6a) And when the menu finally drops down, does it immediately hide itself the way that Visual Studio 2005 does?
OK, I could go on and on and on. I use Visual Studio 2005 for mixed C++ / C# development of an application containing 3 million lines of code. XCode is way better in so many ways.
The secret is that Microsoft doesn't use Visual Studio internally to develop their products. They use command line tools and text editors. Apple, on the other hand, uses XCode to develop MacOS X and the other applications. It really shows.
by Bill Coleman — Apr 12
1) Does XCode crash at least once a day the way Visual Studio 2005 does?
2) Does XCode refuse to bring up Interface Builder for a certain screen, citing some cryptic object instantiation message, either when code has not been rebuilt before bringing up these classes, or perhaps even when the code has been rebuilt, seemingly for no discernable reason whatsoever, the way the Visual Studio 2005's Designer does?
3) Does XCode go ahead and recompile a bunch of code anyway, even after prompting you, when you try to run, if you want to rebuild code, and you answer No the way Visual Studio 2005 does?
4) Does XCode go off and daydream while you are trying to scroll, or trying to bring up an information tab which scrolls painfully slowly in order to open, stopping at several points for no visible reason whatsoever, the way that Visual Studio 2005 does? (probably because VS 2005 is primarily a single threaded application and can't take advantage of that 8-way Mac Pro you just bought)
5) Does the code database feature of XCode often disclaim that it has no information about a routine or type on code that just compiled, or when you go to the definition of a routine take you to an identically named routine in a different file the way that Visual Studio 2005 does?
6) Does the routines menu in XCode often take 10-20 seconds to open up the first time for a file, sitting there doing nothing and giving you no indication that it even is responding to your click the way that Visual Studio 2005 does?
6a) And when the menu finally drops down, does it immediately hide itself the way that Visual Studio 2005 does?
OK, I could go on and on and on. I use Visual Studio 2005 for mixed C++ / C# development of an application containing 3 million lines of code. XCode is way better in so many ways.
The secret is that Microsoft doesn't use Visual Studio internally to develop their products. They use command line tools and text editors. Apple, on the other hand, uses XCode to develop MacOS X and the other applications. It really shows.