Ember.js 1.13.0 and 2.0 Beta Released
emberjs.com
Ember.js 1.13.0 and 2.0 Beta Released
1–10 of 38 posts
Re: Ember.js 1.13.0 and 2.0 Beta Released
#2Oh dear:
EMBER 2.0 BETA
Model-View-Controller is replaced by Model-Route-Component-Service.
Two-way bindings are replaced by data down, actions up (DDAU).
Re: Ember.js 1.13.0 and 2.0 Beta Released
#3Oh dear: EMBER 2.0 BETA Model-View-Controller is replaced by Model-Route-Component-Service. Two-way bindings are replaced by data down, actions up (DDAU). I haven't delved into the details, but it looks like things are starting to move in the direction of React. I'm not entirely surprised. We recently built a full scale app with Ember and Ember Data. Now looking back, React with Backbone feels it could have been an e…
Every JS framework is moving in the direction of React, because React is (in my experience) the best and most logical we have right now.
Re: Ember.js 1.13.0 and 2.0 Beta Released
#4Oh dear: EMBER 2.0 BETA Model-View-Controller is replaced by Model-Route-Component-Service. Two-way bindings are replaced by data down, actions up (DDAU). I haven't delved into the details, but it looks like things are starting to move in the direction of React. I'm not entirely surprised. We recently built a full scale app with Ember and Ember Data. Now looking back, React with Backbone feels it could have been an e…
Every JS framework is moving in the direction of React, because React is (in my experience) the best and most logical we have right now.
And they acknlowedge it : "We would like to thank React for showing that full re-renders can be made efficient. While we did not their precise Virtual DOM approach, their work with Virtual DOM was extremely influential to our approach in Glimmer." Fair play !
Re: Ember.js 1.13.0 and 2.0 Beta Released
#5Oh dear: EMBER 2.0 BETA Model-View-Controller is replaced by Model-Route-Component-Service. Two-way bindings are replaced by data down, actions up (DDAU). I haven't delved into the details, but it looks like things are starting to move in the direction of React. I'm not entirely surprised. We recently built a full scale app with Ember and Ember Data. Now looking back, React with Backbone feels it could have been an e…
> React with Backbone feels it could have been an equally good (if not better) choice.
Superficially it might "feel" like a better choice, but objectively it would have been worse if you're doing anything non-trivial.
The backbone router is severely lacking compared to the Ember Router. Same thing with having a lot of models with relationships between them. Sure there might be Backbone-related projects that try to tackle it — they are all way worse than the Ember equivalents. In my opinion they either lack tests, functionality or have terrible architecture.
I think it's a huge merit of the Ember community that they're moving in this direction. They saw something that worked better and weren't ashamed to say "Well that's better than what we have. We're going to do that instead".
Going by track-record and where they are today, Ember would in my mind be a great choice for any company that wants to start building web applications. Ember-CLI is a huge productivity boost, and I bet any company doing more than a few SPAs has had to build something similar; and it probably ended up way worse than Ember CLI.
I find it very unfortunate that web developers have all put their eggs in the Angular basket. From my point of view the rationale for choosing Angular today seem to be the network effect of readily available developers, and not so much the merits of the framework itself.
The Angular team realised they could do things better, and rewrote their entire framework. The Ember team realised they could do things better, and is incrementally moving towards that while letting you migrate your app with it.
Re: Ember.js 1.13.0 and 2.0 Beta Released
#6Oh dear: EMBER 2.0 BETA Model-View-Controller is replaced by Model-Route-Component-Service. Two-way bindings are replaced by data down, actions up (DDAU). I haven't delved into the details, but it looks like things are starting to move in the direction of React. I'm not entirely surprised. We recently built a full scale app with Ember and Ember Data. Now looking back, React with Backbone feels it could have been an e…
> React with Backbone feels it could have been an equally good (if not better) choice. Superficially it might "feel" like a better choice, but objectively it would have been worse if you're doing anything non-trivial. The backbone router is severely lacking compared to the Ember Router. Same thing with having a lot of models with relationships between them. Sure there might be Backbone-related projects that try to ta…
You make some good points. Yes, I totally forgot how good the Ember router is. As for CLI, we actually did build something similar (because CLI wasn't mature enough at the time I evaluated Ember) and it's holding its own against CLI quite well.
I evaluated Angular (as well as React) before settling on Ember last year. I disliked that it tried to own the DOM and that the concepts and terminology (e.g. transclusions) make it difficult to onboard new developers who weren't already experienced in Angular. Plus (and this is a personal opinion), both Ember and React application code looked more elegant than Angular apps.
Re: Ember.js 1.13.0 and 2.0 Beta Released
#7Oh dear: EMBER 2.0 BETA Model-View-Controller is replaced by Model-Route-Component-Service. Two-way bindings are replaced by data down, actions up (DDAU). I haven't delved into the details, but it looks like things are starting to move in the direction of React. I'm not entirely surprised. We recently built a full scale app with Ember and Ember Data. Now looking back, React with Backbone feels it could have been an e…
Also it's more of a
Model-Route-View-Controller-Component-Service
to
Model-Route-Component-Service
switch.
These things were all present before and many people started to merge the view-controller implementations into a component one.
Re: Ember.js 1.13.0 and 2.0 Beta Released
#8Oh dear: EMBER 2.0 BETA Model-View-Controller is replaced by Model-Route-Component-Service. Two-way bindings are replaced by data down, actions up (DDAU). I haven't delved into the details, but it looks like things are starting to move in the direction of React. I'm not entirely surprised. We recently built a full scale app with Ember and Ember Data. Now looking back, React with Backbone feels it could have been an e…
Every JS framework is moving in the direction of React, because React is (in my experience) the best and most logical we have right now.
Are people always using React with another framework or can you build out full applications with just React? Im looking to start another project and want to try React but not sure if it has everything I'm looking for.
Re: Ember.js 1.13.0 and 2.0 Beta Released
#9I 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?
Re: Ember.js 1.13.0 and 2.0 Beta Released
#10Here is an interesting story about the flarum forum dev and their switch from ember to mithril due to extensibility problems and performance. Hopefully the auhor will blog some more about his experiences.
Mind the bloat if you do not want to sink the boat.