Ember.js 1.0 RC4 released
emberjs.com
Ember.js 1.0 RC4 released
1–10 of 28 posts
Re: Ember.js 1.0 RC4 released
#2I'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.
Re: Ember.js 1.0 RC4 released
#3Can 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?
Re: Ember.js 1.0 RC4 released
#4Can 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 -- it doesn't get significantly more complex than that initial learning curve.
Re: Ember.js 1.0 RC4 released
#5Can 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?
The Ember app that I'm working on has about 20 controllers plus all the models, templates, etc. It's a few thousand LOC right now.
We use it because we don't actually serve (much) HTML. We server up basically an empty DOM and the Ember app uses Handlebars templates to generate the entire webpage as it pulls data from our REST API.
Akamai hosts all our Ember code + handlebars templates + css + images, so the client only hits our servers for the REST API.
I've done some Angular with a simple internal tool, but it didn't see possible (or at least very easy) to take a similar approach so we stuck with Ember.
Re: Ember.js 1.0 RC4 released
#6Can 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 --…
This is the same experience I had. I built a simple Angular app quickly but I soon realized I didn't understand how to go from the sample code on their website to doing more complicated things as the structure of the framework is very different from what I am accustomed to.
Re: Ember.js 1.0 RC4 released
#7Can 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 --…
This was my experience exactly. I started a project with Angular and got the basics set up without difficulty. When it came to integrating Google Maps, it was a nightmare and I switched to Ember. It took me a little while to figure out "The Ember Way" but the integration is very clean and understandable now.
Re: Ember.js 1.0 RC4 released
#8Can 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 haven't built anything in Angular yet, but I can vouch for the Ember side of this. Getting started was pretty painful, but I now feel remarkably productive even in more complicated scenarios.
Re: Ember.js 1.0 RC4 released
#9Can 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?
The Ember app that I'm working on has about 20 controllers plus all the models, templates, etc. It's a few thousand LOC right now. We use it because we don't actually serve (much) HTML. We server up basically an empty DOM and the Ember app uses Handlebars templates to generate the entire webpage as it pulls data from our REST API. Akamai hosts all our Ember code + handlebars templates + css + images, so the client on…
I'm obviously misunderstanding something in your comment because that sounds exactly like how you'd build an app with Angular. Could you explain the issue in a little more detail.
Re: Ember.js 1.0 RC4 released
#10Can 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 of evaluating these two frameworks I found KnockoutJS and I chose it for my large project that is one year into development. After one year with it I love it more now then when I first started. It's not perfect but it is a really well thought out framework, it does lack some documentation, ko.utils I'm looking at you. But it's documentation is vastly superior to the other two frameworks, at least it was a year ago. It's very stable and I prefer the team's approach. The two binding and subscription model is great for solving some intricate problems. It's easily extensible with custom bindings and unlike angular doesn't favour bad coding habits that lock you in to the framework, I forget the name now but their custom HTML tags (I think they call them directives) is nothing but bad news and vendor lock in.