Migrating from Ember.js to AngularJS • Hacker News Board

Re: Migrating from Ember.js to AngularJS

#51

Post by CamShaft » Tue, Feb 05, 2013, 3:35 PM UTC

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…

That jsperf wasn't very accurate. The ember run loop holds all changes and waits for the program to execute before writing to the dom, which is great. Angular does this too by default unless you force it with $scope.$digest(); which is what they've got here. I edited it to show what's really happening http://jsperf.com/angular-vs-knockout-vs-ember/85

Re: Migrating from Ember.js to AngularJS

#52

Post by nilliams » Tue, Feb 05, 2013, 4:25 PM UTC

taligent wrote: post #38

jcampbell1 wrote: post #33

Earlier quoted context omitted.

I think you described exactly what I meant by "allergic to conditionals": a philosophy that conditional logic never belongs in the presentation layer. I didn't intend to imply a value judgement.

> I didn't intend to imply a value judgement. I will. That seems dumb. Why are conditionals not allowed in presentation layer but repetition is ?

It's a judgement call. Some people are wary that going nutty with conditionals in templates could result in littering bits of 'business logic' in them - they prefer to take an all-or-nothing stance and go for nothing.

Personally I like the sort of middle-ground approach that Handlebars [1] has, I'm fine with basic 'truthy/existence' type checks, but will avoid templating languages that allow 'any old code'.

I think this sort of discipline (picking a deliberately restrictive library) is probably more useful for teams than individuals (who are capable of limiting their own conditional crazy).

[1] http://handlebarsjs.com/

Re: Migrating from Ember.js to AngularJS

#53

Post by craftman » Tue, Feb 05, 2013, 5:13 PM UTC

Beside the fact this guy is well know for his trolling ability, he is working for Google, which is the company supporting the angular team.

Re: Migrating from Ember.js to AngularJS

#54

Post by craftman » Tue, Feb 05, 2013, 5:29 PM UTC

craftman wrote: post #53

Beside the fact this guy is well know for his trolling ability, he is working for Google, which is the company supporting the angular team.

My mistake, he actually has left Google: http://beust.com/weblog/2010/05/13/leaving-google/

Re: Migrating from Ember.js to AngularJS

#55

Post by gkatsanos » Sat, Feb 16, 2013, 1:39 PM UTC

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…

The documentation is indeed problematic because of the way it is written and the omissions mostly around Ember-Data. I don't see how I could develop a web-app without having detailed info on how the Rest adapter works.. (for example I don't know how to change the default mapping). I suggest the guide is re-written following a step-by-step approach, and maybe a screencast. (just see what the meteor guides did!) If you're a beginner, there's no way on earth you can understand what you need to do in order to build a very basic web-app. And because of the changes in syntax (makes sense, it's a pre) most of the other screencasts or guides or blog posts on the web are outdated. Seems to me, and in order to be 100% fair, that most of these frameworks are quite new, and I guess we need to give the devs the time and the space to do things right. Most of them are not even 1.0 so... Patience!