Update: After giving some though to one of the responses to this entry below, I have decided to take down the email thread between Jobs and myself. I have no way of knowing if Jobs would be OK with me posting the e-mail publicly, even though the contents of the e-mail didn’t contain anything private or sensitive.
That said, I’d like to turn this entry into a discussion of what people think of having to use Objective C to code Cocoa applications. Feel free to comment below. Here is my take on the subject: “Although I am a die-hard Apple and OSX fan, I’ve never cared for Objective-C much. As far as the development world is concerned, it is my opinion that Microsoft has done wonderful things with .NET, while Apple hasn’t churned out much innovation (not recently at least.) I’d like to see Apple developers gain more choice. With every iteration of OSX, there seems to be so much effort put into innovation of desktop components, but the development environment is age old. I use Objective C because I have to, while I use recent languages such as C# and ruby because I want to. Take look at with Microsoft is doing with .NET: you can write your own .NET compiler - you just have to make sure it spits out the required IL code. It’s beautiful and elegant, and you aren’t locked onto one language. It’s managed, and therefore a bit more expensive, but unless you are writing real time code, it doesn’t matter today: it’s not _that_ slow for writing most desktop applications. In short, I’d love to see Apple investigate managed code, and perhaps help bind Cocoa with more interesting and fun languages.”
Update2 (12/27/2005): Thanks to those who commented below - most of the comments have been quite constructive and I’ve enjoyed reading them. I’d like to add the following notes to supplement my views:
1) I am not suggesting Apple carbon copy .NET and port it to the OSX as is. I am suggesting that Apple put in some resources to investigate the innovations and choices (C#, Python, etc can be used to spit out .NET assemblies. It is possible to write a compiler for .NET as long as they adhere to the IL specification - this is what I mean by more choice) offered by .NET and similarly offer it’s developers more choice. I am suggesting that Apple take a _lead_ with offering its developers new paradigms of creating applications. Feel free to comment on your like or dislike for .NET and compare C# to Objective-C if you must, but you’d have lost the gist of my argument.
2) I do not agree that .NET is ‘too slow’ or only useful for developing quick and dirty solutions. I have come across a _lot_ of good enterprise level implementations of applications coded in .NET. Please don’t attempt to convince me that .NET doesn’t work for enterprise level applications - I have seen otherwise.
3) I do not agree with the “If its not broke, don’t fix it” argument. This is an extremely dangerous argument. It limits progress and innovation. For example, Panther was a great iteration of OSX - why did Apple have to work towards Tiger? If one were to accept the “don’t fix it” argument, Apple shouldn’t have released Tiger, and Apple doesn’t need to release any more iterations of OSX. Everything seems ‘not broke’ with Tiger today, why bother? The answer: innovation. There has got to be a non-stop iteration of improvements. Apple hasn’t disappointed me with progress made towards OSX desktop components, and so I’d be happy to see a stronger push towards more choices and newer methods of development.
4) I do not agree with assertions along the lines of “Objective-C is the best. There is nothing better.” Language preference is a matter of _taste_, and this cannot be forced upon anyone. _You_ may like the Objective-C way of doing things, but _I_ prefer newer languages such as ruby and C#. I am suggesting Apple investigate and put in efforts towards giving people more choice. There is no doubt in my mind that more developers will be enticed into developing for the OSX platform if they had more choice. Also see 7)
5) I am not suggesting Apple abandon Objective-C. Clearly, it has a tremendous fan following.
6) I am aware, and I appreciate many community related efforts towards bridging Cocoa with other languages. However, many of these are incomplete, and I’d be delighted if Apple chose to sponsor similar efforts.
7) As with .NET in 1), my example of ruby is just that - an example. I am not insisting that Apple only bind languages such as ruby and C# to Cocoa because I happen to like them. I am suggesting that Apple take a look at how these languages are improving the lives of developers. For all I care, Apple could come up with a brand new language after drawing inspiration from recent innovations of ruby and the like.
8) I am not suggesting that Apple has made no progress in the past few months. For example, I am aware of new solutions such as Core Data and Core Image to name a few.
To sum it up: Apple has blown me away with it’s innovation with desktop components. For example, after having used Expose with hot-corners, I can’t imagine life without it. I’d like Apple to channel some energy towards giving it’s developers more choice of languages, and perhaps learn a thing or two from efforts such as the .NET environment and the ruby language.
Perhaps I should’ve posted the above with my original post, but I had no idea I was going to get Slashdotted. I’ve enjoyed most of the comments - but the amount of responses has been quite overwhelming. Much appreciated though!
Want to flame me for criticizing Objective-C? This is the place to do it!