Consider two notebooks. A MacBook and a PC.
If you are working on a presentation and for some reason must get up and do something else you’ll be doing the following: save the document, close the notebook, do what you want to do, open the notebook and hope it haven’t crashed.
If you however are working on a Mac you’ll be just closing and opening it.
Once again the time has come to take my clothes off. As in last year I’ll be participating once again in the CSS Naked Day initiative.
CSS stands for Cascading Style Sheets. According to Wikipedia CSS is “used to describe the presentation (that is, the look and formatting) of a document written in a markup language“. Simply put CSS is the shackle in the web technologies stack that makes web sites and applications look as what they look like.
The purpose of the initiative is to move web developers to use the right tool for the right job, ergo to use CSS for styling and (X)HTML (the markup language in the web) for describing data. So, yes, it’s a web developer’s initiative aimed at web developers. Drop me a line or a tweet if you want more detailed information about this matter.
For some weird reason after my vacation my Reader wasn’t any more in English but in German. I’ve tried switching my settings to English and this helped. Only it didn’t switched the interface language of the application, only of the settings view. It felt really weird using Reader in German :).
Here is how I’ve solved the issue:
http://www.google.com from Google Gears trusted sites: Tools -> Google Gears SettingsTools -> Clear Private DataAnd it worked :). Reader’s interface is once again in English.
Representing the destructive option as big shinny button, representing the desired option, in most cases at least, as a smallish link.
Asking for a confirmation on critical and irreversible operations.
I’m a bit late, but rather later then never :). I just didn’t had even 10 Minutes spare time in the last few days.
Here is my response to Dustin’s brain teaser. I’m offering a solution without regular expressions. Though after reading the problem I first thought “Nice, I’ll use regular expressions.”. But then I realized that now I’m facing two problems :). I’m really not that good at regexps.
But I promise I’ll keep the teaser in mind and one day I’ll solve it with regular expressions.
var teaserNoRegExp = function() {
var input = ['a', 'b', 'c', 'c', 'd','e', 'e','e', 'e',
'e', 'f', 'e', 'f', 'e','f', 'a', 'a', 'a', 'f', 'f', 'f'];
var output = '';
// assume Array.prototype.forEach
var spanOpened = false;
input.forEach(function(el, index, input){
if (input[index-1] == el && input[index-2] == el && !spanOpened) {
output = output + '';
spanOpened = true;
}
output = output + ' ' + el;
if (input[index+1] != el && spanOpened) {
output = output + '';
spanOpened = false;
}
});
document.getElementById('result').value = output;
};
P.S. It actually took me a minute or two to write it down.
I’ll be participating in this year’s naked day on 9th of April.
Yeah, I’m a nudist, baby. I’ll be running the whole day with my clothes off and I’ll be exposing myself all over the place. I’m so excited I’ll do the long 48-hours-day striptease.
Cheers.
In addition to the first part of screenshots of the Slick Speed test suite I’ve been able to get my hands on a Konquerer 3.5.6 running on Kubuntu Feisty.
Default install. 383KB, 1000×1190.
Prototype and mootools throw an error on every single selector. dojo on Konquerer is comparable to dojo on Firefox on Linux and is the fastest one along with ext. However the winner this time is jQuery: it throws only one error, like cssQuery, but is twice as fast.
Note that the jQuery team released the new 1.1.3 version just a few days back and selector speed is improved by the amazing 800% (!!!). This is one hell of improvement. I haven’t made new tests on my own, be aware. I will be just giving a calculation of the improved time, next to the measured one.
So I’ve decided to make a simple error and time count, but excluding the double Firefox 2.x install. In parenthesis is given the result without Konquerer:
While making that count I’ve made one discovery: every library struggles with the same selectors on the different A-graded browsers. Another one interesting fact is that cssQuery offers the same browser support on all participants, even on IE5.5
There are no winners in this case study, because each library has its own uniqueness and greatness. Besides, all of them are comparably fast and offer a comparable amount of supported selectors. Now let’s go back to the real thing - coding on top of them and not comparing them!
A fresh install. No extensions. 396KB, 1000×1224.
A fresh install. No extensions. 400KB, 1000×1240.
A bunch of extensions: ~25. 399KB, 1000×1235
MultipleIE install. 156KB, 1000×679.
MultipleIE install. 530KB, 1000×1452.
MultipleIE install. 404KB, 1000×1221.
Default install. 384KB, 1000×1221.
Default install. 392KB, 1000×1261.
Default install. 399KB, 1000×1242.
Default install. 484KB, 1000×1132.
All libraries behave equally fast/slow on the different Firefox installations. Except jQuery and mootools on my default FF install. This could be caused by GMail Notifier, which is checking my mail every minute.
IE7 improves speed by factor 2. Frustrating is that IE5.5, IE6 and even IE7 return different results on the * selector compared to other browsers and compared between the libraries.
Opera 9.2 is slower than 9.1.
Safari is in beta and is a freshman among Windows browser, so results are “just for fun”.
Prototype, mootools and dojo are the winners. I am somehow disappointed by jQuery.
A fresh install. No extensions. 375KB, 1000×1190.
A bunch of extensions: ~25. 375KB, 1000×1190.
Default install. 325KB, 1000×1192.
Opera is the faster one on my Linux box, but it took an awful long time to load the official test page.
Both Firefox 2.x profiles, clean one and one with a bunch of extension, behave quite equally - there are no speed improvements by factor 3 like mootools on Windows.
I couldn’t find any trident or WebKit browsers for ubuntu, but if you know of any feel free to drop me a line and I will run test once again.
We have the same winners - prototype, mootools and dojo.
Overall: libraries are running faster under Windows.
Locally I’ve tested also MochiKit - it threw a lot of errors.
Download SlickSpeed on Windows & Linux (~4.8MB).
Update: Note, that the Konquerer screenshot is not included in the archive. Download it separately.