Geek asks and answers

Should I follow the trends and use Knockout.js or Backbone.js?

My team and I will soon begin developing a new web service (vtv).

Most of the material will be processed and processed through the json api, but we need a decent control panel for users who want to access their data in the gui environment.

We are discussing whether to design a control panel with a frame such as a knockout or spine, or if we should just stick to our classic stack.

As a loyal Javascript fan and developer, I used both knockout and the foundation for some minor applications in my free time, and I can already see how difficult it is to combine all these series in real production.

Is it worth it to spend extra money to follow trends and give the user a faster guy?

My company seems interested in fast dollars, so please tell me what arguments to use!

Thanks =)

+3
source share
3 answers

I cannot comment on Knockout, but the Backbone is absolutely brilliant. This is a small frame to study, and as soon as you hang it, you will find that it does what each structure should do in its own way: implement bits that you would implement anyway, and think about the problems associated with what You will understand a little below the line.

, , .

, , , . , API, , , Backbone. , - , ( , ), , !

+4

" gui"

. , , , . , .

,

, .

0

, /, .

/ , , !

, .

0

More articles:


All Articles