I spoke at Verchaska

Last week I spoke at Verchaska about performance optimization in Javascript and how to implement cross browser solutions. It was a nice experience knowing about early stage problems which most of the front end developers face. Most of the content from the talk covered Javascript from basics to advanced. Also, I spoke about CSS, how to implement cross browser solutions and some new cool features in ECMA5, HTML5 & CSS3.

Some of the things which I generally find common across all the novice front end engineers is that, in essence to meet sharp deadlines and for ease of use they all tend to use libraries and frameworks. As a result, they miss the basic beauty of the language. Assume it like this. Libraries are a dashboard to control and use the language who sits between you and the main language engine. You can perform all the actions and functions which are available on the dashboard but the problem arises when it comes to perform some action which is not available on the dashboard and you never bothered to look into actual engine to implement the action yourself. The real path of learning should be, first you understand the language and it’s insights, then you can jump into a library/framework which helps you rapid development your stuff.

It was really fun to explain floating concepts, handling closure memory leaks and Javascript identifier resolution from scope chains. How with & catch effect the performance of identifier lookups badly and why you should avoid eval. Evals are generally vulnerable to security problems and also, it doesn’t let the browser take the advantage of compile time optimization. People were totally delighted after knowing about such deep concepts and asked lots of questions.

Very few were aware that instead of making lot of DOM getter methods and filtering the nodes by writing long complex code just because you want nodes matching some particular selector rule, now you can use the new DOM selector api <element>.querySelector or <element>.querySelectorAll to avoid unnecessary filtering of nodes. Also, I explained them why you shouldn’t do DOM manipulations blindly. Reflow and repaints are costly and can significantly impact your web application performance if not taken care of. Use of timers can help your browser restart run away time and restart it’s stack call trace to avoid browser crash.

It was really fun talking to developers there and talking about some of their common code problems. And, I also learnt a lot while explaining the stuff to them. I really thank Verchaska for inviting me :-)

One thought on “I spoke at Verchaska

Leave a Reply

Your email address will not be published. Required fields are marked *


You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>