An array of points in C: http://s3.mrale.ph/images/array-of-points-structure-c.png
An array of points in JavaScript: http://s3.mrale.ph/images/array-of-points-structure-javascri...
An array of points in C: http://s3.mrale.ph/images/array-of-points-structure-c.png
An array of points in JavaScript: http://s3.mrale.ph/images/array-of-points-structure-javascri...
I think that is the core of the analogy, and it is not talking about how high or low level each language is in an absolute sense but in a relative sense. It is talking about it being the "at the metal" language of machine instructions and browser "instructions" respectively.
Of course, there are other parallels, but they aren't as strong. Part of the reason for using CoffeeScript is because of a perceived increase in expressiveness, but that increase is very small compared to the improvement of C over assembly (as the author of this article points out).
Actually, you don't know that. Since doubles are immutable, the runtime can (and does) cheat, including turning many of them into integers. It all boils down to predictable usage patterns.
These are the things that Javascript has been growing to facilitate the idea of js as asm. Emscripten uses ArrayBuffers to allow C to compile to JS without the messiness.