“Web 2.0” problems compounded by .Net serialization lameness

Flickr decided to change an attribute of the their tags xml schema that’s part of their open API. I have all of Kat’s Photo Essays running off of Flickr with a custom wrapper I wrote in .Net. It broke the other day and someone was nice enough to point it out. Thanks to the excellent error handling in .Net seriliazation (i.e. “There was an error in serialization (1,5)” or something ultra useful like that) this took 1.5 hours to fix. And, because I love to bitch about MS, really, if you’re serializing a genormous XML document and it fails would it really be the end of the world to tell us why? Would that be too much to ask of the largest software company on earth? Probably an outrageous request… better to have the world playing eye-ball compare between serialized classes and huge XML docs… thank god for NUnit – this would have take forever with out unit tests to debug it.

Anyway – I guess, for “Web 2.0” (webservices) to really take off there needs to be some kind of notification scenario where Flickr could tell everyone using their service that “hey, tag-id is no longer going to be a long, it’s going to be a string”. Until that happens Web 2.0 will be pretty sketchy to use for anything other than non-mission critical applications.