Linux Computers: 249 of 1023 |
Error in operator: add beer
|
|
|
Linux Computers: 250 of 1023 |
Established technology tends to persist in the face of new technology.
-- G. Blaauw, one of the designers of System 360
|
|
|
Linux Computers: 251 of 1023 |
Eudaemonic research proceeded with the casual mania peculiar to this part of
the world. Nude sunbathing on the back deck was combined with phone calls to
Advanced Kinetics in Costa Mesa, American Laser Systems in Goleta, Automation
Industries in Danbury, Connecticut, Arenberg Ultrasonics in Jamaica Plain,
Massachusetts, and Hewlett Packard in Sunnyvale, California, where Norman
Packard's cousin, David, presided as chairman of the board. The trick was to
make these calls at noon, in the hope that out-to-lunch executives would return
them at their own expense. Eudaemonic Enterprises, for all they knew, might be
a fast-growing computer company branching out of the Silicon Valley. Sniffing
the possibility of high-volume sales, these executives little suspected that
they were talking on the other end of the line to a naked physicist crazed
over roulette.
-- Thomas Bass, "The Eudaemonic Pie"
|
|
|
Linux Computers: 252 of 1023 |
<<<<< EVACUATION ROUTE <<<<<
|
|
|
Linux Computers: 253 of 1023 |
Even bytes get lonely for a little bit.
|
|
|
Linux Computers: 254 of 1023 |
Ever wondered about the origins of the term "bugs" as applied to computer
technology? U.S. Navy Capt. Grace Murray Hopper has firsthand explanation.
The 74-year-old captain, who is still on active duty, was a pioneer in
computer technology during World War II. At the C.W. Post Center of Long
Island University, Hopper told a group of Long Island public school adminis-
trators that the first computer "bug" was a real bug--a moth. At Harvard
one August night in 1945, Hopper and her associates were working on the
"granddaddy" of modern computers, the Mark I. "Things were going badly;
there was something wrong in one of the circuits of the long glass-enclosed
computer," she said. "Finally, someone located the trouble spot and, using
ordinary tweezers, removed the problem, a two-inch moth. From then on, when
anything went wrong with a computer, we said it had bugs in it." Hopper
said that when the veracity of her story was questioned recently, "I referred
them to my 1945 log book, now in the collection of the Naval Surface Weapons
Center, and they found the remains of that moth taped to the page in
question."
[actually, the term "bug" had even earlier usage in
regard to problems with radio hardware. Ed.]
|
|
|
Linux Computers: 255 of 1023 |
"Every group has a couple of experts. And every group has at least one
idiot. Thus are balance and harmony (and discord) maintained. It's
sometimes hard to remember this in the bulk of the flamewars that all
of the hassle and pain is generally caused by one or two highly-motivated,
caustic twits."
-- Chuq Von Rospach, about Usenet
|
|
|
Linux Computers: 256 of 1023 |
Every program has at least one bug and can be shortened by at least one
instruction -- from which, by induction, one can deduce that every
program can be reduced to one instruction which doesn't work.
|
|
|
Linux Computers: 257 of 1023 |
Every program is a part of some other program, and rarely fits.
|
|
|
Linux Computers: 258 of 1023 |
Every Solidarity center had piles and piles of paper ... everyone was
eating paper and a policeman was at the door. Now all you have to do is
bend a disk.
-- A member of the outlawed Polish trade union, Solidarity,
commenting on the benefits of using computers in support
of their movement.
|
|