To be fair, and if I'm understanding you correctly, you can use ember-data alongside Ember to get your model layer (or even just use plain Ember.Objects as needed).
Ember fastboot seems like it'll address some of your concerns too - it'll allow for initial rendering of a page on the server with the intention of the client taking over after that.
I use Ember Data along with Ember. Ember Data is my model layer. I should have made that more clear.
As for FastBoot, correct me if I'm wrong, but right now it supports rendering static pages for SEO. This is not useful for business apps. Rehydration on the client-side (what you seem to be referring to) is still being worked on. But it does not replace the server-side application.
At any rate, eventually someone will bring together the best of server and client technologies in one full-stack package. With all due respect to what's out there now, I haven't seen anything approaching the elegance of Ember and Django.
To nitpick, it's the "National Hockey League" (NHL) and has seven Canadian teams and 23 American teams (likely increasing to 8 and 24 soon).
Publishing of salaries has really created another fun side of the games for fans. Numbers junkies now have the luxury of advanced on-ice analytics as well as some cool financial info in the salary cap era.
I was there on a hike along the Via Alpina! Is that Lauterbrunnen and possibly the train to Jungfraujoch?
One of the most memorable times of my life was hiking through there (Meiringen, Grindelwald, and Lauterbrunnen specifically). Very peaceful and meditative.
yes, this is a hike from Murren to Gimmelwald which is quite literally "The Shire" [1] (after a train from Lauterbrunnen). and yes, Jungfraujoch of course.
Ember fastboot seems like it'll address some of your concerns too - it'll allow for initial rendering of a page on the server with the intention of the client taking over after that.