3 ms·
I have a difficult time finding things that differentiate Batman.js from Knockout.js edit - Further research shows RESTful persistence is the highlight differe
by kveykva 15y ago
I have a difficult time finding things that differentiate Batman.js from Knockout.js
edit - Further research shows RESTful persistence is the highlight difference and Batman.js is a bit cleaner.
- encoderer 15y agoTemplates in Batman (eg, your HTML files) are a lot cleaner. Batman is a great choice if you're using CoffeeScript. On the other hand, Knockout has way better docs. Batman will get there eventually. But right now it's still pretty rough going. I've been using batman for a bit now, really loving it. Looking forward to the event system rewrite that they're working on now to close out some open issues.
- dugmartin 15y agoThe templating in knockout is getting a lot cleaner with 1.3 which is in beta. There are now if, with and foreach bindings that use the inner HTML as the template instead of having to write the template as a separate script block.
- knotty66 15y agoKnockout is also probably being included in ASP.NET MVC 4 - it's in the beta - which should help it gain traction especially amongst beleaguered Silverlight developers thanks to it's familiar MVVM / data binding structure.
- knotty66 15y agoAlso Batman has Rails style generators that create a familiar directory structure and a built in server. They're both really neat.