The dynamic linking tax on fork()
Most people will tell you that dynamic linking is an unalloyed good, orat least that any effects on performance are small (for simple programsthat don't cascade to a huge set of shared libraries). This isn'tnecessarily so.
A long time ago, back when dynamic linking was new and people weresuspicious of it, I conducted some timings of how dynamic linkingaffected the speed of fork() . To my surprise, the impact wassignificant, and on the hardware of the day it was
Why dynamic linking
Originally, shared libraries and dynamic linking was sold as the way tomake (newly) bloated libraries tolerable: you'd only have one copy ofthe library on disk and in memory, no matter how many Motif applicationsyou had running. (Motif in specific and GUI libraries were really theoriginal poster boys for shared libraries.)
As R. Francis Smith notes in his comment on my previous entry , these reasons are not entirely relevant any more.Disk space is cheap, and (although I haven't
學術愛恨，歇斯底里肥皂
Closures versus classes for capturing state
Possibly like a lot of other people, I have a 'thread pool' Pythonmodule for doing decoupled asynchronous queries of things. The basic interface looks like this:
wp = WorkPool(HOWMANY)for w in what: wp.enqueue(wrap_up(w))wp.waitDone()res = wp.getanswers()
The important operation is It's always nice when people's software saves me from having to wonderif they're up to no good by handing out obvious signs of it. Take, forexample, the spate of people whose web crawling software advertisesitself by having the User-Agent string of: Evidently no one told them not to stutter. (There are a couple ofvariations in what they claim to Via a link from MiniMsft 's latest entry ,I wound up reading this item on hiring people. In it I hit an interviewer question I realized that Iprobably wouldn't pass: 6. I will ask you in an interview to describe a project you worked onor effort you made that failed - partially, completely, and miserablyare all OK for response fodder. If you've worked for a substantiallength of time in IT, you've been part of at least one of theseturkeys. The traditional way to configure Apache is to take the The big problem with this approach is that .enqueue(
Making things simple for busy webmasters
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Thinking about project failures
消失的中介
——魯迅，〈答有桓先生〉。
（真係夠膽死日日update喎我）
正所謂一雞死一雞鳴，上呀野君！
打小人
昨日驚蟄，澳門有一群婦女在街上打小人。
這是我近年來最想參與的一項運動，如果驚蟄的傳統打小人可以延伸到讓我們把身邊的小人都揪出來“打一鑊”，那就真的大快人心，促進特區和諧，更能減低這個城市無日無之的小人
A modular approach to Apache configuration
httpd.conf file shipped with your distribution and start changing it to your localneeds; for example, so that the DocumentRoot and ServerName are right.This is simple and attractive, until you have to upgrade. httpd.conf has two sortsof settings; it mixes together settings that you want to customize,like DocumentRoot, with Apache internal things, like AddLanguage andAddCharset. With them all jumbled together, upgrading can be Menu