Response Chain
jQuery Push Back
A sampling of letters from the developer community.
I can understand why developers get excited when they first get their hands on jQuery. My team was no different -- especially our designer, for whom the jQuery API provided a low barrier to entry for DHTML, given that he was already an expert in HTML/ CSS design. However, after several intensive rich Internet application projects where jQuery has had to coexist with ASP.NET AJAX code and the Yahoo! YUI library, the conclusion among the developers is that jQuery is a monster!
The jQuery model frequently clashes with the ASP.NET AJAX JavaScript model, and debugging jQuery is an absolute nightmare -- particularly due to the fundamentally flawed design where an object is extended infinitely. This means that when you use IntelliSense in a debugging session to view the properties and functions of a JavaScript object, you get to see hundreds of elements, most of which have nothing to do with the object that is being viewed. Since when has this become a design that Microsoft is promoting?
There are fundamentally different kinds of Web applications, and jQuery is a wonderful tool for prototyping and for injecting life into static data pages. But for serious Web applications with complex user interfaces, I think it becomes a burden to the project. Clearly, some people will be ecstatic about the inclusion of jQuery in Visual Studio, but developers need to know if jQuery is going to add spice to their site or if it's going to cripple their maintenance budget!
Graham Churchley
Web Development Specialist
APX Inc.
Santa Clara, Calif.