3 ms·
I am excited about this release. Once things have settled down I think Ember 2.x will have a much shallower learning curve than 1.x. However it is a shame that
by adwhit 11y ago
I am excited about this release. Once things have settled down I think Ember 2.x will have a much shallower learning curve than 1.x.
However it is a shame that routable components haven't made it in yet. I'm about to start a new, medium-sized Emberjs project, but I'm unsure whether to wait another 6 (or maybe 12) weeks for this feature. Any suggestions?
- jherdman 11y agoI'd jump right in. The upgrade path has been very gentle for quite some time now.
- bttf 11y agoSam Selikoff's article on preparing for Ember 2.0 includes a pattern that could easily upgrade into routeable components [0]. [0] http://www.samselikoff.com/blog/preparing-for-ember-2.0/ http://www.samselikoff.com/blog/preparing-for-ember-2.0/
- sergiotapia 11y agoYou can dive right into Ember with this book with zero previous experience: https://pragprog.com/book/mwjsember/deliver-audacious-web-apps-with-ember-2 https://pragprog.com/book/mwjsember/deliver-audacious-web-ap... I've read lots of Ember books and have seen a couple of screencasts including CodeSchool's Warming up With Ember and hands down this book is the best I've read. There's also https://leanpub.com/ember-cli-101 https://leanpub.com/ember-cli-101 - but I'm not sure if the author has updated it to use pods and components since the last time I've read it. It's in beta, but in it's current state it's good enough. The idea right now is to create as much as you can as self-contained Ember components and pod structure. I know that doesn't make much sense if you're new to Ember, but imagine your project structure being: /app /login /register /profile /profileedit /forgotpassword /about /contact