Last month Grant, Christina and I checked out a couple of screencasts from Pragmatic Programmers' Bill Dudney. Specifically, we watched "Coding in Objective-C 2.0." We took a look at part one mostly, which is an introduction to the Objective-C syntax and structure, culminating in a basic application. Part two covers memory management in depth. Since then they've added a part 3 on debugging, and the plan is to continue adding more. Part one covers classes, objects and messages and, like the other portions in the series, costs $5. One thing I love about Pragmatic Programmers is that they offer a wide choice of formats, including versions tuned for iPhone viewing and Theora Ogg format.

It's important to note that while Objective-C is the language you'll use for iPhone development, these screencasts alone won't make you an iPhone developer. For one, there are differences in memory management on the iPhone versus desktop apps (iPhone apps don't do garbage collection). Also, iPhone interactions require the use of Cocoa Touch, and that isn't covered in these. If you are looking to move from another OOP language to Objective-C, however, this is a great way to get started. Plus, you really need to understand Obj-C to make solid iPhone apps. The side bonus is that you will also be able to write Mac desktop apps.

These screencasts are particularly useful if you are an audio-visual learner and have some background in programming. Don't expect to come up to speed if you have a slight understanding of a basic scripting language. That said, these are very clearly explained and the structure is great. If you watch the videos and do the exercises, I have little doubt you'll be learning the basics of Objective-C in no time. Listen to the audio as we discuss who these are for and what could be done better.

Web applications that function like familiar desktop apps are all the rage these days. Web apps already have the advantage of being accessible from everywhere, but add in a UI that works like something users already know, and you've got something pretty cool. Cappuccino is an up-and-coming way of getting this done, and the code is now all open-source. It's a framework for building apps like this using some tools that are already pretty standard on the web, like Javascript, combined with what's basically a port of Apple's Cocoa APIs, and tying it all together with a language called Objective-J.

Objective-J is to Javascript what Objective-C was to C. As the Cappuccino site puts it, "programs written in Objective-J are interpreted in the client, so no compilation or plugins are required." Beautiful. The developers are pretty clear that Cappuccino is just for apps, not for building websites with "dynamic content," or whatever the kids are calling it these days. Want to see Cappuccino in action? We've actually already reviewed the first great Cappuccino app, 280 North's excellent presentation software, 280Slides.

The iPhone SDK has been out for couple of weeks now and I've been using it to develop an application for my work as a technology demonstrator. My experience thus far has been largely positive. I wasn't surprised by how well-made the SDK is, even at this beta stage. The amount of work involved in releasing any SDK, let alone one that is so tightly scrutinized, cannot be underestimated.

Consider that I am learning three new things simultaneously: programming in Objective-C, learning how to use Xcode, and what is available in the iPhone SDK, I am going to describe the whole experience instead of just confined to the SDK.

First, let me start with the full disclaimer: I develop Windows .NET application by day (and by night too for ecto) and use Mac OS X at home for everything else. Before getting my Mac Pro last December I used to work on ecto using a second Windows machine, but since then I have been using Visual Studio 2005 in an XP virtual machine using Parallels.

Whether you love or hate Microsoft, you have to give them credit for popularising programming on Windows. While I was a junior programmer fresh out of college learning C++ and working on train control software, truckloads of CS/Engineering graduates were learning to program in Visual Basic. Whatever faults VB has, the way it allows even beginner or causal programmers to learn the craft and produce quick and dirty applications means that programming for Windows was no longer the eminent domain of the traditional CS/Engineering graduates, where FORTRAN and C/C++ rules. Microsoft continues this trend with C#/VB.NET and the .NET Framework, providing a lot of built-in functionality that used to require hand-crafted code or expensive third-party libraries, freeing up developers' time to concentrate on problem solving instead of mechanics.

With OS X, Apple began with Objective-C and Java as the programming languages of choice but ever since version OS X 10.3 Java had been put onto the back burner and is expected to be phased out eventually. Unfortunately, making Objective-C the sole language of the platform also makes it difficult and 'expensive' for Windows programmers, such as yours truly, to join the party. The difference in syntax (despite the 'C' in the name it does not have much resemblance to C or C++), difference in framework and API, difference in IDE philosophy, and the lack of refactoring tools (ReSharper, CodeRush, etc.) and unit testing tools (NUnit, JUnit, etc.) mean that some of the more open-minded programmers (mostly Java and .NET) will not take an active interest in Apple software development.

The upcoming Xcode 3 looks like it would make a big step in closing the gap, but the IDE still lacks the tools mentioned above to attract the time-constrained, less hard core developers from the Windows side of the world. The dark horse may be the combination of Eclipse IDE and Mono project. The Eclipse IDE is mature and has a flexible plug-in architecture so refactoring and unit testing tools can be integrated into the IDE by third party developers. Meanwhile the Mono project has been making lots of progress as far as compatibility with Microsoft's implementation is concerned. And the ability to take code written in Windows and runs it in Linux or OS X (with some limitation, of course) will appeal to Windows developers, at least as a starting point.

In fact, Eclipse/Mono may actually achieve what Sun tried to do with Java all those years ago. Remember 'Write once, run anywhere'?