Ember.js 1.0 Released • Hacker News Board

Re: Ember.js 1.0 Released

#101

Post by bwilliams » Mon, Sep 02, 2013, 2:27 AM UTC

digitalzombie wrote: post #95

iamstef wrote: post #47

Earlier quoted context omitted.

comparing angular to ember-data seems strange, no?

Well my reasoning is because angular have a so called model. It's scope. Angular doesn't need a model, it's a MV whatever. Where as ember is MVC. The framework is MVC and it's M is not complete at all. So judging from an overall framework ember is not complete in that respect where as Angular is. Like come on, 1.0 and hey our M in our MVC framework is incomplete. Um... that's shouldn't even be 1.0. 1.0 to them is the…

Nobody is forcing you to use Ember Data. There's quite a few alternatives out there and you can even use $.ajax.

This is a very unfair comparison between a complete stable release of Angular and an alpha of Ember Data that even tells you it's extremely unstable and not production ready.

Re: Ember.js 1.0 Released

#102

Post by ricardobeat » Mon, Sep 02, 2013, 5:31 AM UTC

johncagula wrote: post #99

ricardobeat wrote: post #88

Earlier quoted context omitted.

When writing a single-page app you only need a RESTful API on the backend, much like developing for mobile, to sync your models from the client. Ideally, the models would be shared between client and server without the need for duplicating code. There has been a few steps in that direction in node.js, but it's an ongoing problem that hopefully we'll figure out in the next couple years.

Thanks for your response. To clarify, when you say RESTful API, do you mean the client-side MVC framework issues API calls to a server which then updates the backend (database?). I guess this model is client-centric while the typical Rails app is server-centric (MVC logic executes on the server and then serves the relevant HTML/CSS to the client). Any particular advantages to the client-side framework over the server…

The main advantage would be performance, plus maintainability for complex UIs. Navigation can be nearly instant, since you're only making specific requests for data from the server, instead of shuffling html and reloading dozens of assets all the time.

There are trade-offs, of course: it is a tad more complex than the old way, but that is offset by simpler implementation in the server. Network round-trips are minimized, but you use a lot more memory and CPU on the client, and need more extensive testing. It's a great fit for webapps, not so much for more content-oriented websites.

Re: Ember.js 1.0 Released

#103

Post by Wilya » Mon, Sep 02, 2013, 12:17 PM UTC

iamstef wrote: post #47

digitalzombie wrote: post #35

I sorta learn Angularjs, well went through a few tutorials on Angular for a company. Turned out that company is now doing emberjs and I have to learn emberjs. I have to say EmberData is not production ready. It's modularity is more monolithic compare to Angularjs. There's a lot of moving parts that can break (in term of using emblem, brunch, handlebar, etc...). And the community is much smaller, less books, less peop…

comparing angular to ember-data seems strange, no?

One of the problem is that the tutorial on the emberjs website makes use of ember-data and doesn't show you anything else. You have to dig a bit further to realize what exactly the distinction is and what you can use instead of ember-data. It doesn't really make it explicit (maybe on purpose) that ember and ember-data are distinct projects.

Re: Ember.js 1.0 Released

#104

Post by rapind » Mon, Sep 02, 2013, 12:55 PM UTC

stuartmemo wrote: post #89

yannski wrote: post #34

Earlier quoted context omitted.

Thank you for this video! It nearly convinced me to build my first EmberJS app (I'm coming from a BackboneJS background and I haven't decided yet between Angular and Ember). Will you continue this kind of videos? Building a series by continuing the current "story" could be really really nice.

If you're deciding between Angular and Ember, this video is a entertaining comparison with good examples - http://vimeo.com/68215606

More entertaining than informative I'm afraid. Project Lead v.s. Guy Who Uses. I don't mean that as a criticism of Rob, I just don't think it's fair or expected for him to have the depth of knowledge in AngularJS that Tom has with Ember. I'd have done worse.

I know it's a pain to have to evaluate all of these frikin' frameworks all the time just to get moving, but I'd really recommend building a non-trivial app in both ember and angular.