Knockout 3.1 ships

Re:Knockout 3.1 ships by jf22 on Wednesday March 05, 2014 @06:31AM (#7346402)

If you've never done a SPA before just skip knockout and head to angular or ember.

Your app can out grow knockout and then your stuck rolling your own location provider,dependency injection and more.

2-3 years ago knockout was a breath of fresh air but know its just old and dated technology.

[ Parent | on HN ]

Re:Knockout 3.1 ships by shiz on Wednesday March 05, 2014 @07:41AM (#7346589)

Can you elaborate on why knockout is old and dated? It's HTML and JS, just like the others.

And compared to the bloat that is angular and especially ember, I find knockout strikes with simplicity and 'keeping-it-simple'.

[ Parent | on HN ]

Re:Knockout 3.1 ships by taude on Wednesday March 05, 2014 @09:57AM (#7347251)

It's not. And not everything should be architected as a SPA, but more likely multiple page SPAs. Your users probably don't go to every module of a large app with the same frequency...

[ Parent | on HN ]

Re:Knockout 3.1 ships by skilesare on Wednesday March 05, 2014 @02:07PM (#7349031)

Knockout + Backbone Router is all you really need. It will save massive headaches from trying to shoe horn something in to angular or ember.

[ Parent | on HN ]

Re:Knockout 3.1 ships by sehr on Wednesday March 05, 2014 @12:26PM (#7348254)

Or you can just wire up different libraries as needed and forgo the usage of a entire framework...

[ Parent | on HN ]