Posted by: YuvalShavit
There’s Ajax and there’s Ajax. There is Ajax in the Java world where it’s no-holds-barrred, Katy-bar-the-door, and find-yourself-a-framework-or-die. Then there is Ajax in the .NET world where Microsoft created its own Ajax framework which is offered to you as part of the company’s other Web development offerings.
However, Microsoft’s Ajax framework is not the sole Ajax framework available to .NET developers. And at least one blogger thought it was worthwhile to query the Web audience to see how .NET Ajax framworks stacked up.
Italian Simone Chiaretta, .NET developer and Subtext core member, was spurred in his quest by the recent Richard Monson-Haefel Ajaxian survey on Ajax framework use, but wanted to see what things looked like for .NET. Chiaretta found — lo-and- behold – that Microsoft’s ASP.NET Ajax was tops by far among responders.He writes:
… among the 95% of the .NET developers that said they are using some flavor of Ajax either in production, development or prototype, the most-used Ajax toolkit is ASP.NET Ajax, with 73,7%, followed by the Ajax Control Toolkit which is used by almost half of the .NET developer that are using Ajax.
Despite, Microsoft’s predominance, there is percolating use of other Ajax frameworks amid the .NET crew. Interestingly, among ASP.NET users cited in Monson-Haefel’s survey, ASP.NET Ajax use is represented by 36.3% of responders, and is in a statistical dead heat with Prototype and jQuery open-source alternatives. Writes Burton Group’s Monson-Haefel:
What is interesting about the Ajax market is that it’s more diversified in 2007 than it was in 2005 – the number of toolkits keep growing and jostling position in terms of usage.