4 ms·

jQuery exists for one simple reason : deal with DOM inconsistencies between browsers, and it works. Some people tested the code for you on all the browers so yo

by camus 14y ago

jQuery exists for one simple reason : deal with DOM inconsistencies between browsers, and it works. Some people tested the code for you on all the browers so you can assume your code will work on all the main browsers out there. Those who think they are too smart to use it certainly are not real web-developers in real businesses , having to support legacy browsers because their client base still run on IE6. or they have enough time to work on all the quirks of IE6 IE7 IE8 each time they write a DOM related function , i dont... jQuery is here for quick DOM manipulation, is basically a facade pattern, and the bright idea was to use CSS selectors to query the dom. jQuery selector engine is far more powerfull than document.querySelector Why is it hard to work with the DOM ? because it is STRONGLY and staticaly typed ! it has interfaces and type checking , so using it with a dynamic/weakly typed language is hard. the DOM doesnt use duck typing , that's why can get all these DOM ERROR , invalid DOM LEVEL call ,and you cant create an Element or a Node without a factory etc ... and let's give credit to MS on this, they created DHTML because they understood it made little sense using that api with that language ( each time you are using innerHTML it is DHTML, querySelector to until it was made a standard ). yet I dont see people saying they are too smart to use DHTML because it is not pure DOM. but do they really care about what interface is used ? how the factory method build the given objects ? i dont think so.

masklinn 14y ago
> jQuery exists for one simple reason : deal with DOM inconsistencies between browsers, and it works. It exists for a second reason as well: make DOM interaction not suck. Because they suck hard out of the box. > Why is it hard to work with the DOM ? because it is STRONGLY and staticaly typed ! Not really. It's because it's defined through a very restrictive abstract language which assumes almost nothing about the implementation language (basically, that the implementation language has method calls and a name can map to multiple arities somehow). That gives an API which can be implemented on pretty much any object-oriented language, but will also suck on pretty much all of then. > querySelector to until it was made a standard Uh... no it was not, if you want to give MS credit where credit is due you can give them XMLHttpRequest, but definitely not querySelector which is a WhatWG brainchild (the first revisions were by Anne van Kesteren and Lachlan Hunt). MSIE didn't get querySelector until IE8 (March 2009), Webkit landed it in December 2007 and Gecko in July 2008. Also, innerHTML was standardized as part of the HTML5 effort, as well as a number of ther "DHTML" features. And while you give praise to MS, don't forget to criticize them for e.g. not having implemented the DOM Events API until IE9.

by camus 14y ago

masklinn 14y ago

> jQuery exists for one simple reason : deal with DOM inconsistencies between browsers, and it works. It exists for a second reason as well: make DOM interaction not suck. Because they suck hard out of the box. > Why is it hard to work with the DOM ? because it is STRONGLY and staticaly typed ! Not really. It's because it's defined through a very restrictive abstract language which assumes almost nothing about the implementation language (basically, that the implementation language has method calls and a name can map to multiple arities somehow). That gives an API which can be implemented on pretty much any object-oriented language, but will also suck on pretty much all of then. > querySelector to until it was made a standard Uh... no it was not, if you want to give MS credit where credit is due you can give them XMLHttpRequest, but definitely not querySelector which is a WhatWG brainchild (the first revisions were by Anne van Kesteren and Lachlan Hunt). MSIE didn't get querySelector until IE8 (March 2009), Webkit landed it in December 2007 and Gecko in July 2008. Also, innerHTML was standardized as part of the HTML5 effort, as well as a number of ther "DHTML" features. And while you give praise to MS, don't forget to criticize them for e.g. not having implemented the DOM Events API until IE9.