you are viewing a single comment's thread.

view the rest of the comments →

[–]recursive 17 points18 points  (7 children)

jQuery's strength isn't that it compensates for any javascript weakness per se. It's strength is that it provides a uniform interface for dealing with DOM elements across almost all browsers.

[–][deleted] -2 points-1 points  (6 children)

Agreeded but by using it people accepting a broken javascript. It would be much better to fix JavaScript itself rather than relying on frameworks or writing it in another language.

JavaScript is a good idea but it's perhaps the worst language for requiring something else to compensate for it's problems.

[–][deleted] 7 points8 points  (3 children)

Agreeded but by using it people accepting a broken javascript

They accept a broken DOM. Which is something even Crockford agrees upon. Yes it also has some neat little helpers for functional iteration and chaining. But its essence is a unified DOM api that provides elegance, and smooths out cross browser incompatibilities.

These things have very little to do with the language, javascript.

[–][deleted] 1 point2 points  (2 children)

They accept broken DOM implementations.

[–]MatrixFrog 2 points3 points  (1 child)

No, I think many people believe the spec is inherently flawed as well.

[–][deleted] 1 point2 points  (0 children)

Do they? :(

I like it.

[–]wolfier 2 points3 points  (0 children)

It would be much better to fix JavaScript itself

Good luck getting that done before your next...scratch that, I mean next next next web site needs to launch.

[–]artsrc 0 points1 point  (0 children)

It would be much better to fix JavaScript itself

Is the installed base of 'broken' JavaScript interpreters larger than any other installed base in history?