BRAINFART

Nowadays there are many different JavaScript Frameworks around the web. Many developers use them to speed up their work and to make the result cross-browser compatible. Every web developer (or even someone creating a website for personal needs) faces the challenge to choose the best framework for their specific needs. In this article we’ll try to compare the most famous JavaScript Frameworks: Prototype, jQuery and MooTools...

When you think of interactive multimedia on the Web, you probably think of Flash. Flash offers the webmaster a single platform to create content that will be seen by the majority of Web site users, and that everyone who sees Flash will be able to interact with it in exactly the same way. However, there are some arguments against Flash, and many webmasters choose to use Flash in only limited pockets within their site. What many people don’t realize is that you can create similar experiences in JavaScript, and by doing so you can avoid many of the problems inherent in Flash...

It’s a good practice to use many small JavaScript and CSS files instead of one large JavaScript/CSS file for better code maintainability, but bad in terms of website performance. Although you should write your JavaScript code in small files and break large CSS files into small chunks, when a browser requests those JavaScript and CSS files, it makes one HTTP request per file. Every HTTP request results in a network roundtrip from your browser to the server and the delay in reaching the server and coming back to the browser is called latency. So, if you have four JavaScripts and three CSS files loaded by a page, you are wasting time in seven network roundtrips. Within the USA, latency is average 70ms. So, you waste 7×70 = 490ms, about half a second of delay. Outside USA, average latency is around 200ms. So, that means 1400ms of waiting. The browser cannot show the page properly until CSS and JavaScripts are fully loaded. So, the more latency you have, the slower the page loads...