[In continuation from previous post i.e. JS Channel Conference, 2015 – Day 1]
The second day of the conference started with keynote by Yehuda Katz. He spoke about EmberJS and it’s advantages as a framework as well as what’s new, which can be expected in upcoming versions of EmberJS. The core principal of Ember lies in isolation to scale. The framework treats each screen like its own app and this type of isolation helps in scaling big applications (he also pointed that Ember is not meant for small applications or widgets). With the capabilities of glimmer-components in Ember, he mentioned, how it captures good qualities of ReactJS like
1. components own their data to maintain their state
2. one way data flow by default
3. just refresh the component, when something changes
For Ember 2.0, he hinted that, the transition plan will be feedback oriented and more focussed on convention than configuration.
Adriaan de Jonge, did a live coding session to compare Angular2.0 with Aurelia framework. During that, he pointed out various loop-holes, in the design of Angular2.0 and demonstrated how the similar loop-holes are handled by a bit flexible framework, Aurelia. The session proved to be opening new doors for side-lining from mainstream technologies and try out much more suitable(but relatively new in the industry) frameworks.
Post lunch sessions started with hands-on and live-coding workshop by Christian Lilley ,on ReactJS and FLUX. It was a good follow-up of, what was started by Yahuda Katz in the morning as ReactJS, with most of design principals, seems alike Ember or vice-versa. Christian re-iterated, the core principals behind ReactJS components (like it is for glimmer-component of Ember), additionally, he explained about Virtual DOM, a structure which is maintained by ReactJS. In his opinion, Virtual DOM is not the key success point of React, as most of people think, but it is the performance advantage one gets while rendering the Virtual DOM, via ReactJS. He also explained, the surrounding framework FLUX (which is not exactly the framework, but the architecture used by facebook), to best consume power of ReactJS. [Recording of the session can be found here]
Following that was the panel discussions, again involving major discussions about the current status of the web and the JS framework architectures. There were interesting questions from participants to fuel the best out of panel discussion.