It's unfortunate that people still think they need monolithic libraries to get anything done on the client side. The node ecosystem showed this doesn't have to be the case. It becomes even more important on the client side to keep dependencies small.
I've had this debate with a friend who's a big proponent of EmberJS (and to a lesser degree Angular). My friend feels that without one of these libraries you will simply be writing way too much unnecessary boilerplate code for a single-page app of significant size. I personally prefer to rely on small modular dependencies, so Component appeals to me, but I've only played with Ember/Angular a little bit so I don't necessarily know what I'm missing. Can you recommend a set of Components that would provide similar functionality and productivity?
So what we have so far from these 3 libraries is basically a decomposed backbone with declarative bindings. That will cover 99% of your typical app. I don't find there is too much boilerplate.
Take a look at the Ember examples at http://emberjs.com/. They're doing a lot more with a lot less code. Backbone had its day, but the world is moving on, and a new project that only offers Backbone-equivalent functionality won't garner much interest from me or probably anyone.
I agree in as much as the small component I use is quite well supported and popular. Its a sort of insurance that I don't have to worry about bugs and it running stale. A lot of components in component seem to be written by a single person, and don't get much attention, which to me, is a liability.
the issue is JS doesnt make things easy as soon as one wants to go modular. JS is so flexible that someone's script might not be compatible with yours.When JS gets a proper module system ,that doesnt really on voodoo modules, things will change.
hovering over ratings: "Overall JSDB.io Rating (derrived from combination of the other metrics)"
So I guess that means the rating are based on some formula of: stars + average time between commit + forks + contributes
My only problem is that doesn't this rating favor larger projects (Angular or Ember) as opposed to smaller projects that are perfect for solving small problems? The only way I can see around that is if stars has an overwhelming weight in the formula.
Anyways, looks helpful none the less (will look though it)
Hey! (I made this)
Stars do have more rating than the other metrics, which evens things out. Yes, larger libraries like jQuery are rating higher because of the ranking system, but thats actually accurate if you are looking at 'popularity'; furthermore, there are only a few projects that are on this scale.
Try 'trending' if you want to see libraries that are growing quickly.
It struck me, while browsing that, I would like to be able to browse the libraries by excluding known types.
Things like "Show me all the things that are not frameworks or jQuery plugins"
I'm not looking for anything in particular, but it would nice to see the possibilities without having to search through things that I know I'm not looking for today.
My favourite ecosystem for client side development these days is component (https://github.com/component/component). It's similar in style to npm but faster and made for building apps from small modular pieces. It has a growing community and lots of modules already (https://github.com/component/component/wiki/Components).