You can see it here if you like, in 720p/H.264. I love the flurries of activity that pop up over time.
Props to Adam H for pointing me at this tool.
I know, three posts in one day is really too many; but this quote really tickles my funny bone while being a solid reminder why we need some humility and introspection powers.
While discussing the requirements or principles that might guide the development of a new mail application for Mac OS X; Brent manages to use “Let yaks prowl the grounds unshaven.” in a document. Excellent.
Follow along here for more.
makefor over 20 years; I’ve decided that something has to be better. Turns out, there is something better.
sconstogether for the last few months.
What a wonderful tool for building. There is a ton of information online, so I won’t add to the mélé with my opinions.
Check it out : scons.org.
Swiss Interface Syndrome:
John Gruber over at Daring Fireball pointed me at Sebastian de With’s outstanding gripe on interface design and rendering type on monitors in small pixel-sizes. This is not an easy problem to solve and you can really, truly, do a miserable job of it. I think that not enough people understand fonts in general and that UI design has suffered as a consequence. Yes, there are many other reasons why UI design has suffered, but type-abuse is a really easy low-hanging fruit to pick. *
Sebastiaan de With on the garish practice of mixing Helvetica with Lucida Grande in Mac UI design.
Let’s not get started on the ages-old Arial vs Helvetica fight.
(Via Daring Fireball.)
* In no way do I imply or intend to imply that I have not committed terrible sins against UI design sensibilities or font rendering guidelines myself, but I try to be aware of it. An excellent book on fonts and working with them is the somewhat timeless “Stop Stealing Sheep & Find Out How Type Works” by none other than Erik Spiekermann and, E.M. Ginger.
Lisa recently was playing around with some widgets in the SIMILE project and I have to admit that some of them are very useful for visualization of logfile and data systems, in particular, timeplot. I’ve installed a cool WordPress plugin that uses timeline (not timeplot) to draw a chronology of posts. It is quite a neat idea; you can find it on my timeline page and reproduced in miniature below:
Update: Of course, something in the CSS of the new theme is making this very hard to read, I’ll see if I can fix that at some point.
Something I’ve wanted to make work for a long, long time…
$ uname -a Darwin bose 8.8.0 Darwin Kernel Version 8.8.0: Fri Sep 8 17:18:57 PDT 2006; root:xnu-792.12.6.obj~1/RELEASE_PPC Power Macintosh powerpc $ ssh artni uname -a Linux artni 2.6.16-1.2096_FC5smp #1 SMP Wed Apr 19 05:31:55 EDT 2006 i686 i686 i386 GNU/Linux $ _
$ make i686-unknown-linux-gnu-gcc -static hello-kitty.c -o hello-kitty $ file hello-kitty hello-kitty: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.4.3, statically linked, not stripped $ _
$ scp hello-kitty artni:/tmp hello-kitty 100% 458KB 30.5KB/s $ _
$ ssh artni /tmp/hello-kitty Hello, kitty! $ _
Sweet! Woot! Special thanks to Dan Kegel for crosstool!
Now if only those Linux kids wouldn't make their filenames case-dependent.
(Foo.h and foo.h in the same directory, I mean, really!)
I discovered this by accident today while backing up a Subversion repository. I had written a small script to automate the generation of sane-sized incrementals and decided to given them a filename that was in the form:
Where lower and upper are whole, positive numbers. [ eg) 1:499, 500:999 ].
Since my script had a few errors while I was writing and testing it, I decided to carefully open the storage directory in the Finder and manually clean things up.
I was fairly surprised when I saw the directory (see image).
Apparently the colon character is not permitted in HFS filenames, however, nothing will stop you from making these files in the shell. I suspect that
Finder.app is using a backward compatibiliy mode to display these files in the GUI in case they are on volumes from OS 9 and earlier.
Looking at the output of
ls shows quite a different story, namely, the one I expected:
-rw-r--r-- 1 user wheel 0 Apr 4 18:47 1:2
-rw-r--r-- 1 user wheel 0 Apr 4 18:47 2:3
-rw-r--r-- 1 user wheel 0 Apr 4 18:47 3:4
-rw-r--r-- 1 user wheel 0 Apr 4 18:47 4:5
-rw-r--r-- 1 user wheel 0 Apr 4 18:47 5:6
-rw-r--r-- 1 user wheel 0 Apr 4 18:47 6:7
-rw-r--r-- 1 user wheel 0 Apr 4 18:47 7:8
-rw-r--r-- 1 user wheel 0 Apr 4 18:47 8:9
-rw-r--r-- 1 user wheel 0 Apr 4 18:59 9:10
It gets moderately more intesting: if you try to create a file (or folder) via the GUI; you will get a warning indicating that you cannot create a filename with punctuation (or try making the name shorter)
I’ve compiled a snapshot of how reSIProcate [Everybody's favorite SIP stack] code size is split between object files, text and data segments. You can see more about it on the reSIProcate wiki. There are three graphs, arranged in decreasing order of object size. Note that these are unoptimized objects on a 64-bit PPC 970 build. Comments and feedback are welcome.[Link ].
A new version of the reSIProcateSIP stack was released today. Kudos to the entire team for pulling this together! See the project’s Wiki for the release notes and additional contributor statistics about this release.