Steve Souders recently invited me to participate in his Web Exponents speaker series at Google. Periodically, people come in to give hour-long tech talks about
It was just a couple of years ago that Steve Souders introduced the concept of blocking vs. non-blocking into the common lexicon of web developers around the
Excerpt from Chapter 5 in my book Usability Engineering, from 1993
The basic advice regarding response times has been about the same for thirty years [Miller 1968; Card et al. 1991]:
0.1 second is about the limit for having the user feel that the system is reacting instantaneously, meaning that no special feedback is necessary except to display the result.1.0 second is about the limit for the user's flow of thought to stay uninterrupted, even though the user will notice the delay. Normally, no special feedback is necessary during delays of more than 0.1 but less than 1.0 second, but the user does lose the feeling of operating directly on the data.10 seconds is about the limit for keeping the user's attention focused on the dialogue. For longer delays, users will want to perform other tasks while waiting for the computer to finish, so they should be given feedback indicating when the computer expects to be done. Feedback during the delay is especially important if the response time is likely to be highly variable, since users will then not know what to expect.
Colleges spend years preaching the gospel of object-oriented programming to undergrads. Define classes. Use interfaces. Remember your design patterns. They tell
Though most object-oriented architecture begins with the definition of classes, this should not be your first step when defining a JavaScript solution.
Almost all tasks can be accomplished by singleton objects performing specific functions. Reference types are rarely needed and inheritance is needed even less often.
Good object-oriented design in JavaScript often means avoiding reference types and inheritance to avoid the performance penalty that accompanies them.
If your application’s performance is important (and if it’s not, then you probably have the wrong priorities), you owe it to yourself to design intelligently for the medium in which you’re working.
JavaScript is a different type of object-oriented language and thus requires different architectural approaches to solving problems.
Not too long ago, I wrote a post entitled, Thoughts on script loaders, in which I discussed my thoughts on the continuing introduction of script loaders such
Approximate timing for various operations on a typical PC:
execute typical instruction1/1,000,000,000 sec = 1 nanosecfetch from L1 cache memory0.5 nanosecbranch misprediction5 nanosecfetch from L2 cache memory7 nanosecMutex lock/unlock25 nanosecfetch from main memory100 nanosecsend 2K bytes over 1Gbps network20,000 nanosecread 1MB sequentially from memory250,000 nanosecfetch from new disk location (seek)8,000,000 nanosecread 1MB sequentially from disk20,000,000 nanosecsend packet US to Europe and back150 milliseconds = 150,000,000 nanosec
iPad : 77 fois plus d'émissions de GES lors de la fabrication GreenIT.fr L'Electric Power Research Institute (EPRI) a publié une étude sur la consommation électrique des derniers modèles d'iPad.
I was sitting in a talk given by Facebook's Jason Sobel at Velocity this year, when I was a bit surprised by an impassioned plea that he made at the tail end of
Cette initiative hollandaise vise à fabriquer une smartphone le plus équitable et respectueux possible de l’environnement à un prix raisonnable : 325 euros. Qu’en pensez-vous ? Lire la suite
Those who have attended my talks on JavaScript performance are familiar with my propensity for using setTimeout() to break up long scripts into smaller chunks.
One of the most basic tests developers perform in JavaScript is whether or not a particular property exists on an object. Since feature detection is the
tl;dr version: the web is waaaay too slow, and every time you write something off as just taking a couple of milliseconds, you're part of the problem. Good
Comparer la différence de rapidité entre différents sélecteurs JQuery est une étape importante dans la conception de script. Faites les bons choix grâce à JQuery expressions BenchMarkR
To get content containing either thought or leadership enter:
To get content containing both thought and leadership enter:
To get content containing the expression thought leadership enter:
You can enter several keywords and you can refine them whenever you want. Our suggestion engine uses more signals but entering a few keywords here will rapidly give you great content to curate.