aokolish
Re:Reasons to not use Ember.js
on Monday November 17, 2014 @02:02PM (#8619801)
Correct. This is no fault of Ember's; it's just a characteristic of the language that I dislike.
Re:Reasons to not use Ember.js
on Monday November 17, 2014 @02:00PM (#8619792)
Sorry, I was unclear in the post. Building the dashboard took about 3 months. We then add features to it, and maintained it for 5 months after that.
Re:Reasons to not use Ember.js
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.
Re:Reasons to not use Ember.js
on Monday November 17, 2014 @01:21AM (#8617082)
Hi there. I omitted the hashbang just because I find it ugly.
> Loading those other routes first either loads data or modifies the state of the application in a way that is required to display that route
That should be a non-issue as far as I understand, because visiting a nested route causes the parent route code to be executed first. Hence, the confusion.