I don’t have anything against people who want to use ObjC, but I’ve seen too many ObjC devs trash MT without knowing the first thing about it.

The progression of examples here – from the awful native APIs to the .Net way to the Vici way – is fantastic. I was horrified when I first saw how data access is performed using bits Apple ships. I found it all so ugly that I refused to use SQL for anything. Opted instead to use object archiving (which works well – credit where it’s due), but I would much rather have used SQL for data storage (archives still make the most sense for preserving app state when your app is closed).

The problem is that there are too many devs who make excuses for the appalling native SQLite “solution”. Yeah, there are ObjC wrappers that simplify things, but they don’t seem to follow any familiar patterns. The beauty of MonoTouch, just like anything .Net, is that we already know the interfaces. We can’t just copy and paste any old code from, say, a desktop app on account of SQLite being, as you’d expect, not as fully featured as a SQL server you’d run on a gigantic server in a basement somewhere. But there’s still enough compatibility that the potential for code reuse between different platforms is, relatively speaking, through the roof.

I know I’m not saying anything anybody here doesn’t already know… I just can’t stop writing. It’s always refreshing to encounter people who choose the best tool for the job rather than settling for the tool they’re given, or the tool they have some misguided, almost religious dedication to.

Prior to .Net, I preferred Java to all else.

When .Net came along, I hopped over. And I didn’t suddenly dislike Java – I simply preferred .Net.

I’m rambling.

I’ll end by saying this was a great post. I find it very aesthetically pleasing. The writing is clean; the code is clean.

We need to create an Army of Sensible Thinking and Coding by cloning you.