If you use Ember or have used it in the past, what would it take for you to feel great about using it for your next new project (and recommending it to your friends for new projects)? Feel free to say "I'd already use it" but be honest :)
-
-
Replying to @wycats
Ember desperately needs a "community package love" czar or something. There are FAR too many "big" packages that are left unattended because the dev left their company and aren't using ember anymore.
2 replies 0 retweets 13 likes -
Replying to @peregrine @wycats
Ember desperately needs to move away from Ember Data, its got weird side effects everywhere and the file-based configuration is a nightmare.
3 replies 0 retweets 9 likes -
Replying to @peregrine @wycats
The one thing keeping me from Ember for large applications is dealing with Ember Data
1 reply 0 retweets 1 like -
you don't have to use it. Ember Data is just like any other addon and just because the default blueprint brings it does not mean you have to use it. you can just use plain AJAX or something sophisticated like
@OrbitJS instead.1 reply 0 retweets 1 like -
Replying to @TobiasBieniek @yburyug and
Absolutely, but to the beginner, to the learner, its the default suggested way. Its in all the guides, its generated. And this is the exact response I got on Ember slack when I suggested that maybe Ember Data isn't perfect.
1 reply 0 retweets 1 like -
Replying to @peregrine @TobiasBieniek and
Let me be a little more subtle. I think a good way to use Ember Data is to treat it like a dumb store for data that can be updated. The adapter and serializer story makes it look much more complex than it really is, which makes "you don't have to use it" fall flat.
1 reply 0 retweets 3 likes
In the near term, we plan to pull out adapters and serializers into add-ons to highlight the fact that they are intended to be optional and often not needed.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.