Last time I griped about ASP.NET ATLAS [LINK]. Ok so with that said, what’s the alternative? When I wrote my book (Amazon.com Mashups) I did most of the Javascript coding by hand. It wasn’t bad but it wasn’t always easy. I tried ATLAS/ASP.NET AJAX and it sucks. I’ve moved on.
Decision criteria are as follows:
1) The stack should be fast, it should perform and add minimal overhead to my pages.
2) It should not impede interoperability. I want my code to play nice with others.
3) It should not slow me down. …

Wordpress is nice but it’s a bit of a hog CPU-wise. Jeff Atwood has a nice piece on this entitled “Behold WordPress, Destroyer of CPUs“.
We have a big set of releases coming up at work and I’ve become a bit obsessed with performance. We’re not using Wordpress but I figured performance improvement, just like anything, starts at home. So ever since installing Wordpress with this Arthemia theme I’ve been tweaking to try to get the most out of it.
I’m measuring performance using Fiddler 2, starting with clear browser, …

It’s no secret I’ve long been a fan of .NET and the ASP.NET stack. I feel the team really got it right making developers highly productive and the Visual Studio IDE is second to none. After spending some long hours with Atlas and ASP.NET AJAX though I’m afraid I can’t say the same.
ATLAS on top of ASP.NET is an example of a retro-fitted round tube jammed into a square hole. The whole notion of AJAX is that it’ll serve PARTIAL pages, snippets of data, merged with presentation …