Phanfare Blog - Latest Comments in Xcode vs. Visual Studio

Re: Xcode vs. Visual Studio

mike — Fri, 03 Jul 2009 06:01:59 -0000

i think documentation is ok, in fact apple has solid documentation which i prefer to that of microsoft because of conciseness and to the point attitude. with the other points i agree

Re: Xcode vs. Visual Studio

mike — Fri, 03 Jul 2009 05:55:45 -0000

Let the truth about macs be told. I prefer macs to windows machines, but why apple cant just make a good developer tool?
XCode is standing next to the another free app; never mind the usability with multiple windows and the fact that i cannot simply go back (even vim can do it!) in code - debugging is a pain (C++) and 'fix and continue' feature simply never worked for me!

visual studio overall is the best ide, though i am not a typical ms fan.

Re: Xcode vs. Visual Studio

Teddy — Sat, 27 Jun 2009 12:27:23 -0000

I agree with the article. But let me add some comments.

In my opinion the whole difference is not about philosophies. It is more about the workflow.

The workflow to create something in VS is far much better. Debugger is slick, fast and reliable. MVC could have been automated to some level (like in VC++).
However some people claim that the maintenance of the code in XCode is easier. I cannot comment it since most of my time I create something. It is very seldom when I have to maintain some old code and recreate the GUI.

Re: Xcode vs. Visual Studio

Charles — Tue, 07 Apr 2009 03:21:07 -0000

Great discussion!
I started using XCode only for iPhone app development as it's so hot. The IDE truly hinders my productivity, mainly lack of IntelliSense, poor documentation, IDE Window layout, etc. that need major improvement. Even Interface Builder can do much better job. The UI concept may be different or better, it can still make it more ease of use while keeping the underneath generated code in the way to adhere MVC that should make the code more maintainable, but not with compromise of code creation.

Re: Xcode vs. Visual Studio

Thaurin — Tue, 16 Sep 2008 04:04:21 -0000

The main thing that I love about Xcode and hate about Visual Studio is indeed the performance. Visual Studio (as well as SQL Server Management Studio) drags and it often frustrates me when I have to wait for the UI designer to load *again*. I don't know what happened, but somewhere along the line, Microsoft made its UI code bloated.

I agree that the multi-window approach is an acquired taste. It is basic NeXTSTEP UI philosophy, as far as I can tell. It's much more prevalent on UNIX systems and you have to get used to it if you're not.

I'm also a .NET developer, but I guess I'm saying that Xcode deserves a fair chance.

Re: Xcode vs. Visual Studio

Michael — Fri, 18 Jul 2008 08:43:10 -0000

Nice post, but I don't agree with all points :)
VS is a very good IDE, you are right, IntelliSence and and screen layout is extremly good and easy to use. I'm .NET programmer and like it very much.
But VS is a windows application, it fits the OS with it's office etc. I guess, most of you guys are also programmer for windows, so you are used to the windows os concept.
So it's quite hard to compare it with an IDE of MAC. Apple's OS has a completely different GUI concept than windows. So you guys look at the apple IDE and complain that it's not like your are used to, a bit to short look on a product right?

Julian complains the Interface Builder is not intuitive. Can be, if you are not used to. Have you ever heard abput MVC?XCode completly separates code and GUI. Look at VS and you find the greatest mix between GUI/Code/Business Logic. So again a completly different concept!

On the other hand, the IntelliSence from VS is really top, and XCode is no match for it, with that I agree!

The main thing I don't like on VS is the performance. VS can drag down the whole OS just while opening a Solution (just u few XML files......)

Re: Xcode vs. Visual Studio

Joseph — Thu, 24 Apr 2008 07:02:21 -0000

Eclipse is a java IDE. Having used eclipse and vc++ 6/7 extensively they're really 2 different beasts. For C/C++ programming VC is amazing. I hate to tip my hat to anything that Microsoft puts out, but if there's one thing MS has done well - it's the vc++ IDE.
There are alot of nice features in eclipse - the plugin system by far is the best feature allowing you to plugin database browsers for example - something you cant do in vc++. However, overall it's interface is not as intuitive and it's debugger is not even close to vc++. Vc's ability to do stack traces, mouse over of variables to get current execution variables, etc. is very valuable. My one complaint with vc++ is it's annoying ability after version 6 to link Microsoft specific CRTs to any app that it builds (which is why vc6 is still floating around...)

Re: Xcode vs. Visual Studio

Moja — Wed, 16 Jan 2008 18:20:59 -0000

You know what, Xcode is stupid. Visual Studio is a way better than that IDE.

Re: Xcode vs. Visual Studio

Jasper Bellentree — Wed, 24 Oct 2007 19:18:59 -0000

That last bit os just baloney. Xcode apps are build with gcc which is as robust a compiler as Microsoft's, perhaps better, although the Intel compiler is best of all.

I too much prefer Visual Studio too Xcode, but it's all bout the IDE, not the quality of the build output. Also, I've seen plenty of stack traces deep in MS code so I don't see any difference on that front.

Re: Xcode vs. Visual Studio

Julian Brown — Fri, 07 Sep 2007 07:11:17 -0000

Perhaps it's an unfair comparison becuase Visual Studio costs $$$ while Xcode is essentially free but in my opinion VS is in another universe compared with Xcode. Apart from problems with Xcode already mentioned here, how about the following:

1. Debugging in Xcode is a pretty painful experience because (a) it's highly prone to crashing for no good reason, (b) you can't see variable values by hovering the mouse cursor over the code as you can in VS, (c) the default key bindings for stepping thru code are totally bizarre (you have to press three awkwardly placed and unmemorable keys simultaenously to step forward one line - unlike VS which uses F10 and F11 - don't tell me about changing the keybindings - that didn't work properly when I tried it.

2. The Interface Builder - is a pretty ghastly add-on to Xcode becuase (a) it's not really integrated into Xcode and (b) it's totally unintuitive in the way you connect up controls to the code. You have to do all kinds of weird stuff from adding lines of code in a header file and dragging the header file over the Interface Builder app to drawing connector lines while you hold down the shift key from the the UI panel to some other window. In VS on the other hand everything is so much simpler. You simply drag a control from a toolbox onto your form and click the control and voila VS adds event handler code for responding to button clicks, combo drop downs and so on. No fuss no muss.

3. VS built apps seem far more stable compared with app built in Xcode. Xcode apps seems to crash for all kinds of weird reasons - it's often very difficult to figure out why an Xcode app crashes especially when you look at the stack trace and see the thread that failed was one that was executing code deep inside one of Apple's Frameworks. In VS, however, a crash is much more likely to originate in your own code and the chances are the stack trace will point you to the source of the problem directly.

4. .NET code is so much nicer than Objective-C but that's another stpry ...

Re: Xcode vs. Visual Studio

Sultan — Thu, 21 Jun 2007 22:36:23 -0000

Xcode is fine if you know how ton use it.
Xcode-Preferences-General-Layout : All In One
That might help you :)
It pays to read release notes

Re: Xcode vs. Visual Studio

Fabian Lidman — Sat, 16 Jun 2007 07:05:26 -0000

I agree with most of what you say. However, if you use Exposé (one of the best features of Mac OS X) to get a birds-eye view of all those different windows in Xcode, it quickly becomes more mangeable. I often find myself needing to keep multiple source files open to read and compare, and just switching back and forth between them in Exposé feels way faster than clicking a tab.
Also, build results and console output can be hidden behind the source code while you are editing it, and then quickly accessed using Exposé when you run the project. Better for concentration. :-)

Re: Xcode vs. Visual Studio

Sumanth Peddamatham — Tue, 13 Feb 2007 12:44:39 -0000

Leslie beat me to it, but thanks for the great writeup!