News for hackers. Stuff that matters.
Re:Reasons to not use Ember.js by tomhallett on Monday November 17, 2014 @01:24AM (#8617089)
The diagram comparing the stacks feels pretty unfair to me. You have one box for "rails", but then break apart ember's stack into "models", "controllers", "routes", etc. a similar diagram could be drawn for activerecord, actioncontroller, etc - right?
Re:Reasons to not use Ember.js by sotirisk on Monday November 17, 2014 @01:49AM (#8617155)
What difference would it make? The Rails box is the same for both columns. He could have ommitted it and just add a generic "backend framework" box with the results being the same.
Re:Reasons to not use Ember.js by aokolish on Monday November 17, 2014 @01:42AM (#8617137)
I considered adding breaking that down further; it's definitely more complex than that. The thing is rails "models", "controllers", "routes" are still there in the Ember version. The point is added concepts, structure, files, etc. with Ember.