C# vs Objective-C – Part II

Just some quick thoughts to wrap this up:

.NET vs. Cocoa

Hierarchy & Readability

I didn’t realize how much I loved Microsoft’s hierarchial implementation of the framework until I started using Cocoa. Which one of these is more organized and intuitive to get the current date?

//C#
DateTime dt = DateTime.Now;

//Objective-C
NSDate *today = [NSDate date];

Without reading any documentation, I wouldn’t think that the date method of NSDate was the current date. It’s little things like this that I really like in .NET.

Community

This is completely not scientific, but I get the feeling that the .NET community has a larger amount of forum q&a than Cocoa–this would obviously be reasonable to assume given the Microsoft vs Mac share of the PC market. Just a little annoying since most Google searches of .NET problems have solutions in the first several results.

Visual Studio vs. Xcode

Events vs. Outlets/Actions

Yet again, I might be biased since I started out with .NET first, but I just think the list of events that the Visual Studio interface provides (e.g., when a user clicks, when the user hovers) is more intuitive than Xcode’s outlets since you simply have to double-click on the event name and the method is automatically created, and more importantly, already bound.

I have since gotten used to Outlets (relatively), but I still think it’s much more intuitive the way Visual Studio and .NET do it.

[Edit] This guy makes some good points as to why the Cocoa way of doing things is better, i.e., it fits the MVC model.

Advertisement