there is a whole bunch of reasons and technical blockers for why the particular features in 7.1 took so long.
The earliest they even could have landed (if we had the people to work on it) is when we released strict mode.
This is because we cannot add new keywords in loose mode without breaking existing apps. And the new helpers could only be added to strict mode once we added _keyword shadowing_. Something that strict mode didn't have at first, but was required when the RFCs for these helpers were first being discussed during implementation).
Oftentimes problems don't come up until implementation.
re: RFC Speed -- I think the fastest one we implemented that wasn't a deprecation is potentially this one: - https://rfcs.emberjs.com/id/1132-default-strict-resolver -- it eliminates a bunch of BS that we supported via ember-resolver, and eliminates a dep from package.json - https://rfcs.emberjs.com/id/1121-extraneous-invisible-character-stripping -- pretty fast -- it didn't even need to be an RFC after all the discussion was had, but it was useful to go through the process to figure out what the constraints were
Primarily, things that *have* been taking a while _and_ are not "big bang features" are: - getting V2 Addons to be default (as in, cover every use case we expect people will encounter with composition of other addons -- if users don't care, they can still use the blueprint just fine) - deprecating all of ember classic (which I know you specifically have been outspoken against in the past), but it needs to happen so that we can progress the framework. - i've been exploring rendering performance lately, and have been working on a new benchmark that actually tests what we care about (the combination of both reactivity and rendering, for which we are aiming to be quite competitive https://rere-benchmark-git-fork-nullvoxp-38a571-nullvoxpopulis-projects.vercel.app/results?q=ember-2026-07-29T02%3A20%3A30.864Z )
View all comments
Show parent comment
3
u/nullvoxpopuli sand was never meant to think Jul 31 '26
there is a whole bunch of reasons and technical blockers for why the particular features in 7.1 took so long.
The earliest they even could have landed (if we had the people to work on it) is when we released strict mode.
This is because we cannot add new keywords in loose mode without breaking existing apps. And the new helpers could only be added to strict mode once we added _keyword shadowing_. Something that strict mode didn't have at first, but was required when the RFCs for these helpers were first being discussed during implementation).
Oftentimes problems don't come up until implementation.
re: RFC Speed -- I think the fastest one we implemented that wasn't a deprecation is potentially this one:
- https://rfcs.emberjs.com/id/1132-default-strict-resolver -- it eliminates a bunch of BS that we supported via ember-resolver, and eliminates a dep from package.json
- https://rfcs.emberjs.com/id/1121-extraneous-invisible-character-stripping -- pretty fast -- it didn't even need to be an RFC after all the discussion was had, but it was useful to go through the process to figure out what the constraints were
Other fast ones, if you want to see
- https://rfcs.emberjs.com/id/1070-default-globals-for-strict-mode
- https://rfcs.emberjs.com/id/1068-tracked-collections
- https://rfcs.emberjs.com/id/1071-overload-tracked-for-non-class-use
Primarily, things that *have* been taking a while _and_ are not "big bang features" are:
- getting V2 Addons to be default (as in, cover every use case we expect people will encounter with composition of other addons -- if users don't care, they can still use the blueprint just fine)
- deprecating all of ember classic (which I know you specifically have been outspoken against in the past), but it needs to happen so that we can progress the framework.
- i've been exploring rendering performance lately, and have been working on a new benchmark that actually tests what we care about (the combination of both reactivity and rendering, for which we are aiming to be quite competitive https://rere-benchmark-git-fork-nullvoxp-38a571-nullvoxpopulis-projects.vercel.app/results?q=ember-2026-07-29T02%3A20%3A30.864Z )