Hacker News Reader

Comment by weeksie | Hacker News Reader

Honestly, Ember has been incredibly frustrating to get going. Mainly in the area of testing—it's a nightmare.

The documentation is nicely formatted but missing a lot of context. For such a large project, it needs more than API docs and the overviews are not especially useful.

Using it with Rails is a nightmare, you have to fiddle with ember rails and if you want to use anything but Handlebars it's a huge hassle (tags, what? I thought we'd collectively moved past that to things like Haml, Jade, Thin, etc. . .)

I love where it's headed and I like a lot of the ideas, but it's been pretty aggravating to get up and running.

View on HN

I started a major rewrite for a Rails App that I'm converting to Rails API + Ember with Ember Data. Yeah, the learning curve has been huge and Ember Data pretty much didn't help things. But, I've stuck with it and everytime I struggle with something (happened first with routing nested resources - still feels a bit magic sometimes), I take a step back and look at the Ember way of doing things and I usually become enlightened with the very well thought out decisions.

For those of you struggling with Ember Data - this is your best friend - https://github.com/emberjs/data/blob/master/TRANSITION.md probably the best documentation on the matter. If you got Active Model Serializers, use the right serializer on Ember data side to get going.

IF you're using Ember Rails - be sure to check that it's pulling the latest Ember Data.

I like that there are more tutorials and demos coming out but seriously, we need some more non-trivial UI examples. Maybe after my project I'll write up a blog post if anyone here is interested.

Thank you! It's good to hear someone else say it. I've made a couple of runs trying to come to terms with Ember; invariably the docs are wrong, and various examples don't work with the currently-released Ember build; and then Googling turns up some other docs for some other version. Maddening to try to figure out what the current reality is.

The third party ecosystem also seems very sparse -- would pay money for the Ember equivalent of Two Scoops of Django, although I'll probably just try Angular instead of waiting to see if things get better. Seems to be vastly more resources for Angular and the rate of development seems much quicker.

Don't use the asset pipeline. Compile your assets and then you can just drop them in the public dir. I use the ember app kit which can build a production distribution.

I love angularjs, way more consistent api, it actually does what you expect.

Re. Haml: try emblemjs.com

Reply on news.ycombinator.com