I’ve used Ember for years professionally on an app that I believe is pretty well suited to Embers strengths. I’ve always been happy with it, but also always taking a look at other frameworks to see how the space is evolving. Octane is a breath of fresh air I did not know I needed. I started working in Ember prior to VS Code, so development environments for web applications have come along way and I don’t think I knew what I was missing out on.
Ember pre-octane did not really support things like native classes. Everything you create was an object wrapped by a factory function. This means that IDE support for things like finding references to methods, renaming symbols, etc never worked across files. As I’ve been converting everything to use native classes suddenly I have far better refactoring capabilities (even things like ‘Peek Definition’ seem so advanced!) The Ember Community has built some excellent tooling alongside this release to allow for better syntax highlighting and auto-complete in the handlebars templates. It’s a much different feeling writing an Ember application today than it was when I started years ago.
If you haven’t written an app with Ember, I encourage you to test it out. It’s a very easy framework to write for and it gets better as you add team members and grow the codebase.
Agree here. There’s another thing I love about Ember. As a backend person, I don’t frequently (but sometimes) work in frontend. With Ember, I always roughly know my way around. It’s not like every frontend is a react+100 plugins. I can go away and come back and it’s still by and large the same.