It is the main reason I completely stick to the boring mainstream (like react) now, so I'm never again stuck between "nobody knows Ember" and "this one consultant is charging $28k a month cuz I'm competing with LinkedIn, Netflix, and Apple" and then am stuck with them implementing engines for fun and then I don't have the time to undo it months later - all left me wanting to flee.

Basically, left it for non-technical reasons, just practical "literally nobody except billion dollar companies use this, I've painted myself into a corner" reasons.

But I do have fond memories of building things with it, personally.

  export default class CounterComponent extends Component {
    <template>
      <p>0</p>

      <button type="button">+1</button>
      <button type="button">-1</button>
    </template>
  }

    export default component CounterComponent < Component {
        <template>
            <p>0</p>

            <button type="button">+1</button>
            <button type="button">-1</button>
        </template>
    }

We need more LTS versions of dev tools like emberjs, django, node etc. And am a fan of their RFC process as well. It looks like this is the framework you use if you want to incrementally improve stuff without having to go through radical shifts between versions.

they tried to bring the convention over configuration thought from rails to js.

it worked for people that had crazy engineering resources such as Addepar & Heroku.

but react & angular were just easier to get started with. Angular with their early typescript support in angular 2 then just took the fire out of ember. React with its earlier simple model shifted all the hipsters & newcomers.

It turns out they didn't use any of those and didn't ask questions about them in the interview. :) After a year or so they did start using Angular though.

Anyway, I did end up playing with ember and backbone around that time. Cool to see it's still developed.