Good try kid. But you ain't goin' nowhere with this FUD. - Life's too short to deal with cross-browser incompatibilities. - jQuery too heavy for you, there's

Good try kid. But you ain't goin' nowhere with this FUD. - Life's too short to deal with cross-browser incompatibilities. - jQuery too heavy for you, there's Zepto. - Not at all times you are in control of your stack, especially when you just inherited the project. - If you happen to work on a Drupal project, good luck with ditching jQuery. It's built in. - Clients will always ask for "cross-browser support up to IE8" without knowing it's a dead browser. - What matters to clients is that it works. They don't give a beaver's construction project what you used to build it. I'd wouldn't say "Why you shouldn't use jQuery", but more of "when to and when not to use jQuery/vanilla/CSS3".