Ember.js 1.13.0 and 2.0 Beta Released • Hacker News Board

Re: Ember.js 1.13.0 and 2.0 Beta Released

#21

Post by sergiotapia » Sat, Jun 13, 2015, 1:59 PM UTC

adwhit wrote: post #9

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?

You can dive right into Ember with this book with zero previous experience: 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 - 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

Re: Ember.js 1.13.0 and 2.0 Beta Released

#22

Post by hajile » Sat, Jun 13, 2015, 2:03 PM UTC

Nemcue wrote: post #5

hliyan wrote: post #2

Oh 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…

Most React devs use react-router which is heavily inspired by ember's router but the JSX-syntax makes it easier to work with IMHO.

That said, I think Ember's an excellent choice and basically on par with React (it's up to your development style).

Re: Ember.js 1.13.0 and 2.0 Beta Released

#23

Post by aikah » Sat, Jun 13, 2015, 2:09 PM UTC

Nice, contrary to some I believe competition is good and the more the merrier, so I 'm really really impatient to test the Ember.js 2.x beta.

Re: Ember.js 1.13.0 and 2.0 Beta Released

#24

Post by aikah » Sat, Jun 13, 2015, 2:13 PM UTC

johnsberd wrote: post #8

Tankenstein wrote: post #3

Earlier quoted context omitted.

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.

The only thing you need is Ajax and you have it right here in the browser without the need of a third party library. All the rest can be handled by React and its plugins.

That's how I do things, React + raw Xml Http requests. Since JSX is already a layer on its own no need to add yet another layer of complexity.

Re: Ember.js 1.13.0 and 2.0 Beta Released

#25

Post by constantlm » Sat, Jun 13, 2015, 2:22 PM UTC

Nemcue wrote: post #11

UserRights wrote: post #10

Here 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.

You didn't provide a link. I assume you were going to link the blog post announcing their switch to Mithril — that didn't contain any rationale behind it. I did find this however, which goes into details about why Ember was not a good choice for them: http://discuss.flarum.org/139-introducing-flarum-s-fast-new-... Seems to be a well based choice. Doesn't seem to have anything to do with performance though. While Mith…

That "template" is really not okay.

Re: Ember.js 1.13.0 and 2.0 Beta Released

#26

Post by Tankenstein » Sat, Jun 13, 2015, 2:49 PM UTC

geoffroy wrote: post #4

Tankenstein wrote: post #3

Earlier quoted context omitted.

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 !

Yup, i really like how the js community doesn't hate on other frameworks/libraries, but instead they use each other's ideas to better their own.

Re: Ember.js 1.13.0 and 2.0 Beta Released

#27

Post by Tankenstein » Sat, Jun 13, 2015, 2:53 PM UTC

johnsberd wrote: post #8

Tankenstein wrote: post #3

Earlier quoted context omitted.

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.

Just pure react is great for tiny things, but for large applications you should use React with Flux architecture with alt or flummox or reflux or whatever you like, it simplifies things in the long run.

Of course you would need to do things like ajax or routing, for which there are endless libraries, or you can just go pure XHR. React-Router is terrific for routing.

Re: Ember.js 1.13.0 and 2.0 Beta Released

#28

Post by steveklabnik » Sat, Jun 13, 2015, 3:27 PM UTC

hliyan wrote: post #2

Oh 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…

> things are starting to move in the direction of React.

Not just interface wise, but internally: the new Glimmer engine is similar to React as well, but takes advantage of what Handlebars knows about how templates can change to do less diffing. (I think React is gaining something similar soon too)

Re: Ember.js 1.13.0 and 2.0 Beta Released

#29

Post by lobster_johnson » Sat, Jun 13, 2015, 4:20 PM UTC

hajile wrote: post #22

Nemcue wrote: post #5

Earlier quoted context omitted.

> 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…

Most React devs use react-router which is heavily inspired by ember's router but the JSX-syntax makes it easier to work with IMHO. That said, I think Ember's an excellent choice and basically on par with React (it's up to your development style).

It's been a while since I used react-router, but I think this is one place where the Flux flow is better.

Navigation is state, so we built a store to track it. It mediates between a UI model (which abstracts the window location and pushstate stack) and an internal state. Routing involves dispatching an action to request a specific URL, and changing the view to the navigation state is handled by the app's root "application" component, which then sends parameters onward to its current "view" component. There's a simple mapping of route names to views.

Re: Ember.js 1.13.0 and 2.0 Beta Released

#30

Post by lobster_johnson » Sat, Jun 13, 2015, 4:26 PM UTC

k__ wrote: post #12

johnsberd wrote: post #8

Earlier quoted context omitted.

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.

React is the "View", so you need something like Backbone to fuel it. Roll your own, use Backbone, Flux (made by FB especially for React) or Reflux (third party. Flux re-imagined).

I would advise against using Backbone with React/Flux. First, because you don't need it, and secondly, because Backbone is mutable by default, which can cause all sorts of data flow bugs.

Once you buy into the Flux methodology (not necessarily Flux as described by Facebook), a lot of the concerns that Backbone handles melt away. You don't need observable collections and models because all state changes are explicit and data moves in just one direction. Given that Backbone's core is just a thin layer on top of XMLHTTPRequest, you're better off just doing XHR yourself, with POD objects for data.