Hier. Der Brüller!
Help me, I don't SEE my music.
Coole sache, wieder mal eine RiesenSubEthaEditSession im Rahmen des Chaosradio 89! Nice. Nice appearances, joichi ito e.g., sadly he only lurked.
Now Down:hydra://feedback.berlin.ccc.de/chaosradio-89-feedback.txt
Ein statischer Snapshot vom endgültigen Dokument von 1:10

Now, for quite some time actually, called The Harrow Report.
A very nice regular about faster cpus, smaller disks and the likes. Always with an .mp3 version, ideal for your iPod.
be my anti-valentine
Valentinstagskarten nach meinem Geschmack. Leider einen Tag zu spät entdeckt.
[via moosmilbe]
... because it was intended to.
Listen to this Interview with Rasmus Lerdorf, the Father of PHP and be enlightened.
BTW: ITConversations real nice site.
What do we learn from this interview? The main goals of PHP were a easy learning curve, a easy way to solve simple problems. It all evolved through Mr. Lerdorf including more and more fucntionality to suit his users. He puts it this way: "I don't know how to stop it, there was never any intend to write a programming language [...] I have absolutely no idea how to write a programming language, I just kept adding the next logical step on the way".
In this way PHP is a great success for it's original target group: the HTML-Dreamweaver-Javascript-Designer. It's easy for them to do nice small stuff quickly. But if you want to do a proper web applications there are other solutions around that include an actual programming language, nice separation of data and layout, etc.
And the other downside is: PHP works in many ways different than actual programming languages, all intended to make it easier too use for the non-programmer. The problem is once a non-programmer gets into PHP he gets mislead in so many areas, so it will be very hard for him to do some real programming with an actual programming language that has a memory model, where endless loops run endless, where objects are pointers and not copied, where variables have a consistent and thought through scoping, where memory consumption does count, where lifecycles of objects are important and so on and on.
Now with snowballs!
Can you do better than this?

Lately I get the
The AIM service could not send the message: You have sent too much data too quickly. Please wait a little while before sending more.
all the time while chatting in iChat. This is really annoying. Really really annoying.
hdiutil convert BluetoothFWUpdater.dmg -format UDRW -o UpdaterRW.dmg open UpdaterRW.dmg
Now I understand, that's the way microsoft will continue to improve security. Instead of filling all their little security holes it will help their users do the job.
Try it yourself: Leak
So keep restarting your Safari from time to time to reduce memory usage. If you enable the debug menu, you see the memory usage in the "Page Load Test" window at the bottom.