Jan 14, 2006 08:06 AM|BillKrat|LINK
[jodywbcb] If your not ready to wait for ATLAS investigate AJAX as that is ultimately what ATLAS will be targeting.....AJAX can be used in production enviroments I do believe...
When I saw the link to MagicAjax.NET, which mumfie2003 provided, I wavered in my position of patience - but then I remembered (like a kid touching a hot stove)... and went back to patience mode.
I stepped off the Gates yellow brick road once (I thought Clipper was the way to go) and learned my lesson. When Windows 95 took off I was out in the cold. I never believed an operating system that crashed would/could ever become an industry standard;
but we quickly entered a new error (pun intended) of the "blue screen of death" and turn-it-off-and-back-on mentality. Since the 80s I've watched Microsoft put a lot of companies out of business by making their products obsolete; Novell was rock solid until
Windows 3.1 for Workgroups came out - it had "free" built-in networking capability - it now seems somewhat redudant to integrate a superior networking application into a network capable operating system (especially if you have to pay for it).
When that next operating system comes out, and potentially takes the world by storm (as Windows XP did) - we'll probably find that ATLAS will be an integral part of it requiring little to no coding. It's a sure bet that ASP.NET 3.0, and it's controls, will
most likely be centered around ATLAS, probably requiring no coding, so I envision many third-party applications will go away and developers will be rewriting their applications (after having to extract all third party code from the baseclass libraries).
Thus I take my hand off the hot stove and wait patiently on Gates "yellow brick road".