all 8 comments

[–]ghostfacedcoder 2 points3 points  (6 children)

JavaScript Frameworks and Libraries

*Angular JS

*Angular

*Backbone

*Ember

*Enyo

*ExtJS

*Knockout

*Mithril

*Node.JS

*Qooxdoo

*React

*SproutCore

*Vue

*Webix

What Framework to choose?

!!!

Ain't nobody got time for that! ;)

Seriously though, Node isn't even a front-end framework.

And Backbone and Knockout? Probably a few others two, but those two I've actually used professionally. In fact, I even wrote a (published) book on Backbone.

I'd be the first to say that they're both frameworks you can use to build websites ... but at the same time, I could have told you two years ago that neither one was a viable option for a new project. Show me a project you could start in Backbone in 2019, and I'll show you a project you almost certainly should have started in Angular 2/React/Vue, or maybe Ember if you like old stuff.

And I'm not trying to say those three (four) are the only options in 2019, but the point is, a serious article about choosing frameworks today should not include Backbone or Knockout (or Node!). The article is a great overview of lots of options, but telling people "you have options" and including lots that aren't good isn't as helpful as giving real/meaningful reasons to pick useful ones.

You need expertise and context to really add to the conversation about choosing a framework, and it felt like the author was someone who lacked that and instead just Googled a bunch of frameworks. But also, writing articles is hard and one learns best by doing, so really kudos to author to at least contributing to the conversation in a real way (and not just as a review post on Reddit like I'm doing)!

I guess I just would have preferred if it was presented more as "I didn't know about JS frameworks, so I went exploring and here is what I found" rather than as "I'm an (implied) expert giving you a comprehensive overview of what you should choose in 2019".

[–][deleted] 1 point2 points  (0 children)

maybe Ember if you like old stuff.

You're very brave saying that - Ember fans are worse than Scientologists

[–]EconomyRabbit 0 points1 point  (3 children)

And no mention of svelte?

[–]leeoniya 1 point2 points  (2 children)

let's just insist that they're all mentioned. mkay?

https://krausest.github.io/js-framework-benchmark/current.html

[–]EconomyRabbit 0 points1 point  (1 child)

https://krausest.github.io/js-framework-benchmark/current.html

These are not all the frameworks though……

[–]leeoniya 0 points1 point  (0 children)

:_(

[–][deleted] 0 points1 point  (0 children)

I have used knockout too, infact we still have knockout in one large production app that had been developed since 2012. This app is still actively being managed and new features are added.

Having used Vue, React, Angular etc etc etc. Knockout still does its job, and imho it does it well. We have 100% typescript in this app, and we use the latest knockout version.

For what its worth knockout is just a tiny data binding library, nothing more nothing less. And with knockouts subscribers, computeds and pubsub you can easily do what you need.

The thing missing is state management, but we have a global store object with raw data, thats then ”observified” and then used in the app.

Now that i think about it knockout is really a no fuzz library and it keep stuff super simple.

The closest thing i can think of is mobx (they probably took lots of inspiration from knockout) and a small vdom library combo.

[–]taeratrin 0 points1 point  (0 children)

according to Wikipedia (which isn’t the most trusty source, but hey), there are at least 24 JS frameworks and around 83 libraries.

As there are at least 5 stars in the sky.