From the very, very useful Top Ten One-Liners from CommandLineFu Explained:

 ssh remote-machine 'cat >> .ssh/authorized_keys' < .ssh/id_rsa.pub

More comprehensive syntax highlighting for Snow Leopard’s QuickLook: qlcolorcode

When XHTML was all the rage years ago, it was common knowledge that an XML prolog declared before the doctype will trigger quirks mode in IE6. That has been fixed in IE7.

However, I found out that actually anything at all, except for white spaces and the XML prolog, will trigger quirks mode in IE6, 7 and 8 for doctypes that should otherwise trigger standards mode.

So if someone decides to add <!-- $Id$ --> to the first line in the HTML file, it will trigger quirks mode in IE. Now you know too.

So Mosaic‘s source code has just been released on GitHub, and a sharp eye at Reddit has already spotted this gem (keep in mind that IE is originally derived from Mosaic).

Assuming that IE was actually derived from this code base, may I present the reason we had to work around PNG24 for almost a decade:

/* its #if'ed out for now cause I don't have anything to
   test it with */

For example, id, class and attribute names should be in lowercase-with-dashes in HTML/CSS; JavaScript names should be in camelCase (better defined here); and anything in URLs (including file names) should be in lowercase not only because of conventions, but for cross-platform compatibility as well.

Please, avoid crazy shit like ab_someName and keep things consistent!

F.lux adjusts the color temperature of your screen to match your lighting and time of the day.

Measuring Javascript Parse and Load

While studies like this are fascinating to observe and to learn from, be very careful — unless you’re doing something like distributing JS libraries, these optimizations probably do not apply to you.

Keep in mind that the parse-and-load test runs 1000 iterations; in the first table, the actual average parse time is really only 0.125ms at worst and 0.003ms at best. Compare that to the average HTTP request — you might see sub-30ms responses just for a HTTP 304 on a good day, but 1000ms+ responses are not unheard of on unprimed caches (even more with DNS lookups). To put this into perspective, a snappy HTTP request at 30ms is more than 200 times slower than the slowest parse time of 0.125ms.

In other words, the net improvement you might gain from such parse-and-load optimizations is insignificant compared to the improvement from removing just one HTTP request.

So before you go adding more lines of code to accomplish yet another new trick, profile your code to see where the actual bottlenecks are. Otherwise, this smells like a lot like premature optimization.

Update: I’ve wrongly interpreted the results table and Carlos has corrected me. This means that the cost of script parsing and loading is significant, and optimizing this should help reduce CPU load which is hard to benchmark in real world conditions but could certainly be perceptible to users.

Note to self — Apache (stock on Leopard, which runs as _www) cannot read the preset directories in my home directory (like Desktop, Documents, Downloads, Library etc) because these directories only allow owner access by default (drwx------).

So that is why PHP won’t include files on my desktop. D’oh.