Submitted by Jaideep Singh (@jaideepsingh) on Friday, 9 August 2013
As the browsers continue to evolve and become more powerful, the application architectures tend to move more towards the client than the server, enabling the browser to do most of the heavy lifting, while providing a seamless experience to the users. However, as the applications grow, so does their memory footprint.
We'll be taking a look at some of the real applications and analyzing them for memory leaks. Also, we'll find out the real reasons behind the leaks, fix them and profile the application to compare the results.
Jaideep has been speaking at different forums about the front-end practices and workflows and believes that jumping to any frameworks without an understanding of the core generally leads to code which is less optimum and harder to debug.