Terrible post! I'm an Angular/Rails guy myself but this guys just doesn't know how to dig into the internals of something and figure it out. That's what really makes an engineer an engineer.
For those of us coding for a business purpose, we don't often want a library that requires digging into the internals.
Ideally, you want something simple that saves time. But sometimes you have to compromise and use something opaque that just gets the job done without forcing you to understand it.
The curiosity and intellectualism that make an engineer an engineer, in your opinion, can be toxic in a business environment. Spend a lot of time tinkering, learning cutting-edge technology, or reinventing wheels, and your deadline whizzes by. There's a delicate balance.
I only point these things out because, to many people, Ember.js (and many other libraries) are time-savers rather than something we want to deeply dive into just to use them.
Ideally, you want something simple that saves time. But sometimes you have to compromise and use something opaque that just gets the job done without forcing you to understand it.
The curiosity and intellectualism that make an engineer an engineer, in your opinion, can be toxic in a business environment. Spend a lot of time tinkering, learning cutting-edge technology, or reinventing wheels, and your deadline whizzes by. There's a delicate balance.
I only point these things out because, to many people, Ember.js (and many other libraries) are time-savers rather than something we want to deeply dive into just to use them.