News for hackers. Stuff that matters.
Re:React vs. Ember – EmberNYC slides by rakoo on Tuesday September 02, 2014 @05:36PM (#8260308)
> separating the view (which a team of designers can freely modify without worrying about breaking anything or even touching the logic) from any logic that can handle events

Where does the designer's job stop ? Does he not handle animation ? Should he be in charge of CSS too, because that's how you do basic animations ? Why shouldn't he be in charge of slightly heavier animations, just because they're in javascript ?

The point of the authors (which I agree with) is that the whole notion of "view == template" is wrong, and thus "view == html+css files" is wrong. A view is the thing the user interacts with: a button, a list of items, a search bar. All these components should be handled as a whole, and should be handled independently from one another. If a component doesn't need any javascript for it's logic, fine; if another component needs some javascript for whatever reason it's nonsensical to separate this javascript. A design doesn't always stop purely at static appearance.

The fundamental unit is the object you're working on, not the technology you're using.

There are no comments on this comment yet.