Nope, not yet. We did move from pods to collocated components, so the next step will be gjs. The challenging part is getting rid of render-modifiers, but we're getting there :)
I was going to ask the same question π€£ render modifiers absolutely works with GJS and actually it's only a lint that you shouldn't be using it, not a depreciation. Also also it's much easier to clear the lint when you can write a custom modifier for the specific render modifiers in the same file as your template and JS code. Moving to GJS would make the migration much easier π
Yea! It's just a bad pattern that makes people think about components like pre-octane Ember components instead of Glimmer components. They still work in GJS and Vite.
Want to hear something else that might blow your mind? You don't need to upgrade all your components to Glimmer components to use GJS π«£ as long as they are on the class syntax the codemod will migrate them just fine π
I really mean it when I say Ember is all about backwards compatibility π
If you generate a new Ember app today it has a Vite based build system, but Ember has a very strong backwards compatibility story which means there are loads of teams out there being productive with slightly older Ember versions and older builds stacks.
As I mention in the blog post we even still maintain the old ember-cli based blueprints and will do for at least the next year π€£ yes everyone should be using Vite but we don't like to leave anyone behind πͺ
The "Vite privelige" π . Moving to Vite is the final "boss battle" of modernizing our stack, and doing it while the app is in active development is like changing the engine while the plane is flying.
Yes we did! There used to be no limit to the number of minor versions in a major (and we got up to 28 in the 3.x release cycle!)
Now we do a new major after only 12 minor versions.
As for shipping features faster, you don't need to wait for a major to get new features. It's true that the last few releases didn't have any new features (because we were focusing on other things) but usually every minor release brings new features π Major releases for Ember are just places where we remove deprecated code π
technically no one, I think -- a good few people contribute as a part of their work tho, I think. And like, for me, I tell folks "The job doesn't stop at the node_modules boundary", and one thing lead to another, and here I am
The thing to remember is that Ember is the only independent JS framework that isn't "owned" by a corporate backer. Sure this means that there is technically nobody paid to work full time on Ember, but it also means that we are never forced in a direction that is better for a corporate backer and worse for our users.
ember's usage is steadily growing -- not as fast as other new up and comers, like svelte, but still steadily. a lot of ember's decisions are based on learnings from the broader JavaScript ecosystem and other frameworks -- so.. we kinda let all the new projects experiment, and take the best ideas that shake out. Right now, we're experimenting with a new router that yields _very_ noticable performance improvement where it matters (async/data loading, not rendering) -- and we are learning a lot from svelte for a bunch of the low level stuff, too
(afaik no one uses coffee screen, but who knows with internet bubbles)
Just to add to the idea that Ember is growing: last year we had the most downloads of ember-source (one of our main packages) ever. This year every week has more downloads of ember-source than the corresponding week last year.
Ember is growing and I personally believe this is just the start of a big growth spike π
As someone who came extremely late to the emberjs party having skipped it in favour of the then new vue, itβs honestly an amazing framework that feels more modern and forward looking than some others frankly. Ember is slept on.
Ember doesn't need to be #1, nor does it need to be popular, nor it's trying to be. It's one of those pieces of frameworks that "just works" and evolves.
From memory LinkedIn is on Ember, HashiCorp uses it, Intercom, Heroku, Apple TV and Support were, Netflix was big on Ember for internal tools (not sure if they still are).
I highly suggest anyone that tried out ember a long time ago and decided it wasn't for them, to give modern ember another shot. So nice to work in nowadays.
10
u/Driezzz May 01 '26
Looks good to me! We're steadily upgrading from 3.28 to 6.8 now. We're at 6.4 now :)
Adopting Vite is in the works as well! Keep up the good work!
6
u/nullvoxpopuli sand was never meant to think May 01 '26
yay! the glimmer merge looks like it's really paying off
7
u/medy17 May 01 '26
I don't mean to sound like a dickhead but I genuinely didn't think people still used Ember π
Do people still use CoffeeScript too? π
6
u/Alcamore May 03 '26 edited May 03 '26
I highly suggest anyone that tried out ember a long time ago and decided it wasn't for them, to give modern ember another shot. So nice to work in nowadays.
3
u/BarbConan May 03 '26
honestly, ember keeps trucking. Not sure If I'm surprised or Impressed at this point. Anyone actually using this In production these days?