# Why i'm leaving ember

**URL:** <https://discuss.emberjs.com/t/why-im-leaving-ember/6361>\
**Category:** Uncategorized\
**Created:** [September 27, 2014, 4:43pm UTC](https://discuss.emberjs.com/t/why-im-leaving-ember/6361 "2014-09-27T16:43:27Z")\
**Posts on this page:** 1\
**Showing post:** 117

<div class="post-metadata">

**Author:** ![jesmith](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/jesmith/32/11707_2.png) [@jesmith](https://discuss.emberjs.com/u/jesmith)\
**Post date:** [November 18, 2015, 7:17pm UTC](https://discuss.emberjs.com/t/why-im-leaving-ember/6361/117 "2015-11-18T19:17:33Z")

</div>

I think a great example of the struggles that cause people to abandon Ember are shown in posts like this.

> [@Handling an action triggered by the same component used in multiple routes](http://discuss.emberjs.com/t/handling-an-action-triggered-by-the-same-component-used-in-multiple-routes/8561/5):
>
> Perhaps some sort of factory service?

It’s a fairly simplistic action, but Ember (or at least the community) doesn’t seem to have a good answer for how to handle this. The downside of opinionated frameworks is that you spend more time having to document, explain, and support those things that fall to the edges of the opinion. The above blog posts references one of them. And it’s a case where routable components aren’t going to help either.

The community does more to address these issues, the more people will stick with Ember.

---

_[View the full topic](https://discuss.emberjs.com/t/why-im-leaving-ember/6361)._