ReactFoo 2019

ReactFoo 2019

A gathering of over 250 web and mobile developers working with React

About ReactFoo Bangalore:

ReactFoo Bangalore comes back to its original home after completing five successful editions, India-wide:

  1. ReactFoo Bangalore - September 2017
  2. ReactFoo Pune - January 2018
  3. ReactFoo Hyderabad - March 2018
  4. ReactFoo Mumbai - May 2018
  5. ReactFoo Delhi - August 2018

ReactFoo Bangalore will bring together over 250 developers working with React, and who are invested in building a space for conversations around experiences using React in production.
ReactFoo Bangalore is a single-day, single track conference with talks, office hours and Birds of Feather(BoF) sessions. Workshops will be held on 1 and 3 March, before and after the conference.

Who should attend ReactFoo:

  1. Front-end engineers
  2. Teams and companies who are evaluating frameworks to use for running applications in production
  3. Cross platform mobile developers

ReactFoo provides you the opportunity to:

  1. Learn from and network with peers from the industry
  2. Gain insights from case studies of practical implementation, and evaluate ReactJS and React Native for your work
  3. Understand how to run React in production, end-to-end, rather than only build an application with React

Hosted by

A community - for and of - front-end engineers to share experiences with ReactJS, performant apps with React, crafting better User Interfaces (UI) with React and GraphQL ecosystem. ReactFoo also discusses design patterns and user experience. more

Tanay Pratap

@tanaypratap

How we broke React and understood Fiber!

Submitted Feb 11, 2019

We were trying to push the boundaries of web performance with React in Microsoft Teams when we were left with no choice but to get into React’s souce code. What came out was an appreciation of the React’s new Fiber architecture and this talk. This will get into the story of how a bug in React made us all understand Fiber better and in turn advance our Javascript performance knowledge. This isn’t a walk through of the souce code, rather an easy going explanation of one of the biggest rewrites in our beloved library and how those learnings can be applied anywhere, even outside React ecosystem.

Outline

Starts with a story of what we were trying to do with React in Microsoft.
The issue which was filed and Dan acknowledging it after some explanation.
This led to digging deeper in React and thus, Fiber.
Let’s see what is Fiber and how it is the biggest change since React(sorry Hooks but you are about writing code, THIS IS performance!)
What’s the idea of Fiber: the idea of one unit of work
How requestIdleCallback made all of this possible?
What happens if your browser doesn’t support requestIdleCallback?
Demo time: This simplifies the code logic to make the attendees understand and appreciate the ingenuity of React team.
Walk through of the demo code.
Also, this performance hack can be used by any of us, once it hits you, aha!
Closing remarks on Fiber.
The changes and challenges beyond the simplified demo which are there in React’s source code.

Speaker bio

Tanay Pratap lives in Bangalore and works @Microsoft, he is building Teams which is touted as the next generation collaboration tool. He believes in sharing tech via story and thinks he has a gift to make tech easier to understand. This thought of his has been reinforced by reviews of students, professionals, attendees in his numerous talks/workshops/meetups.

Links

Slides

https://www.slideshare.net/tanaypratap1/react-under-the-hood-131341792

Comments

{{ gettext('Login to leave a comment') }}

{{ gettext('Post a comment…') }}
{{ gettext('New comment') }}
{{ formTitle }}

{{ errorMsg }}

{{ gettext('No comments posted yet') }}

Abhay Nikam

Transition from REST APIs to GraphQL

Abstract: REST APIs are used in almost all the web and mobile applications today. Using REST APIs has some disadvantages which cost the application. In this talk, we will walk through some of the use cases where REST APIs failed for us and discuss how moving away from REST to GraphQL helped us solve the problems. more

12 Feb 2019