Joel on Software's admin dude wrote a post about how they are doing db backups. 

http://www.michaelgorsuch.org/wordpress/2007/07/11/some-times-you-have-to-roll-your-own/

Funny thing is that this is how all databases fundamentally perform backups.  Just makes me think that once you get X years under your belt you come to the conclusion that you've seen it / know it all.  Fundamentally, this stuff is simple, the problem comes into play when MS (or vendor of choice) tries to layer multiple extra layers of shite on top of a simple concept.

Html, javascript, css are easy (compared to multi-threaded servers and C++).  ASP.NET makes them much more complicated then the have to be.  I'm currently in the process of removing all of the ASP.NET AJAX CRAZY framework out of the whatsyour20.com as it's just too damned complicated for what you get.  Also I think the ASP.NET page life cycle is ridiculous.  We stopped teaching ASP.NET for web development at the college I used to teach at because it was just too hard for students to figure out.  Ironically, MS made ASP.NET follow the desktop paradigm to get the Windows Forms dudes (like myself) to buy in, which caused ASP.NET to become almost incomprehensible for those that wanted to learn web development without having any desktop experience. 

There is a reason PHP and MySQL are so popular.  Simplicity has a place and that place is HUUUUUGE.  It's a big house on the hill overlooking the lake with a great view. 

The point of this rant is that sometimes we make things so complex by trying to make them simple.  Instead are we perhaps better off if we let the complexity stay were it needs too. 

ASP.NET missed being one of the best pieces of software ever designed.  Why?  Page lifecycle (why must i figure out if i need init, load, pre init, pre load after load, after init, and the if (postback == false) { madness).  The dirty little secret about ASP.NET is that nobody needs a freakin' data grid!  They are completely useless.  Html tables are easy to make.  Grids are ridiculous and bloated and don't support Ajax worth a damn. 

Why I'm at it I should rant about how SQL Server 2005 leaves out features already in 2000.  But this post is getting too long as it is.

ASP.NET needs a sane alternative implementation that works with the web instead of against it.