EmberJS was the first front-end framework I learned as a web developer, shortly after learning Django. This was before Ember 1.0 . It was cool at first - but on

EmberJS was the first front-end framework I learned as a web developer, shortly after learning Django. This was before Ember 1.0 . It was cool at first - but once I started developing real projects I ran head first into unreadable or cryptic internal stack traces and APIs that forced me to adapt my back-end to fit the needs of the front-end app. A short time later I picked up angular 1.x and was off to the races because anytime I ran into a problem with a feature or design decision I could easily find the hack that would keep my momentum going. I always felt like EmberJS meant well but chose rigidness where it should have been flexible, and flexibility where it should have been rigid. It's probably changed and solved many of these early problems. I want to go back and re-evaluate, but nowadays so many different technologies, frameworks, languages, and tools, are pulling at my time that I don't think I will be able to. FWIW my current stack of choice (and at work) is Golang and Vue (w/Typescript) - which might identify where some of my biases and predilections are.