Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Migrating from Ember.js to AngularJS

beust.com

Post reply on HN
Print view View original

41–50 of 55 posts

Re: Migrating from Ember.js to AngularJS

#41

Post by dgregd »

tomdale wrote: post #5

While there's great feedback here, it's interspersed with information that is either outdated or just flat-out inaccurate. Overall, Angular is a much more extensive framework than Ember. I don't think this is true. For example, AngularJS, as far as I'm aware, does not offer a persistence story at all. Injection and testability. Ember.js does dependency injection too; we just roll it into our conventions so that new d…

> This "dirty checking" can quickly lead to pathological performance issues.

I would say that "dirty checking" is a better approach. The code is cleaner and with Object.observe() there are no performance issues even in _edge cases_ with thousands of monitored objects.

Re: Migrating from Ember.js to AngularJS

#42

Post by pieceofpeace »

myhf wrote: post #15
hakaaaaak wrote: post #7

Earlier quoted context omitted.

Like this: {{name}} There are no names in the list

Or, if you don't want the "no names" item in the list at all when it's inapplicable, instead of merely hidden: There are no names in the list. {{name}} Either way you end up with an ugly dom.

Best approach would be to use the 'ui-if' directive from angular-ui

  
    {{name}}
    There are no names in the list
: http://angular-ui.github.com/#directives-if

Re: Migrating from Ember.js to AngularJS

#44

Post by saurabhnanda »

tomdale wrote: post #5

While there's great feedback here, it's interspersed with information that is either outdated or just flat-out inaccurate. Overall, Angular is a much more extensive framework than Ember. I don't think this is true. For example, AngularJS, as far as I'm aware, does not offer a persistence story at all. Injection and testability. Ember.js does dependency injection too; we just roll it into our conventions so that new d…

ES6 supports object proxies, which provide sufficiently rich semantics that we will be able to drop the get/set requirement if you are targeting ES6 browsers. We are ready to add this to Ember as soon as proxies land in popular browsers.

Will, both, EmberJS & AngularJS become faster because of these new core-JS features?

Re: Migrating from Ember.js to AngularJS

#45

Post by patrickaljord »

steveklabnik wrote: post #13
hakaaaaak wrote: post #2

Would be nice if they hadn't closed comments before Peter Wagenet, Yahuda, and the rest from the Ember team could weigh in. I personally like AngularJS a lot, but I also like Rails. Rails 4 has a rails-api project along side of it, which makes it seem like they are starting to spend more time thinking of Rails as provider for a Javascript front-end. Because of Yahuda's involvement, they have also placed more bets on…

> Because of Yahuda's involvement, they have also placed more bets on Ember than Angular the last few years. To be clear: I want rails-api to work well with any JS framework that wants to work well with us. Obviously, Ember is a big target, as conceptually, Rails and Ember are very close. That said, I'm a server-side guy: I don't care what is consuming my JSON, just that I serve the JSON up well. If someone who's big…

Angular can take any kind of json so it doesn't really matter what rails return. It could re-use ember json format just fine.

Re: Migrating from Ember.js to AngularJS

#46

Post by abhishiv »

How does an angular app deal with layouts and regions? I.e. Landing and Loggedin Layout, both with totally different regions.

Marionette prefers Region managers, and I guess ember does it in a similar way. What the angular way of doing it?

Re: Migrating from Ember.js to AngularJS

#47

Post by patrickaljord »

hakaaaaak wrote: post #2

Would be nice if they hadn't closed comments before Peter Wagenet, Yahuda, and the rest from the Ember team could weigh in. I personally like AngularJS a lot, but I also like Rails. Rails 4 has a rails-api project along side of it, which makes it seem like they are starting to spend more time thinking of Rails as provider for a Javascript front-end. Because of Yahuda's involvement, they have also placed more bets on…

AngularJS is agnostic when it comes to json format, it can work with whatever rails-api returns so it could re-use even an ember specific format which is I think the rails format. I've written a rails project to work with angular just fine, you can check it out here: https://github.com/patcito/angularjs_scaffold

It generates everything for you scaffold style :)

Re: Migrating from Ember.js to AngularJS

#48

Post by hakaaaaak »

patrickaljord wrote: post #47
hakaaaaak wrote: post #2

Would be nice if they hadn't closed comments before Peter Wagenet, Yahuda, and the rest from the Ember team could weigh in. I personally like AngularJS a lot, but I also like Rails. Rails 4 has a rails-api project along side of it, which makes it seem like they are starting to spend more time thinking of Rails as provider for a Javascript front-end. Because of Yahuda's involvement, they have also placed more bets on…

AngularJS is agnostic when it comes to json format, it can work with whatever rails-api returns so it could re-use even an ember specific format which is I think the rails format. I've written a rails project to work with angular just fine, you can check it out here: https://github.com/patcito/angularjs_scaffold It generates everything for you scaffold style :)

Nice project, and I like that you can use regular JS with the --language=javascript option. You should make that clear in the README's title which seems to indicate it is CoffeeScript only. Might also want to get your angular dependency through a versioned gem, not jquery-rails, and have (pre) Rails 4 support branch.

Re: Migrating from Ember.js to AngularJS

#49

Post by salmanapk »

taligent wrote: post #36
creamyhorror wrote: post #19

Earlier quoted context omitted.

Your response is certainly fair. I just think it's kind of unfortunate that the competition between JS frameworks has heated up so much of late - I've seen a few potshots aimed at particular frameworks in the last year. I'm tempted to wish that devs/maintainers would evolve their frameworks to occupy distinct, separate niches so they wouldn't have to clash head-on, but that's pretty utopian. (Not that such competitio…

That StackOverflow post is hilarious. Who actually justifies slow performance by quoting the limitations of humans ? Here's a thought for that genius. What if I am showing a dynamic graph with that table .. or I have complex rows .. or animations .. or a trillion other use cases that he can't seem to envisage ? And people on slow computers or mobile devices obviously aren't welcome. Anyway here's a performance compar…

I don't find that post hilarious but good thing: they no longer need to do the dirty-checking in the latest Chrome[1], which will improve performance significantly.

1: https://plus.google.com/112439678898563138768/posts/RZKRBiGX...

Re: Migrating from Ember.js to AngularJS

#50

Post by machty »

collint wrote: post #28
tomdale wrote: post #5

While there's great feedback here, it's interspersed with information that is either outdated or just flat-out inaccurate. Overall, Angular is a much more extensive framework than Ember. I don't think this is true. For example, AngularJS, as far as I'm aware, does not offer a persistence story at all. Injection and testability. Ember.js does dependency injection too; we just roll it into our conventions so that new d…

I lifted the run loop concept. Damn good one. I don't really spend any time pushing my work for use by others. But I agree it ought to be copied by others. Run loops make a great partner in crime with requestAnimationFrame. https://github.com/collin/taxi/blob/master/src/taxi.coffee#L...

For what it's worth, the Ember run loop isn't that fires according to a step timer, but rather a loop that runs to completion in response to specific events (mouse click, keyboard press, response from ember-data). If you're talking about requestAnimationFrame there's a good chance you're talking about an entirely different kind of run loop, though I'd be curious to dig into this deeper.
Post reply on HN