How to choose a JavaScript framework

[rosetaylor01]

Efficiencies. Projects live or die by them. A JavaScript framework may not make you a better programmer, but it will make you more efficient. That alone should be reason enough to choose a JavaScript framework, or library if you prefer. Unless you decide to build your own, there are plenty of options available to developers. However, choosing the right framework can be tricky, and weeding through a mess of opinionated fanboys (myself included) is intimidating.

The best advice I can offer is to be flexible in your approach, and to ask the right questions. This list should help you get started.

[fside]

Efficiencies. Projects live or die by them.


So some suggest GWT or some other 'cross-programming' abstraction because it's more - efficient. More error prone is more likely. You're adding an extra layer to go wrong.



A JavaScript framework


People tend to prefer that jQuery, Prototype, MooTools be termed - libraries. What you or I have that is a collection of tools and things specific to our pages and sites might be termed - toolkits.



choose a JavaScript framework, or library if you prefer.


A framework is much more ambitious. That's an important difference.



The best advice I can offer is to be flexible in your approach, and to ask the right questions. This list should help you get started.

jQuery has emerged as a consensus library. Prototype is still used, often in conjunction. Many like MooTools. You'll see that on various sites. And then there are 'plug-ins', extensions, to these from all sources.

jQuery, though, and its many extensions have sort of emerged from the pack. And one might start there.