I know you’re being tongue in cheek here @msavin, but it really is. Meteor is much more than a framework, and can’t be easily fit into any of the survey categories. Let’s look at each category from Meteor’s point of view:
- Flavours: Meteor works with the top 4 (ES6, ES5, TypeScript, Flow) and probably the others as well.
- Front-end: Meteor works with all of them.
- State Management: Meteor works with all of them.
- Back-end: I don’t think you can really compare Meteor and the winner Express in the same category. Meteor uses and depends on Connect, which is essentially a scaled down version of Express (actually, connect was a hard dependency of Express until version 4). So while Meteor does well in this category, it essentially includes a large subset of the winner’s functionality as well.
- Testing: Meteor works with all of them.
- CSS: Meteor works will all of them.
- Build Tools: The winner here (npm) is an integral piece of Meteor, and the others can be integrated with Meteor.
- Mobile: Meteor works with all of them
I think it’s safe to say that no other piece of JS based technology discussed in the survey results even comes close to matching Meteor’s capabilities when viewed as a whole. Meteor is much more than a framework, a library, a helper … it’s a platform whose capabilities not only allow us to build apps more efficiently, effectively and happily, but also allows us to integrate with all other key pieces of the JS world.
Meteor