I loved ember for years. Even attended EmberConf in portland around 2015. In fact, I'm just weeks away from retiring my last ember codebase that was in production and worked great for a decade (but I haven't updated in 5 years, since I was unable to keep up with all the changes). But after years of the community dying the most slow and boring of deaths, and having an absolute nightmare needing to hire Ember consultants, I really soured on it.
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.
Same here. Loved the LTS thinking and Ember data being built in but hiring was a pain and ecosystem packages were often out of date.
Kudos for sticking it out. But man EmberJS is basically CakePHP at this point. A relic of days gone by. May as well use Marionette or Backbonejs.
I remember my first full time frontend job I applied to in like 2013 the job listing said I should know ember, backbone, and angular. I was kind of living out of my car so I just studied up a bunch on Ember at the time at random Starbucks.
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.
I love that ember is still going. It’s obviously not the number one choice these days, might never have been, but it represents approaches to frontend web dev that are very different from the standard so it’s always great to see the diversity of ideas out there.
I've been waiting for their Polaris edition for a while now. It looks like it is still not released. But am gonna learn Emberjs one of these days. It will be my secondary framework for projects.
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.
This brings back memories, I thought it was long gone in the magpie attention world of frontend frameworks.
Cool, just in time for the maintenance contract in the old legacy project I worked on like 10 years ago.
[deleted]
Backbone if you’re a real engineer.
Before backbone there was already knockout.js which was based on signals. Which is what all the hip frameworks are converging on now anyway. You could have bypassed all the drama.
We could have just stopped at Backbone. It had everything you needed, if you were a real engineer.
GWT still rocks!!
Since an agent could write all the boilerplate needed, I wonder if that offers any more reason to choose Ember over other frameworks/libraries now
I loved ember for years. Even attended EmberConf in portland around 2015. In fact, I'm just weeks away from retiring my last ember codebase that was in production and worked great for a decade (but I haven't updated in 5 years, since I was unable to keep up with all the changes). But after years of the community dying the most slow and boring of deaths, and having an absolute nightmare needing to hire Ember consultants, I really soured on it.
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.
Same here. Loved the LTS thinking and Ember data being built in but hiring was a pain and ecosystem packages were often out of date.
Kudos for sticking it out. But man EmberJS is basically CakePHP at this point. A relic of days gone by. May as well use Marionette or Backbonejs.
I remember my first full time frontend job I applied to in like 2013 the job listing said I should know ember, backbone, and angular. I was kind of living out of my car so I just studied up a bunch on Ember at the time at random Starbucks.
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.
I love that ember is still going. It’s obviously not the number one choice these days, might never have been, but it represents approaches to frontend web dev that are very different from the standard so it’s always great to see the diversity of ideas out there.
I've been waiting for their Polaris edition for a while now. It looks like it is still not released. But am gonna learn Emberjs one of these days. It will be my secondary framework for projects.
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.
This brings back memories, I thought it was long gone in the magpie attention world of frontend frameworks.
Cool, just in time for the maintenance contract in the old legacy project I worked on like 10 years ago.
Backbone if you’re a real engineer.
Before backbone there was already knockout.js which was based on signals. Which is what all the hip frameworks are converging on now anyway. You could have bypassed all the drama.
We could have just stopped at Backbone. It had everything you needed, if you were a real engineer.
GWT still rocks!!
Since an agent could write all the boilerplate needed, I wonder if that offers any more reason to choose Ember over other frameworks/libraries now
not much probably.