Newsgroup: it.hobby.umorismo
Titolo: I 10 bug piu' importanti della storia

Se vi interessa, date un'occhiata qui.
http://www.cnet.com/Content/Features/Dlife/Bugs/ss05.html
-- 
Andrea The Troll Meneghini
I due piu' comuni elementi nell'universo sono l'idrogeno e la
stupidita'.


http://www.cnet.com/Content/Features/Dlife/Bugs/ss05.html
E dai.... copiali, incollali e spediscili su ihu invece, che solo per aprire 
Netscape 4.0 mi ci vogliono 10-15 minuti....
Ciao,
Peppe

OK Peppe, l'hai voluto tu:
Here is our highly subjective list of the most dangerous, ornery,
news-making, expensive, and scandalous bugs of all time. There have been
so many that paring the list down to ten was hard, but these ten are
truly world-class bugs. Count down with us through the history of
computer bugs. 
1) The millennium bug: 2000 
For a long time, programmers have saved memory space by leaving only two
numeric fields for the year instead of four: 87 instead of 1987, for
example. When clocks strike midnight on January 1, 2000, this
programming shorthand will make millions of computers worldwide think
it's 1900, if their software isn't fixed before then. The so-called year
2000 (Y2K) bug has given birth to a cottage industry of consultants and
programming tools dedicated to making sure the modern world doesn't come
to a screeching halt on the first day of the next century. Some say that
the bug will cause airplanes to fall from the sky, ATMs to shut down,
and Social Security checks to bounce. At the very least, the bug is a
huge and expensive logistical problem, although most vital organizations
now say they will have fixed the critical portions of their systems in
time.
2) Deregulation of California utilities has to wait: 1998 
Two new electrical power agencies charged with deregulating the
California power industry have postponed their plans by at least three
months. The delay will let them debug the software that runs the new
power grid. Consumers and businesses were supposed to be able to choose
from some 200 power suppliers as of January 1, 1998, but time ran out
for properly testing the communications system that links the two new
agencies with the power companies. The project was postponed after a
seven-day simulation of the new system revealed serious problems. The
delay may cost as much as $90 million--much of which may eventually be
footed by ratepayers, and which may cause some of the new power
suppliers to go into debt or out of business before they even start. 
3) Java opens security holes; browsers simply crash: 1996 to 1997 
All right, this is not a single bug but a veritable bug collection. We
include this entry because the sheer quantity of press coverage about
bugs in Sun's Java and the two major browsers has had a profound affect
on how the average consumer perceives the Internet. The conglomeration
of headlines probably set back the e-commerce industry by five years. 
Java's problems surfaced in 1996, when research at the University of
Washington and Princeton began to uncover a series of security holes in
Java that could, theoretically, allow hackers to download personal
information from someone's home PC. To date, no one has reported a real
case of a hacker exploiting the flaw, but knowing that the possibility
existed prompted several companies to instruct employees to disable Java
in their browsers. 
Meanwhile, Netscape and Microsoft began battling in earnest in the
much-publicized browser wars. That competition inspired both companies
to accelerate the schedules for their 4.0 releases, and the result has
been a swarm of bugs, ranging from JavaScript flaws in Netscape's
Communicator to a reboot bug in Microsoft's Internet Explorer.
Communicator is now in Version 4.04 for Windows 95 and Windows NT, six
months after its first release. Internet Explorer 4.01, the first of
presumably many bug-fix versions, arrived in December, two months after
the initial release of IE 4.0.
4) New Denver airport misses its opening: 1995 
The Denver International Airport was intended to be a state-of-the-art
airport, with a complex, computerized baggage-handling system and 5,300
miles of fiber-optic cabling. Unfortunately, bugs in the baggage system
caused suitcases to be chewed up and drove automated baggage carts into
walls. The airport eventually opened 16 months late, $3.2 billion over
budget, and with a mainly manual baggage system. 
5) Intuit's MacInTax leaks financial secrets: 1995 
Intuit's tax software for Windows and Macintosh has suffered a series of
bugs, including several that prompted the company to pledge to pay any
resulting penalties and interest. The scariest bug was discovered in
March 1995: the code included in a MacInTax debug file allowed Unix
users to log in to Intuit's master computer, where all MacInTax returns
were stored. From there, the user could modify or delete returns. Intuit
later ended up winning BugNet's annual bug-fix award in 1996 by
responding to bugs faster than any other major vendor. 
6) Pentium chip fails math test: 1994 
The concept of bugs entered the mainstream when Professor Thomas Nicely
at Lynchburg College in Virginia discovered that the Pentium chip gave
incorrect answers to certain complex equations. In fact, the bug
occurred rarely and affected only a tiny percentage of Intel's
customers. The real problem was the nonchalant way Intel reacted.
"Because we had been marketing the Pentium brand heavily, there was a
bigger brand awareness," says Richard Dracott, Intel director of
marketing. "We didn't realize how many people would know about it, and
some people were outraged when we said it was no big deal." Intel
eventually offered to replace the affected chips, which Dracott says
cost the company $450 million. To prove that it had learned from its
mistake, Intel then started publishing a list of known "errata," or
bugs, for all of its chips. 
7) Patriot missile misses: 1991 
The U.S. Patriot missile's battery successfully headed off many Iraqi
Scuds during the Gulf War. But the system also failed to track several
incoming Scud missiles, including one that killed 28 U.S. soldiers in a
barracks in Dhahran, Saudi Arabia. The problem stemmed from a software
error that put the tracking system off by 0.34 of a second. As Ivars
Peterson states in Fatal Defect, the system was originally supposed to
be operated for only 14 hours at a time. In the Dhahran attack, the
missile battery had been on for 100 hours. This meant that the errors in
the system's clock accumulated to the point that the tracking system no
longer functioned. The military had in fact already found the problem
but hadn't sent the fix in time to prevent the barracks explosion. 
8) AT&T long distance service fails: 1990 
Switching errors in AT&T's call-handling computers caused the company's
long-distance network to go down for nine hours, the worst of several
telephone outages in the history of the system. The meltdown affected
thousands of services and was eventually traced to a single faulty line
of code.
2) Radiation machine kills four: 1985 to 1987 
Faulty software in a Therac-25 radiation-treatment machine made by
Atomic Energy of Canada Limited (AECL) resulted in several cancer
patients receiving lethal overdoses of radiation. Four patients died.
When their families sued, all the cases were settled out of court. A
later investigation by independent scientists Nancy Leveson and Clark
Turner found that accidents occurred even after AECL thought it had
fixed particular bugs. "A lesson to be learned from the Therac-25 story
is that focusing on particular software bugs is not the way to make a
safe system," they wrote in their report. "The basic mistakes here
involved poor software-engineering practices and building a machine that
relies on the software for safe operation." 
10) Mariner 1 Venus probe loses its way: 1962 
A probe launched from Cape Canaveral was set to go to Venus. After
takeoff, the unmanned rocket carrying the probe went off course, and
NASA had to blow up the rocket to avoid endangering lives on earth. NASA
later attributed the error to a faulty line of Fortran code. The report
stated, "Somehow a hyphen had been dropped from the guidance program
loaded aboard the computer, allowing the flawed signals to command the
rocket to veer left and nose down...Suffice it to say, the first U.S.
attempt at interplanetary flight failed for want of a hyphen." The
vehicle cost more than $80 million, prompting Arthur C. Clarke to refer
to the mission as "the most expensive hyphen in history." 


Visto che ce sei , vacce de traduzione in italiano.
Ciao
Karl Heinz Makka
Forza Lazio
Ma...@Dada.it
Numero ICQ 5993026

...

La tua pigrizia supera ogni limite, non riesco a capire il motivi perchè usi
ancora un winWN o simile, per la posta che usi mail di unix?
Addios
Sto cazzo Addios ve piacerebbe, oggi flood il ng :PPPPP

Numero ICQ 5993026
Sempre PEggio
IRCLuther

ancora un winWN o simile, per la posta che usi mail di unix?
Il mio discorso era anche collettivo... Cioe', se Andrea pija il messaggio e lo 
incolla (come ha peraltro gia' fatto), risparmia l'avvio di un browser WWW non 
solo a me, ma anche agli altri 373 frequentatori di IHU, con un aumento minore 
dell'entropia dell'universo, ed un migliore ordine delle tue pecore...
Per la posta all'inizio (tre-quattro anni fa) usavo davvero mail di Unix, poi 
sono passato a Pine, ed ormai faccio anch'io parte del volgo, ed uso Eudora...
Poi scusa, non siete proprio voi programmatori che vi fate i fighi ed arrivate 
a dire che vi e' il migliore text-editor che esista (parola di... aspetta... 
chi era... Trev ?), ma mi faccia il piacere.... Scommetto che adesso mi vieni a 
dire che il suo pregio migliore e' il fatto che e' molto "user-friendly" ed ha 
una interfaccia molto intuitiva !!!! :-))))
Ciao,
Peppe

IRCLuther
....ICQ forever :-))
Snafuz!, Razzo
CoPresidente della Smerding sps
http://idea.logicom.it/elio
 (e le Storie Tese)

single faulty line of code.
E ve lo immaginate il programmatore che dice "Ops, sorry..."
Ciao, Pipol!
Piero

 Ciao
Haem... 
Nel mezzo del cammin di nostra vita
mi ritrovai per una selva oscura
che la diritta via era smarrita...
continuo o vi basta?


E ve lo immaginate il programmatore che dice "Ops, sorry..."
E' stata la prima cosa che mi e' venuta in mente quando ho
letto questo messaggio....
"Chissa' cosa gli avranno fatto a quel poveraccio...".
Ciao,
Peppe

 continuo o vi basta?
basta e avanza direi....
della serie : "eifusiccomeimmobile"
machettepuozz
ariaccentamoselo
	-p-

       -p-
... causa della tastiera americana. Ndo sta sto cazzo di accento,
porcacc....
Come scusa non vale un'ostia, ma su ihu...


Peppe
Non se ne e' neanche accorto...
Si e' trovato a culo per terra sulla freeway senza neanche sapere come.
Ciao, pipol!
Piero

una interfaccia molto intuitiva !!!! :-))))
"User-friendly" e' un termine coniato apposta per chi non ha il tempo - o le
palle - per imparare seriamente un programma. 
P.S.: io _non_ sono un programmatore. Programmo per necessita' (e spero di
smettere quanto prima), ma usavo VI anche da studente in architettura, quando mi
curavo la mia homepage al politecnico.
A bientot,
			Marco.
	E-mail: 
dec...@been-there.com.EDU
 (remove .EDU) - UIN: 113102
				   ---o---
                  Appropinguare: avvicinarsi ad un ciccione.

palle - per imparare seriamente un programma. 
Sul fatto dello user friendly mi trovo d'accordo (vedi esempio utente Mac 
medio: ho comprato il Mac perche' e' facile da usare. Succede una cazzatina 
qualsiasi... Ma sai metterci le mani ? Nooo, e adesso come faccio ?!?!? Ok, 
chiamo il servizio clienti).
Per il fatto "palle" credo che torniamo al succo di quello che volevo dire... 
perche' i programmatori (o anche quelli che si sentono "ganzi" con i computer 
ed i linguaggi di programmazione) devono passare per vie estremamente astruse 
quando possono fare le cose molto piu' semplicemente ?!?!?
Un esempio di questo modo di pensare era quel messaggio postato da 
chissacchi/chissaquando (forse addirittura da te...) nel quale veniva
mostrata l'evoluzione del linguaggio di programmazione, passando da una 
sintassi semplice semplice ad un turbinio di simboli vari, per poi finire, con 
una retroevoluzione, al linguaggio dal quale si era partiti decine di anni 
prima. Si, lo so', l'esempio e' soltanto umoristico, ma qualcuno mi 
spiegherebbe il perche' di questa logica ? Forse davvero il mercato del 
software ha bisogno di questi piccoli espedienti alla Bill Gates ??? (Tipo.. il 
nostro prodotto e' il piu' cazzuto, il piu' figo, il piu' trendy, lo dovete 
comprare ed impararlo... dopo un paio di mesi... il nostro prodotto l'abbiamo 
modificato e leggermente complicato, adesso e' ancora piu' figo e trendy, ed e' 
diventato cazzutissimo, dovete assolutamente, come al solito, comprarlo...).
Mah...
Ciao,
Peppe 

quando possono fare le cose molto piu' semplicemente ?!?!?
...e spesso anche in molto piu' tempo.
Questione di punti di vista, comunque.
E' chiaro che anche la facilita' d'uso e' un punto a favore...
(magari facciamo che si passa in e-mail?)
Live long and prosper,
			Marco.
	E-mail: 
dec...@been-there.com.EDU
 (remove .EDU) - UIN: 113102
				   ---o---
             'Til the blood on your sword is the blood of a King!

(magari facciamo che si passa in e-mail?)
Ok, aspetta che cerco un po' Pine... :-)
Ciao,
Peppe 

Ok, aspetta che cerco un po' Pine... :-)
Apro, vero che lo sai cosa significa PINE?

Apro, vero che lo sai cosa significa PINE?
No, ma ci posso provare:
Primitive InterNet E-mailer ?
No, eh :-)
Ciao,
Peppe