AngularJS Meetup Sep 2016: Change detection & React vs Angular 2 vs Backbone
Details
IMPORTANT: This meetup will take place in a different location. The new address is 111 8th Ave, between 15th and 16th street.
Requirements:
• Use your real name to RSVP
• Bring your ID to the meetup
• No cancellations allowed. If you fail to show up or if you cancel after Thu at 6:00 pm you will not be able to attend this meetup for the next 3 months.
We will have 2 talks:
Change detection – Angular 1 vs Angular 2
http://photos4.meetupstatic.com/photos/event/d/1/a/4/600_454133668.jpeg
by Vikas Goyal (http://www.vikasgoyalgzs.com/) from Sapient Global Markets (https://www.sapientglobalmarkets.com)
We will talk about what change detection is and why we need it in modern web development frameworks. Then we discuss about how change detection is implemented in Angular 1 and how Angular 2 brings major performance improvements by implementing a new change detection strategy.
Direct comparison of Backbone.js vs React + Redux vs Angular 2
http://pgburt.github.io/images/paul-burt-in-the-flesh.jpeg
by Paul Burt (https://pgburt.github.io) from Ebay (http://www.ebay.com/)
We have our own templating language + reactive components in the form of MarkoJS + Marko Widgets. We use that day to day on the regular. Then we stumbled into a project to create a CMS with a WYSIWIG for managing some of the widgets on our homepage.
We saw it as an opportunity to step outside of our comfort zone, and do a direct comparison of many of the other popular options out there. Three engineers each chose a popular framework, built a prototype, and presented to the group.
We knew we needed features like Drag and Drop functionality, easy and fast updates to the page, and the ability to integrate with some of our own legacy APIs (think: still serves data in an XML / SOAP format).
Our homepage serves up to 80 million hits a day, so we value maintainability and rendering speed equally. This talk is a look at those three frameworks, why we thought it was worth it to do the comparison, and which framework ultimately fit our use-case the best. Hint: we chose Angular 2!