Hacker News Reader

Right off the bat, on the first 3 examples, he shows how you need to use different APIs depending on the IE version.

That alone is enough reason to use jQuery and not having to bother.

You're pointing out an IE problem, not a javascript problem that isn't present in other browsers.

It's a developer's problem.

And your point is? Pointing the blame at a different source doesn't mean the problem isn't present. If a client needs IE support, what do you do? Write the code three times? Detect IE and redirect the user to chrome-frame, then cry when you don't get paid?

I don't care who caused the problem. Just that it wasn't me, I can't fix it, and I have a deadline to meet and constraints to follow. jQuery is a lifesaver.

Chrome Frame is no longer supported. :(

Reply on news.ycombinator.com