##JSFoo 2016: Theme
We are inviting full talks (40 mins), crisp talks (15 mins + 5 mins Q&A), and 3-6 hour long (hands-on) workshops from practitioners on the overall theme of speed and performance, including the following topics:
- Architecting for performance – case studies on how you got faster response times
- Best practices: debugging and profiling on the web, measuring performance
- Handling large volumes of data in the browser
- Building and deploying web apps eg webpack, travis
- Modern web technology: Angular 2, React
- Progressive Web Apps
- JS off the web – raspberry pi, IoT
- The cutting edge: elm
Every proposal MUST be accompanied by:
- A three minute preview video where the proposer gives an elevator pitch about the talk.
- Detailed outline of the talk – either in the form of draft slides, mind map and/or textual description.
- If you are proposing to speak on a topic where the code is not open-sourced yet, the editorial panel will consider your proposal only if the code is made open-source at least three weeks before the conference.
Without the above information, your proposal will not be considered for review.
If you are submitting a Workshop Proposal, you must clearly state:
- Background knowledge that participants must possess in order to attend your workshop.
- Details and links to software / packages which participants must install before coming to the workshop.
- Laptop configuration.
- Links to background reading material and GitHub repos.
- Duration of the workshop.
- Maximum number of participants who can attend your workshop.
- Instructor’s past experience with conducting workshops.
There is only one speaker per session. Workshops can have two or more instructors.
Entry is free for selected speakers.
Due to budgetary constraints, we prefer speakers closer to home. But if we think you stand out, we’ll provide a grant to cover part of your travel and accommodation to Bangalore. Grants are limited and are made available to speakers delivering full sessions (40 minutes or longer) only.
HasGeek believes in open source as the binding force of our community. If you are describing a codebase for developers to work with, we’d like for it to be available under a permissive open source licence. If your software is commercially licensed or available under a combination of commercial and restrictive open source licences (such as the various forms of the GPL), please consider picking up a sponsorship. We recognise that there are valid reasons for commercial licensing, but ask that you support us in return for giving you an audience. Your session will be marked on the schedule as a sponsored session.
Deadline for submitting proposals: 29 August 2015
Conference dates: 15-16 September
JSFoo will be held at the MLR Convention Centre, J P Nagar.
For more information about speaking proposals, tickets and sponsorships, contact email@example.com or call +91-7676332020.
Performance Engineering with React
You know how awesome React is, but do you know React has still kept some room for you to have a chance at increasing its performance even more? What is the average number of times your React components render unnecessarily on a single set state - 3, 4, 5? Or have you even checked that yet? We’ll see how we can optimise your components so that we minimise or eliminate unnecessary renders, virtual DOM diffing, DOM manipulation, etc., which can give you significant performance gains in large applications.
The audience needs to be familiar with the basics of React, to the least.
In this session we’ll take a more in-depth approach to understanding how ‘shouldComponentUpdate’ method of a React component works. This will enable us to realise it’s importance and then we can look at the various ways we can make the best of it to optimise React’s performance.
One of the approaches will cover using Immutable JS towards this end. We’ll also see what are the ‘gotchas’ to check for in implementing ‘shouldComponentUpdate’. Other approaches caution against using Function.bind() and literal arrays/objects, while also encouraging to break up your components effectively in order to optimise performance.
On the go, we’ll also see how to measure performance of your components using React’s performance tools, including one case study.
I’m a frontend developer with extensive experience in building complex web apps from scratch involving several key architectural decisions, and also leading UI teams. I’ve been using React for about 2 years now. I also have given beginner to advanced level trainings in React to my teams.