Chop that code! Shake that tree! - A data insight towards understanding how nuances affect performance.
Submitted by Vivek (@avivek) on Monday, 15 October 2018
Section: Crisp talk Technical level: Intermediate Status: Under evaluation
Performance today has become a prime concern of apps as who doesn’t love a fast app. In today’s world which is full of distractions, there can be nothing more difficult than engaging the user with a slow app. If your app is slow, gradually user will get frustrated and leave it. As developers, we are aware mostly about major factors affecting an app’s performance, like too many scripts requests etc.. but there are other factors too which can help in further boosting the performance like code-splitting/tree-shaking. This talk aims towards sharing what these concepts are and with the help of case studies attempt to provide a data insight into what effect these factors can have on your app’s performance.
Brief outline of talk is as following:
- What is Code Splitting + brief on how its done
- What is Tree Shaking + brief on how its done
- Use case when code splitting and tree shaking not used
- Use case when code splitting and tree shaking used
- Comparison of Metrics
I have around 10 years of experience in software development and have been involved from the days when IE6 was the main browser. Currently working as a Principle Engineer in Pramati Technologies, my prime responsibilities are to take care of UI engagements implementing the best practices.