Hacker News new | comments | show | ask | jobs | submit login
Tomorrow's Ember 1.0 Release: Things to Know (codefellows.org)
51 points by mikeyanderson 1427 days ago | hide | past | web | 17 comments | favorite



> Already in the Chrome App store, the Ember Inspector extension will let you see what your Ember app is doing in production or your development environment. You can also use the inspector on other site's Ember apps as well. Three cheers for easier debugging of your Ember app! Link to the Ember Inspector.

This is cool. AngularJS having a Chrome-plugin debugger was one of the things that got me interested in trying it out. Powerful, specialized debuggers are always a killer feature for any new framework/system.


The defacto web framework. :) Congrats to the Ember Team.


Agreed. Seriously. Great work, team. If anyone is able to help them get to the finish line - as I see they are requesting - go grab a task to work on (https://github.com/emberjs/ember.js/issues/3246) and join the #emberjs-dev IRC channel on Freenode.


This has been a long time coming and the pace of change over the last year (or so, not sure exactly) has been rapid. I worked on a version of an application I am working on with Ember, even moved the backend to Rails 3 to make it work better with Ember Data, but recently switched development on that app and for other projects I am working on to component.io. I like what Ember is intended to be and I think with this release and the tutorials finally catching up to changes in the API it will be a good framework for people to learn. But I find working against it's opinion of how things should work took up most of the time of working on that project. I now build things with a small abstractions that work well for me, not automatically generated routes that I had no end of trouble debugging.

I'm now using the wonderful http://visionmedia.github.io/page.js/ which is practically express for the browser. The data binding support was the reason I originally choose Ember, but it turned out to give me very little in how I built that app, it's not a simple CRUD so the opportunities for binding models to views is fairly small. And, in any case, attaching events to those models works just as well for me. I've actually reused some of the concepts I've learned from Ember, such as creating an app container to store global objects, and created a few simple view and container view classes based on those in component.

So again, awesome news.


Excellent resources. I've been learning Ember over the last few days and I didn't see any mention of these on the Ember.js site. I can see these being very useful tools for development.


The documentation is leagues better than where it was 6 months ago.

I couldn't comprehend much of the Ember docs last time I was faced with a decision point on which front-end framework to use.


This is fantastic news - I'm just finishing up my second Ember app now and I have to say it's pretty amazing how it works. It's a large system with some complex parts, but once you get a handle on what's going on, you can make some truly elegant code. I've been doing javascript/jquery as part of web development for 5 years now, and shifting to ember from raw jquery is as transformative as shifting from cgi scripts to django


They can document it all they want, still seems like Angular is easier to get started with.


I think that's the point, I think Angular is easier also. But once you've mastered Ember, what you can do with Ember in a timeframe, greatly exceeds that of Angular. It's extremely powerful.


Let's not go there again, shall we?

My personal story is that while I liked Ember, it lacked a bunch of other things that were painful to find elsewhere and integrate with Ember (such as includes). I switched to AngularJS because it gives me all this (and many more) out of the box.

Still, I'm not going to start preaching that AngularJS "greatly exceeds Ember".


Because it doesn't - here's a great article examining the scope of the two.

http://eviltrout.com/2013/06/15/ember-vs-angular.html

It's great to make the decision to focus on simplicity over scope - that's a good, defensible choice and I don't think anyone here will fault you for it. But an honest understanding of the extra features you gave up to make that choice will go a long way.


Huh, that's an interesting perspective. What makes it more powerful? Is it a higher level of abstraction thing, like PG suggests makes one language more powerful than another?


This kind of reaction reminds me of the early days of Rails and Django.


Ah, the good old days…


Small examples. Tried understanding something more complicates and got buried in lots of $ signs, scopes, directives, services. Sometimes stuff doesn't work as expected so digging through a huge swatches of angular.js code to understand how somethings works.


Ember is good though i finally decided to use backbone+ractive, best of both worlds.

AngularJS perf on mobile were not that great , Ember came a bit late ,but good luck.


I use ractive as well with TypeScript but I am not writing SPA.

Anyway frameworks only help up to a certain point - you still have to write your application. Just because one picked framework x,y,z don't mean the app is any good.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: