Evil Google Web Accelerator?

I hate it when inconsiderate actions in the form of an ugly hack by a big player have malicious impact on current best practices. Now we have to add checks for "
X-moz: prefetch
" in request headers if we want to keep the
Google Web Accelerator
from "googling-up" certain web apps with broad branching, performance intensive get-requests. I wonder how well Google is making use of caching to limit the effect this has on server load.

Apple's Tiger brings a
replacement for init, rc, the init.d and rc.d scripts, SystemStarter, inetd and xinetd, atd, crond, and watchdog
to the Unix world. As slahdotted by JQuick,
the new launchd
"[...] the launchd plist files (short for property lists) contain a set of key/value pairs describing what to run, and when to run it. Beyond this, launchd defines keys which tailor how the program is run, all of which are optional. These include specifying: user and group by either name or uig/gid; working directory, chroot directory, a dictionary of environment variables, CPU niceness, umask. Do you want to limit how much memory or stack it uses, prevent it from wiring system memory? Do you want limit the number of children it can spawn, or treat its IO requests as low priority as urgent? Keys are available for that."

The larger manufacturer of Swiss Army knives, Victorinox,
has taken over
its much smaller competitor and only rival, Wenger.

"The two official makers of Swiss Army knives, which will keep their
identities separate under the deal, have been struggling to make
headway since the September 2001 terrorist attacks in the United States. After 9-11, the companies lost between 15% and 20% of turnover as business at duty-free outlets slumped. Although airline passengers can buy the knives in duty free stores,
they are not allowed to take them on aircraft as hand luggage because
of security concerns."

"The problem with AJAX is that it doesn't address the fundamental difficulty in developing web applications--the unbridgable client-server divide. You still have to use a completely different set of languages and tools for writing the GUI on one hand, and the server components on the other, with no possibility of sharing code in between."

"A truly revolutionary web paradigm would allow developers to use the SAME language and object model in developing both the client- and the server-side. The server would retrieve an objects from the datastore, serialize it, and pass it off to the client for editing. The client would be able to modify these same objects (defined in the same class libraries) and pass it back to the server, which re-validates them and persists them back into the datastore."

Your email address:
The "Decentralize" Newsletter
Exchanging ideas for building a
decentralized fabric of society.
Making true democracy work on a larger
scale while decentralizing "everything",
benefiting from local diversity and
global synergies at the same time.
http://tinyletter.com/zumbrunn