[MTOS-dev] [ProNet] Javascript Library Standardization

[Timothy Appnel]

I thought this post was pretty good food for thought with the question at hand:

http://blog.reindel.com/2007/10/30/how-to-choose-a-javascript-framework/

I like that it really isn't explicitly partisan to a certain toolkit
though I suspect some of the authors commentary plays nicely into his
weapon of choice. I can't tell what that choice just reading this
article though so I take that as a good thing.

Here are two passages that jumped out at me:

> 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.

> Terseness, as well as chainability, are two very important features that should not be overlooked. Remember, you can grow irritated quickly because of cumbersome implementation details.

Most of the comparisons I found where dated and had a lot of
subjective ratings such as documentation and community support. I did
find one recent comparison that stay away from that sort of thing
pretty well.

http://javascriptant.com/articles/24/javascript-libraries-by-comparison

The one bummer was #7, the file sizes seem kind of incomplete.

<tim/>

-- 
Timothy Appnel
Appnel Solutions
http://appnel.com/