Why Angular, Ember, or Backbone don't work for us.
1–10 of 20 posts
Re: Why Angular, Ember, or Backbone don't work for us.
#2"I want two-way binding only, but I'm forced to take the whole framework. There is too much overhead for me. I hope they will make the data-binding a separate piece and make it simpler."
How about Knockout.js? http://knockoutjs.com/
Re: Why Angular, Ember, or Backbone don't work for us.
#3Neat. Would be super interesting to see what the architecture is like, how the modules are laid out etc.
Re: Why Angular, Ember, or Backbone don't work for us.
#4Also, how many people are working on this codebase? :)
Re: Why Angular, Ember, or Backbone don't work for us.
#5"I want two-way binding only, but I'm forced to take the whole framework. There is too much overhead for me. I hope they will make the data-binding a separate piece and make it simpler." How about Knockout.js? http://knockoutjs.com/
Looks decent. With a quick look the the binding system looks simpler than in Angular and the docs are not blowing up. They openly love jQuery. Much closer to my taste. I picked up the 3 frameworks on my blog entry because they seemed to be the most talked about. Have to keep an eye on this.
Re: Why Angular, Ember, or Backbone don't work for us.
#6Neat. Would be super interesting to see what the architecture is like, how the modules are laid out etc.
The whole client will be open sourced later once it's properly packaged. It takes time.
I'll first release the syntax highlight package, which supports 50+ languages and is super small. Then I'll first release the json-rpc communication piece. Finally the client.
Re: Why Angular, Ember, or Backbone don't work for us.
#7Also, how many people are working on this codebase? :)
I do most of the work + 2 other contributors.
Re: Why Angular, Ember, or Backbone don't work for us.
#8Neat. Would be super interesting to see what the architecture is like, how the modules are laid out etc.
The whole client will be open sourced later once it's properly packaged. It takes time. I'll first release the syntax highlight package, which supports 50+ languages and is super small. Then I'll first release the json-rpc communication piece. Finally the client.
Awesome
Re: Why Angular, Ember, or Backbone don't work for us.
#9"I want two-way binding only, but I'm forced to take the whole framework. There is too much overhead for me. I hope they will make the data-binding a separate piece and make it simpler." How about Knockout.js? http://knockoutjs.com/
This example from the docs seems quite heavy:
Feels a bit strange to define functions on the HTML code.
Re: Why Angular, Ember, or Backbone don't work for us.
#10nice post. Could you go into more detail about the controller snippet? What are you doing after the "// listen to events on model".