4 ms·

Looks like very biaised towards knockout to me.

by gbog 13y ago

tracker1 13y ago
Yeah.. the couple projects I've done with Knockout seemed to be very easy to get your JS and html muddled, and even harder to make modular. It was probably the easiest to get started with, but more complex tasks were really complicated. It really seems to be patterned after XAML in a lot of ways. I do like it's observable models though... not sure if the 2-way binding is worth the level of overhead it introduces though. Backbone is interesting, and I have yet to use it all in a project, I've used bits and pieces in a couple things so can't comment. It does seem to be the most flexible from those I've talked to about it. AngularJS just seems like a big undertaking, and not sure I'm willing to do it unless I have to. I think a more interesting compare/contrast would be with regards to project packaging, how to handle modules and even building processes. I know RequireJS/AMD has a big lead here, but is it really worth it over say Browserify, or other patterns. Also as build tools go, is Grunt the best and what other options are there? I'd love to see how others structure their projects... I tend to have a /client/(less|images|scripts|fonts) set of directories as a source then optimize/merge/push into /pub/(img|js|css|font) directories. I know that Ruby and Python have mature frameworks, but it looks like NodeJS is growing and taking over a lot of these roles, separately from even other server-side frameworks. My last 3 .Net projects have used Grunt for building client-side tools. I haven't settled on a popular module framework (yet) though... I generally just include the tools I want, and namespace my own code out, which comes out lighter, but less reusable/modular than newer approaches.
- pico303 13y ago
  Let me recommend Yeoman plus Angular. Yeoman is that extra step above and beyond basic Grunt. Integrates Bower so your common components stay separate, then builds out your stylesheets and JS like they should be for deployment. It's a nice way to develop client-side apps. Then give Angular a shot. I'm not a JavaScript superstar, but it was pretty easy to pick up Angular and run with it. I love how they've organized directives and services. Really lends itself to building reusable components for your apps. Just wish the docs, particularly around testing, were a bit better.
- threeseed 13y ago
  Weird. I found Knockout to be very easy to be modular. It supports RequireJS and you can have as many view modals as you like. It's biggest problem is that it still feels like a bit of a hack at times as you have to constantly have to battle between what is a JS object and what is a function.
skore 13y ago
I wanted to dislike it for that reason alone, but alas, the editing was so terrible, I didn't even get to that.

Looks like very biaised towards knockout to me.

by gbog 13y ago

Looks like very biaised towards knockout to me.

Yeah.. the couple projects I've done with Knockout seemed to be very easy to get your JS and html muddled, and even harder to make modular. It was probably the easiest to get started with, but more complex tasks were really complicated. It really seems to be patterned after XAML in a lot of ways. I do like it's observable models though... not sure if the 2-way binding is worth the level of overhead it introduces though. Backbone is interesting, and I have yet to use it all in a project, I've used bits and pieces in a couple things so can't comment. It does seem to be the most flexible from those I've talked to about it. AngularJS just seems like a big undertaking, and not sure I'm willing to do it unless I have to. I think a more interesting compare/contrast would be with regards to project packaging, how to handle modules and even building processes. I know RequireJS/AMD has a big lead here, but is it really worth it over say Browserify, or other patterns. Also as build tools go, is Grunt the best and what other options are there? I'd love to see how others structure their projects... I tend to have a /client/(less|images|scripts|fonts) set of directories as a source then optimize/merge/push into /pub/(img|js|css|font) directories. I know that Ruby and Python have mature frameworks, but it looks like NodeJS is growing and taking over a lot of these roles, separately from even other server-side frameworks. My last 3 .Net projects have used Grunt for building client-side tools. I haven't settled on a popular module framework (yet) though... I generally just include the tools I want, and namespace my own code out, which comes out lighter, but less reusable/modular than newer approaches.

pico303 13y ago
Let me recommend Yeoman plus Angular. Yeoman is that extra step above and beyond basic Grunt. Integrates Bower so your common components stay separate, then builds out your stylesheets and JS like they should be for deployment. It's a nice way to develop client-side apps. Then give Angular a shot. I'm not a JavaScript superstar, but it was pretty easy to pick up Angular and run with it. I love how they've organized directives and services. Really lends itself to building reusable components for your apps. Just wish the docs, particularly around testing, were a bit better.
threeseed 13y ago
Weird. I found Knockout to be very easy to be modular. It supports RequireJS and you can have as many view modals as you like. It's biggest problem is that it still feels like a bit of a hack at times as you have to constantly have to battle between what is a JS object and what is a function.

skore 13y ago

I wanted to dislike it for that reason alone, but alas, the editing was so terrible, I didn't even get to that.