This post originated from an RSS feed registered with .NET Buzz
by James Avery.
Original Post: Prototype vs. Atlas
Feed Title: .Avery Blog
Feed URL: /blog/Install/BlogNotConfiguredError.aspx
Feed Description: .NET and everything nice
I have never hidden my distaste for Atlas, I think it’s too bulky and complex, but perhaps the future of JavaScript is huge client-side engines like Atlas. As download speeds get better and better maybe the bulk won’t be a problem for users. If we are going to have a client-side engine like Atlas though, I would much prefer complete access to all of that JavaScript… and the rights to modify and re-distribute (which is what you would be doing when any user hit your website), something I doubt we will ever get from Microsoft.