The point is, if the client-side platform had any "real" capability, there wouldn't be a need for Atlas. It's 2007, not 1997.
Troy T.
The point is, if the client-side platform had any "real" capability, there wouldn't be a need for Atlas. It's 2007, not 1997.
Troy T.
http://msdn2.microsoft.com/en-us/virtuallabs/aa740378.aspx[^] Tools like this will help take some of the sting out of web dev, but the problem is still with the HTML/CSS/Images pardigm. There is a growing gap between the client and server sides of software development. Just take a look at the progression of the client side technology. We basically use the same stuff we did 10 - 15 years ago HTML/CSS/Images. Now compare that to the server side technologies. CGI, ASAPI, ASP, ASP.NET 1.1, ASP.NET 2.0. You can see the same thing in the other platforms, Java, ColdFusion, PHP. On the MS platform, what's one of the best tools to come along in the last few years? ASP AJAX (Atlas)? That is basically a server-side tool to help manage the decrepit client-side markup. In fact, MS gave us an intermediate scripting language for when we need to wander over to the client-side.
Troy T.