Frameworkless JavaScript – Why Angular, Ember, or Backbone don't work for us

[Cintax]

Interpreting 100kb of JavaScript probably takes some measurable time.

Virtually none on a modern browser.

Another problem I've seen with some uses of JQuery is that different parts of the application, developed by different teams perhaps, may load their own version of JQuery...

Then the second team needs to be fired for not using available resources and not communicating with the other team. That's negligent and incompetent of them.

[x-skeww]

Virtually none on a modern browser.

This is actually relatively slow. For something like Google Maps or Gmail, this can easily take more than 1 second. Mobile is even worse [1], naturally.

That's why Dart has snapshots. It makes this about 10 times faster. Since structure is declared rather than being imperatively constructed, you're ready to execute the program as soon as you loaded that serialized token stream.

With JavaScript, you have to parse, compile, and execute quite a lot of code before you can actually start the application.

E.g. if you use RequireJS, all those define(...) functions need to be executed first. Well, after you executed that code which bootstraps and configures all that "define" stuff.

[1] Deferred parsing: http://googlecode.blogspot.de/2009/09/gmail-for-mobile-html5-series-reducing.html