Over a million developers have joined DZone.

Which JS Framework Are You *Most* Interested in Right Now?

DZone's Guide to

Which JS Framework Are You *Most* Interested in Right Now?

Pick between Angular, React, Ember, Meteor, and Backbone and let's see what the DZone community thinks about today's selection of JavaScript frameworks.

· Web Dev Zone ·
Free Resource

Learn how error monitoring with Sentry closes the gap between the product team and your customers. With Sentry, you can focus on what you do best: building and scaling software that makes your users’ lives better.

Last week we took a break from JavaScript framework questions to ask about TypeScript usage in the wake of the TypeScript 1.5 release.

Image title

It looks like TypeScript still needs more time to gather adopters. Languages and supersets of languages always take a lot longer to become widely adopted than libraries and frameworks. Take for example, the JavaScript front-end and platform frameworks. React has rocketed to popularity recently, but so did SproutCore for a while. Do you remember that one? Ember was originally forked from that framework.

So even though frameworks, and generally a lot of tools and libraries in the still-immature JavaScript/Node ecosystem, are fleeting in their popularity, I wanted to do one more overall poll on which JavaScript frameworks were most interesting to all of us at present.

Poll Link

Results show when you take it

Do you wanna run a poll on DZone, leave a comment and I can put it in a poll. And of course, anyone can post articles themselves.

What’s the best way to boost the efficiency of your product team and ship with confidence? Check out this ebook to learn how Sentry's real-time error monitoring helps developers stay in their workflow to fix bugs before the user even knows there’s a problem.

javascript ,front-end ,ember.js ,meteor ,backbone.js ,angularjs ,react.js

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}