PIcking Your Javascript Mobile Framework: Part 6 - Elimination Round

Since the next few steps are going to be pretty expensive time-wise (on my part), it’s time to remove some of the options from the table. That should speed up the process, and I don’t think I left any real candidates out.

First, we are going to eliminate those contenders that have a much faster cousin. That means all the combinations with RequireJS will be kept, while their Require-less brethren are kicked out. These are marked as “rq” in the elimination table.

Second, we will remove all those that were characteristically slow to load. That was only three of them: React with Backbone, Enyo with Backbone, and EmberJS. They are marked with “zz.” I’ll let you guess why.

Third, we remove all those that have excessive coding length. That would be Enyo again, Flight, Lavaca, VanillaJS (which was never a real contender, anyway), and Closure. They are marked “vb” for verbose. Notice that adding RequireJS really doesn’t change code length by much.

This leaves us with the following table:

And after elimination, the following candidates: