...and the Microsoft AJAX Library, err, and the ASP.NET AJAX Control Toolkit. Yep, Microsoft has not only finally come up with an official name for the AJAX technologies which until now have been known collectively as ‘Atlas’ but has also split it into three individual products. All are expected to ship by year-end.
ASP.NET 2.0 AJAX Extensions cover the server-side functionality, while the Microsoft AJAX Library handles the client-side stuff and integrates with the server-based extensions, naturally. The final part of this triumvirate is the self-explanatory ASP.NET AJAX Control Toolkit.
But you know what, nobody seems to care about that online. The big fuss seems to be on the naming convention: what was wrong with Atlas? Why not call it iAjax? Why is Microsoft so boring these days? It is branding that counts, that’s why the x-box is a success.
Is it just me, or does what a technology can do matter more than what it is called? Especially in the corporate domain where something like ASP.NET 2.0 AJAX Extensions is destined to live? Personally, I rather like the name, it pretty much says what it does on the tin.
Perhaps the problem is that the Atlas stuff is competing with true open-source toolkits, a world where obscure naming is key. Hey, you’ve got to have some badge to wear that shows you are a member of the IT in-crowd, you are in ‘in-the-know’ after all. I suspect we will see it being referred to collectively as MAJAX 1.0 before too long.
Anyway, back to the real business: Microsoft also announced that its AJAX tools will be fully supported within Visual Studio 2005 (and should ship with the next version of Visual Studio, codename Orcas, when that finally arrives.) Another small, but rather important fact that got lost in the what’s it called again argument. As was the fact that it should ship in Beta form real soon now, and be shipping properly by the end of the year.