Live data from Hacker News

Ember.js 1.0 RC4 released

emberjs.com

11–20 of 28 posts

Re: Ember.js 1.0 RC4 released

#11
post #4
post #3

Can anyone who has tried Ember and Angular on moderately sized apps (500-1k+ LOC) compare their experiences? I'm using Angular, I love how little code I have to write to make testable apps with their two-way binding, and dependency injection. I went from 0 to Todo App in about an hour after I started to learn Angular. Should I give Ember a try?

Ember is a lot harder to go from 0 to Todo App in an hour. There's a fairly steep learning curve, but once you've grokked the "Ember Way", building more complex apps is significantly easier. With Angular, you can build a Todo App in no time, but building anything more complex requires you to understand e.g. Services, Directives, and Transclusion. With Ember, you are just learning about Models, Views, & Controllers --…

from my limited experience with Ember, it appears that it hosts entire application from a single base url, and overrides forward/back buttons so that the page doesn't reload in order to keep state. instead it uses query string view paths and tokens to navigate around right? Does Angular support anything like this?

Re: Ember.js 1.0 RC4 released

#12
post #2

I'm happy to see RC4. Ember has really come a long way since I started using it. Ember itself has really stabilized. I'm really looking forward to 1.0. There is one more thing I'd really like to see before hitting 1. https://github.com/tildeio/router.js/pull/19 is probably the most important thing happening right now. 1.0 will not be there until these problems are addressed. I hope to see the PR make it to 1.0.

Agree. The router needs a little more power and then 1.0 will be pretty sweet.

Re: Ember.js 1.0 RC4 released

#13
post #2

I'm happy to see RC4. Ember has really come a long way since I started using it. Ember itself has really stabilized. I'm really looking forward to 1.0. There is one more thing I'd really like to see before hitting 1. https://github.com/tildeio/router.js/pull/19 is probably the most important thing happening right now. 1.0 will not be there until these problems are addressed. I hope to see the PR make it to 1.0.

This will definitely be in before 1.0

Re: Ember.js 1.0 RC4 released

#14
post #4
post #3

Can anyone who has tried Ember and Angular on moderately sized apps (500-1k+ LOC) compare their experiences? I'm using Angular, I love how little code I have to write to make testable apps with their two-way binding, and dependency injection. I went from 0 to Todo App in about an hour after I started to learn Angular. Should I give Ember a try?

Ember is a lot harder to go from 0 to Todo App in an hour. There's a fairly steep learning curve, but once you've grokked the "Ember Way", building more complex apps is significantly easier. With Angular, you can build a Todo App in no time, but building anything more complex requires you to understand e.g. Services, Directives, and Transclusion. With Ember, you are just learning about Models, Views, & Controllers --…

Very high learning curve but it levels out. It doesn't get more complex unless you make it. It's hard to transition to a fully async environment if you're coming from the server side.

Re: Ember.js 1.0 RC4 released

#15
post #3

Can anyone who has tried Ember and Angular on moderately sized apps (500-1k+ LOC) compare their experiences? I'm using Angular, I love how little code I have to write to make testable apps with their two-way binding, and dependency injection. I went from 0 to Todo App in about an hour after I started to learn Angular. Should I give Ember a try?

You can see an open source, hosted dashboard that we're developing here:

https://github.com/balanced/balanced-dashboard

It's live @ https://dash.balancedpayments.com/

We're currently moving over the old dashboard to the new one, so it's currently a WIP. Happy to field any questions on Github.

Re: Ember.js 1.0 RC4 released

#16
post #4

Earlier quoted context omitted.

Ember is a lot harder to go from 0 to Todo App in an hour. There's a fairly steep learning curve, but once you've grokked the "Ember Way", building more complex apps is significantly easier. With Angular, you can build a Todo App in no time, but building anything more complex requires you to understand e.g. Services, Directives, and Transclusion. With Ember, you are just learning about Models, Views, & Controllers --…

from my limited experience with Ember, it appears that it hosts entire application from a single base url, and overrides forward/back buttons so that the page doesn't reload in order to keep state. instead it uses query string view paths and tokens to navigate around right? Does Angular support anything like this?

What you're describing is pretty much fundamentally a "single page web app". This is a pretty common pattern for frontend apps.

Re: Ember.js 1.0 RC4 released

#17
post #4
post #3

Can anyone who has tried Ember and Angular on moderately sized apps (500-1k+ LOC) compare their experiences? I'm using Angular, I love how little code I have to write to make testable apps with their two-way binding, and dependency injection. I went from 0 to Todo App in about an hour after I started to learn Angular. Should I give Ember a try?

Ember is a lot harder to go from 0 to Todo App in an hour. There's a fairly steep learning curve, but once you've grokked the "Ember Way", building more complex apps is significantly easier. With Angular, you can build a Todo App in no time, but building anything more complex requires you to understand e.g. Services, Directives, and Transclusion. With Ember, you are just learning about Models, Views, & Controllers --…

Learning directives, services, and the scary sounding "transclusion" has not been an issue at all for my team and I who are using angular on a very large project and loving it. Directives are quite simple once you understand the basic principles. Transclusion when actually explained (http://www.egghead.io/video/cjrBTjMvruI) is a trivial and obvious concept. I understand the confusion one may have around services/factories/providers because they are all very similar and in some ways little more than syntactic sugar for a single API, but once their differences are sorted out as in this blog post (http://iffycan.blogspot.com/2013/05/angular-service-or-facto...) they too become very natural.

Re: Ember.js 1.0 RC4 released

#18
post #3

Can anyone who has tried Ember and Angular on moderately sized apps (500-1k+ LOC) compare their experiences? I'm using Angular, I love how little code I have to write to make testable apps with their two-way binding, and dependency injection. I went from 0 to Todo App in about an hour after I started to learn Angular. Should I give Ember a try?

I'm throwing my 2 cents in, although I haven't built a large scale app with either, I did do a full evaluation of both before my latest large app and I decided on neither one. There were many reasons but every time I wanted to do anything that was remotely non-trivial both fell apart. Although most of that had to do with the MVC pattern more than the actual framework (but the two are tied intricately) In the process…

That's pretty much the same conclusion I came to. Wake me up once ember-data is stable and can support things like range queries and pagination, and just generally dealing with a small subset of data.

Re: Ember.js 1.0 RC4 released

#20
post #4
post #3

Can anyone who has tried Ember and Angular on moderately sized apps (500-1k+ LOC) compare their experiences? I'm using Angular, I love how little code I have to write to make testable apps with their two-way binding, and dependency injection. I went from 0 to Todo App in about an hour after I started to learn Angular. Should I give Ember a try?

Ember is a lot harder to go from 0 to Todo App in an hour. There's a fairly steep learning curve, but once you've grokked the "Ember Way", building more complex apps is significantly easier. With Angular, you can build a Todo App in no time, but building anything more complex requires you to understand e.g. Services, Directives, and Transclusion. With Ember, you are just learning about Models, Views, & Controllers --…

I'd say that once you've mastered Angular concepts like services and factories, dependency injection, etc., it's far easier to build complex applications in it than in Ember. That's because the abstractions Angular introduces are focused around writing decoupled and reusable code.

If you want to build an app in an hour, I'd suggest knockout instead of either ember or angular.

Post reply on HN