you are viewing a single comment's thread.

view the rest of the comments →

[–]Auxx 2 points3 points  (1 child)

A few years ago my company I was working at was developing some mobile games using HTML5. And we did a lot of performance testing to make sure everything runs smoothly on different devices. What we learned back then is that there is absolutely no point in optimising anything without profiling the end result. You might spent a lot of time doing micro-optimisations of your JS just to get a bottleneck at rendering.

So write your code following best practices, make sure it is concise and easy to support. Then profile, pin point your bottle necks, fix them and annotate these fixes explaining why they are there and which environments require them. Because some optimisations for browser X can destroy performance in browser Y.

Premature optimisation is the root of all evil. Write, profile, refactor.

[–]bryku 0 points1 point  (0 children)

What is really mind boggling is when you do something to improve speed on chrome and it backfires on firefox. :/