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

21–30 of 55 posts

Re: Migrating from Ember.js to AngularJS

#21

Post by tomdale »

creamyhorror wrote: post #19
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…

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…

The Angular guys are incredibly smart (and good looking) and I am not above stealing their good ideas for Ember. It's great having skilled competitors, because it drives us both to build a better product.

I hope you didn't find any personal attacks in my response. I want to be firm about the fact that the article contained gross inaccuracies.

I welcome criticism of Ember.js; as with any open source project, there's plenty to criticize. I would just like that criticism to be accurate.

Re: Migrating from Ember.js to AngularJS

#22

Post by 1qaz2wsx3edc »

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 don't think this is true. For example, AngularJS, as far as I'm aware, does not offer a persistence story at all.

It does have angular-resources for restful interfaces. Which are straight forward and easy to use.

I'll let ember ferment.

Re: Migrating from Ember.js to AngularJS

#23

Post by marknutter »

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…

Well, the fact that you have to come on HN to refute these points means there's a problem. People aren't getting it. This could be a documentation issue, a complexity issue, or a marketing issue. But it's clear there's an issue. Just calling it FUD is disingenuous. It didn't sound like the OP was trying to smear ember.js at all, but instead give some reasons why they moved to angular. The OP doesn't write frameworks and doesn't know the intricacies of every framework that's out there. They presumably know as much as they need to to get shit done and for them angular.js was the more efficient path.

Re: Migrating from Ember.js to AngularJS

#24

Post by jcampbell1 »

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.

This is what I was looking for. I gather the framework is allergic to conditionals.

Re: Migrating from Ember.js to AngularJS

#25

Post by chrixian »

I don't get these kinds posts really maybe because I use Ember (most of the time) but I also use Batman and Sencha Touch... I like that there is so much going on with so many projects in this area of development because it's what interests me...

And while I do feel some of your points aren't very accurate they are after all your feelings and observations and I'm not 100% of the time in love with the state of things either... and then I realize--

Ember is in its infancy and because I have faith in Tom and Yahuda, based on their pre-Ember work and the way they go about moving Ember forward now, I just know in my heart that I'm not wasting my time investing in Ember now and for the future.

Thats a far different feeling from what I get when I use Angular.

Re: Migrating from Ember.js to AngularJS

#26

Post by logical42 »

tomdale wrote: post #16
hakaaaaak wrote: post #14

Earlier quoted context omitted.

> Ember.js does dependency injection too; we just roll it into our conventions so that new developers don't need to learn what dependency injection is. If you have to learn a ton of comp sci terminology to start learning a framework, they blew it. I've been using Angular for months now and although I already knew what dependency injection was, I didn't have to understand the term to use Angular. > Additionally, Ember…

Not to start a flame war, but I'm not sure this is a plus. Full unit coverage is nice for confidence, but can be balls and chains when it comes time to make changes. Ask any of our pre-1.0 users; they'll assure you that the pace of change was breakneck and certainly not hindered by our unit tests.

I will vouch for this as well. I have still, very conflicted feelings about the improvements in the router and having to rewrite large portions of the app I was (and am still) working on.

@tomdale thank you for the breakneck speed in development, it amazes me how much the project has evolved in the time I've been using it.

Re: Migrating from Ember.js to AngularJS

#27

Post by camus »

Angular is great but it has some problems , and i dont think one framework is suitable for all use cases.

- For an app that is form/list oriented ( LOB ) angularJS is the best, plays very well with Bootstrap.

- For an app where i need full control over object lifecycle(create custom events , hook into object creating/destruction), when some animated transition between views or states are needed, i would use BackboneJS or EmberJS, these frameworks play well with require-js.

Iadapted a backbone showcase to angularJS , the whole app is opensourced on github : https://github.com/Mparaiso/silex-bookmarkly and you can test the app live here : http://markme.alwaysdata.net/application . My 2 cents : - AngularJS can get slow when using repeaters on large object lists , i never had that problem with Backbone or Ember. - Directives are tricky , and some tricks( $timeout , element.ready , etc ... ) feel like you dont control anything at all. - since angularJS uses $ to namespace it's variable on models , there is some model corruption happening while loading stuffs from the server. - i found using requireJS was a bit hard ,and having both AMD and IOC containers is ugly ( but orthogonal ). - AngularJS doesnt too much stuff under the hood imho.

Overall , AngularJS is one of the best framework out there for html client apps.

Re: Migrating from Ember.js to AngularJS

#28

Post by collint »

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

Re: Migrating from Ember.js to AngularJS

#29

Post by hakaaaaak »

jcampbell1 wrote: post #24
myhf wrote: post #15

Earlier quoted context omitted.

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.

This is what I was looking for. I gather the framework is allergic to conditionals.

Behavior can be provided through directives via elements, attributes, css class names, and comments.

It isn't "allergic to conditionals". It just drives the logic elsewhere to keep the presentation layer looking as clean as possible to the developer so that you can either focus on the view (template) or the controller or model.

Re: Migrating from Ember.js to AngularJS

#30

Post by laureny »

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…

Calling this "FUD" is a bit over the top. Call it inaccurate information if you wish, but "FUD" implies willful intention to deceive, and I really don't see this in the article.

Sadly, these days, "FUD" has become synonym for "this person is saying something I disagree with".

Post reply on HN