CODEWITHSUNDEEP
javascriptbackbone.jsknockout.jsember.js
Martin GOYOT
Martin GOYOT

Reputation: 286

Javascript framework: Knockout, backbone, ember…

I'm currently on a web application project written in javascript with node.js and Express server-side and it's time to consider the client-side of this application. The two questions are:

I've chosen three of these: backbone, knockout and Ember. I read all the questions I found about them but I'm still hesitating. The points to consider are:

EDIT: And what do you think about JavaScriptMVC?

Upvotes: 1

Views: 2356

Answers (3)

himeshi
himeshi

Reputation: 485

If you're thinking of building an application with scalability and maintainability in mind you might want to consider a reference architecture such as Boilerplatejs.

BoilerplateJS incorporates best practices to be used when building a large scale application. Furthermore it ships with libraries such as knockoutjs and also utilities that would help structure and organize your code.

Upvotes: 0

santiagobasulto
santiagobasulto

Reputation: 11686

All those are good frameworks. You can choose anyone and you won't make a huge mistake. Of course, you might like one most than others, but that's a matter of taste. All those frameworks will make your app easy mantainable.

Now, I want to add something more. You asked "Should I consider using a framework"? You can build your own stuff, that's something cool. I'd just recomend to keep in mind good organization of your project. In my short experience, Js is a mess. And these FWs help you to keep your code clean and organized.

1 more thing to add to organization: You should consider some AMD tool, like Require.js

Upvotes: 0

Mark Robinson
Mark Robinson

Reputation: 13278

As @Christian Varga has said in the comments, it depends. However, I would make the following observations:

It is good to mix html with javascript like knockout does?

With knockout you are not forced to mix javascript into the html. See Unobstrusive Event Handling.

Will my application be easily maintainable?

In my experience with knockout , if the application gets especially large the pages do get complicated. However, if you are going for a SPA style page then the code will always get fairly involved. I haven't worked with Ember or Backbone but certainly Backbone does have a reputation for being be good for larger applications.

Will the framework continue and not diappear tomorrow, leaving me in a very uncomfortable situation?

I think you have picked your three frameworks to consider wisely. Knockout and Backbone both have fairly wide adoption. Knockout is to be shipped with MVC4 which gives you some confidence behind its future. Ember is newer but there seems to be a lot of excitement behind it. There is a good discussion of Ember with various references to knockout and backbone here

Hope this helps you evaluate what will be best for your project.

Upvotes: 4

Related Questions