 |
|||||||||
|
|||||||||
|
|
Just recently I put up a blog post talking about consuming a POX service using Cocoa. As it turns out, Aaron Hillegass had some sample code in his book that does just that - it consumes an Amazon.com service that returns book information.
In the course of writing this post, I made some statements that I thought were funny and sarcastic. Turns out that when I went back and re-read the post, those statements seemed to be in really poor taste. This is really a big problem with blogging in general as we don't have the same rigorous editorial process that we have when publishing printed material. If I was writing a chapter, a copy editor or a trusted colleague would've said, "Hey, this joke doesn't work. In fact, it sucks. Cut it.". But, when I'm writing a blog post at 1am while watching re-runs of Battlestar Galactica on UHD and trying to create the world's most awesome creature in the Spore creator, I can look at my blog post and thing "OMFG that's gonna be funny" whereas, in my right mind, I would've said, "OMFG that's gonna be ass." and reworked things. So again, my bad - I am really sorry.
So, I am really sorry that the tone of my previous post was in bad taste and my "sky is falling" joke about following Hillegass' example was entirely too dry and sarcastic for a medium that cannot convey tone of voice.
Hillegass is the King of Cocoa. Its his day job, it's his not-so-day job. It's what he does. I'm just a .NET developer who tinkers with Cocoa. Obviously he's going to know that NSXMLParser is faster than NSXMLDocument, but my post wasn't about XML parsing. It wasn't about performance. It was about a design pattern.
The purpose of my post was about keeping concerns separated and making my application easier to maintain. The issue I had was in storing the XPath in the column identifier inside Interface Builder. I personally dislike this option for many reasons. Here are a couple of them:
It's also worth noting that I would feel the same way about WPF as well. If
a low-level networking change occurs such as a change in the XML format of
the service I am consuming and I have to change my XAML to account for that
change, then I would also feel like I have too much tight coupling going
on.
Kevin, I really appreciate this posting; both the tone and the thoughtful
technical points. I think your blog is, in general, great. Please keep up
the good work. I'm sorry I was such a grumpy old man.
" This is really a big problem with blogging in general as we don't have
the same rigorous editorial process that we have when publishing printed
material."
