Microsoft seem to think that asking programmers to understand databases is too hard. So they have come up with yet another automatic code generator (following in the footsteps of Access, Data Controls, Typed Datasets, ... apologies to any silver bullets I may have dodged in the last 15 years).
Unfortunately the barrage of criticism from programmers has fastened on entirely the wrong point (as you might expect from a bunch of twenty-something blogshites).
Here's what's really wrong with it.
Definitely read this. It's not really about Martians or headsets.
It's always nice to see well written, controlled anger. Hacknot's demolition of Ruby and similar cults is worth sitting down with a cup of coffee or two, and reading to the end ....
I've read a few times (and can recommend) Bruce Tate's Beyond Java (though that doesn't have a lot about UIs in it) and I'm always interested to hear views on where UI programming is going.
User-level configuration of custom software has always been a pain to implement. Traditionally, as a database specialist, I've used databases for this: but there are drawbacks and although I've tried XML, it doesn't seem to solve them.
I've finally got the Offspin site onto a content management system (CMS).