4 ms·
With a cursory glance, a lot of these changes make Ember look more familiar for React users, w.r.t. not treating root specially (versus Angular for example) and
by jchw 7y ago
With a cursory glance, a lot of these changes make Ember look more familiar for React users, w.r.t. not treating root specially (versus Angular for example) and with moving away from mixins for more functional composition. All in all I think this is great and would like to take a look at Ember and see what it has to offer nowadays.
- wycats 7y agoYou got that right. We got a lot of inspiration from the React ecosystem, both in terms of component design (the root element is just another element) and composition. Those changes played out differently in the context of Ember, because of the way our APIs work, but the core ideas are sound, and I'm happy that the React community paved the way.
- k__ 7y agoYes, basically all frameworks became React-like after the success of React. In my opinion, the only one that got a really interesting take on components was Cycle.js, the rest simply tried to bend their APIs to look more Reactish.
- nullvoxpopuli 7y agogood ideas are good ideas. The world only gets better when we let ourselves be inspired by others' success
- preommr 7y agoMore like everything is seen from the viewpoint of react. I've seen people lump in frameworks like angular and vue with react while comparing them in a way that don't make sense for the first two.
- DigitalSea 7y agoAurelia is a framework that didn't rewrite their API's to try and become Reactish either. They have been over in their own lane, while Vue seemingly becomes React Lite.
- jchw 7y agoQ: with regard to mixins and root elements, what downsides do you see to being more like React? I can’t see how these aspects aren’t better this way.