Subtle changes, bugs and feedback

Don't see the point of CoffeeScript. It's not that much quicker than just writing the actual JS.
Aside from the issue of leaving your code optimisation to someone else in the first place, CoffeeScript pumps out some pretty inefficient code - functions defined as variables, functions inside of object literals, switch statements, etc. which will use more memory and perform more slowly.[QUOTE]

Wrong.

[QUOTE]Zepto is utterly irrelevant to me because it doesn't support IE, and sadly I have yet to have a single client say "neither do we". As such there's no point me even finding out what it does.

Fair enough if you have to support IE

The whole "guaranteed to work on everything" thing - what exactly is wrong with including an array.indexOf for IE - it's small, efficient and leaves all grown up browsers to use their native implementations, and crucially you only include it if you know you will need it, rather than shoving it, and a load of other things, in whether or not you do.

CoffeeScript only includes what you need. Maybe you should actually read about it!

I would imagine you take great care to optimise images, reduce server fetches by using sprites or maybe base64 inline images. Why go to that trouble if you are then going to lard up the page weight again by throwing in a load of JS, HTML and CSS that you know you will never need?

Because the CSS reset is gzipped to almost fuck all, and for the applications I'm building, the reset reduces the size of the rest of the CSS. The JavaScript it almost almost always uglified or Closure Compiled, so is also tiny. And I only include what I need.