Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Choosing the Right JavaScript Framework

airpair.com

Post reply on HN
Print view View original

61–70 of 91 posts

Re: Choosing the Right JavaScript Framework

#61

Post by geodude »

Fjejfhfheifjv wrote: post #12

JS frameworks are absolute cancer. They do nothing but kill page load times and degrade user experience: since when is it a good idea to recompile the whole entire standard library each time a program is run? They're also completely redundant in the modern browser, since standard compliance has gotten much better and more features have been added to HTML/JS/CSS. It's just yet another api that developers have to learn…

wow , is this the ... show HN hyperbole thread??? ... they do something ... thats why they slow down the page ... but you know the page wouldnt even be there if you didnt have a tool to speed up your development ... I hope you have fun with your css transitions call me when you want some two way data binding with ajax calls ... I think I know some tools that help do that :>

Re: Choosing the Right JavaScript Framework

#62

Post by henryw »

bellerocky wrote: post #44

> Backbone lacks support for two-way data binding Actually Backbone is painful because of the two way data binding. You do have to write way more boiler plate, but forms and actions in views will update your models and so will content coming in from the server and your event listeners have to be able to ensure that your events don't runaway from you causing all kinds of problems. Like view action -> updates model ->…

Rivets.js can be added to backbone fairly easily to support 2 way binding.

Re: Choosing the Right JavaScript Framework

#63

Post by morty16 »

clairity wrote: post #56

i appreciate the author's effort but don't feel like i have a better handle on the applicability of each framework to real projects (like many similar articles). basically, this article lists some good and bad features of each framework with some light commentary about a few of those features, which means it doesn't really help you answer the question implied by the title ("which js framework should you choose?"). i…

There's a recent release by O'Reilly called "Choosing a Javascript Framework" (http://shop.oreilly.com/product/9781939902085.do) that you might want to look at.

It covers the same frameworks (Angular, Backbone, Ember) and also mentions Polymer and React.

~20$ for the early access version.

Re: Choosing the Right JavaScript Framework

#64

Post by andrewvc »

nacs wrote: post #60
megaman821 wrote: post #49

Earlier quoted context omitted.

React + what? Is there a standard router/controller and model that get's used with React? I think they just could have added the line "As an alternative to using underscore templates in Backbone, you can use React instead."

There are a couple React-only routers but a lot of React.js people (including myself) use Backbone for the router/controller.

I'm actually using 'director' which works great, much simpler.

Re: Choosing the Right JavaScript Framework

#65

Post by andrewvc »

megaman821 wrote: post #49
andrewvc wrote: post #6

What, no React/Flux? How can this be a serious comparison without React?

React + what? Is there a standard router/controller and model that get's used with React? I think they just could have added the line "As an alternative to using underscore templates in Backbone, you can use React instead."

Well, react/flux completely replaces backbone except for the router. The models go away completely, as do the views.

Re: Choosing the Right JavaScript Framework

#66

Post by compedit »

megaman821 wrote: post #49
andrewvc wrote: post #6

What, no React/Flux? How can this be a serious comparison without React?

React + what? Is there a standard router/controller and model that get's used with React? I think they just could have added the line "As an alternative to using underscore templates in Backbone, you can use React instead."

There's no standards, but at this point I'd say Flux + React-router are quickly becoming it. react-router is made in the spirit of Ember's which is pretty well liked.

- Flux Architecture Pattern [0]

- React Router [1]

Note that there isn't really a prescribed model in Angular aside from $scope either.

[0] - http://facebook.github.io/flux/

[1] - https://github.com/rackt/react-router

Re: Choosing the Right JavaScript Framework

#68

Post by someone13 »

bsimpson wrote: post #53

I just did a bunch of research on state-of-the-art JS architectures for a new project I'm working on, and neither of my first two choices are on this list. (Granted, they aren't restricted to MVC either.) Polymer is interesting because it's the first one that's geared around the idea that the browser is an app rendering engine, not a document reader. Being able to declare your own HTML elements and bind them together…

If you don't mind sharing, have you done any research on data layers for React? From what I can see, there seems to be three major schools of thought: the Flux architecture, using Backbone's models, or just writing something custom.

Re: Choosing the Right JavaScript Framework

#69

Post by clairity »

morty16 wrote: post #63
clairity wrote: post #56

i appreciate the author's effort but don't feel like i have a better handle on the applicability of each framework to real projects (like many similar articles). basically, this article lists some good and bad features of each framework with some light commentary about a few of those features, which means it doesn't really help you answer the question implied by the title ("which js framework should you choose?"). i…

There's a recent release by O'Reilly called "Choosing a Javascript Framework" ( http://shop.oreilly.com/product/9781939902085.do ) that you might want to look at. It covers the same frameworks (Angular, Backbone, Ember) and also mentions Polymer and React. ~20$ for the early access version.

nice! seems a bit pricey for a rough draft ebook though. but i do like that it includes polymer and react, which i know little about.

what i find interesting with these frameworks is that they're all moving the templating engine (something like coldfusion from 15 years ago, ha!) to the frontend... part of the ebb and flow of server vs client side computing i guess.

Re: Choosing the Right JavaScript Framework

#70

Post by juriga »

someone13 wrote: post #68
bsimpson wrote: post #53

I just did a bunch of research on state-of-the-art JS architectures for a new project I'm working on, and neither of my first two choices are on this list. (Granted, they aren't restricted to MVC either.) Polymer is interesting because it's the first one that's geared around the idea that the browser is an app rendering engine, not a document reader. Being able to declare your own HTML elements and bind them together…

If you don't mind sharing, have you done any research on data layers for React? From what I can see, there seems to be three major schools of thought: the Flux architecture, using Backbone's models, or just writing something custom.

I'm currently using Fluxxor[1] which reifies the Flux architecture with Stores and a central dispatcher. I did some research into Backbone.Model bindings but eventually decided to go "full Flux". I've yet to regret my decision even though my app has grown quite complex.

The best part is, thanks to React & Flux I'm building a large scale web app without jQuery for the first time in my life :)

[1] http://fluxxor.com/

Post reply on HN