There are 3 places where one can say ember is stringly typed:

1- controller/service dependency injection(no more with octane).

2- ember data API(store.createRecord(modelNameString) and serializerFor(modelNameString)). I don't mind it results in less imports and API might change in the future.

3- this.owner.lookup('$abstractionName:$fileName') => I like this one. It removes the need for an extra line of import code and import path could have been very verbose for something far away in dependency tree.

Therefore, I don't think it is a serious issue anymore.

Majority of the ember source code and internal packages are in typescript and there is a good typescript support for app development via addons. As a person who wrote an ember-cli alternative, I can say with confidence that you can build ember apps in typescript. Despite all that, the type analysis performance overhead/cost of typescript compiler today isn't worth the type benefits for really big SPAs yet in my opinion. I think instead those frontend teams should optimize their hiring and mentoring practices until we have a very fast typescript compiler.

Addon/package authors can write their code in typescript and make it work with JS or TS ember application code today.

TLDR for the ones who made weak typescript arguments here against ember.js: Don't be a hypester and claim certain things without making a good research.

Thanks for this breakdown, very helpful.