bill gates can choose
Bill Gates suddenly dies and finds himself face to face with God. God stood over Bill Gates and said, "Well Bill, I'm really confused on this one. It's a tough decision; I'm not sure whether to send you to Heaven or Hell. After all, you helped society enormously by putting a computer in almost every home in America, yet you also created that ghastly Windows '95 among other indiscretions. I believe I'll do something I've never done before; I'll let you decide where you want to go."
Bill pushed up his glasses, looked up at God and replied, "Could you briefly explain the difference between the two?" Looking slightly puzzled, God said, "Better yet, why don't I let you visit both places briefly, then you can make your decision. Which do you choose to see first, Heaven or Hell?"
Bill played with his pocket protector for a moment, then looked back at God and said, "I think I'll try Hell first." So, with a flash of lightning and a cloud of smoke, Bill Gates went to Hell.
When he materialized in Hell, Bill looked around. It was a beautiful and clean place, a bit warm, with sandy beaches and tall mountains, clear skies, pristine water, and beautiful women frolicking about. A smile came across Bill's face as he took in a deep breath of the clean air. "This is great," he thought, "if this is Hell, I can't wait to see heaven."
Within seconds of his thought, another flash of lightning and a cloud of smoke appeared, and Bill was off to Heaven. Heaven was a place high above the clouds, where angels were drifting about playing their harps and singing in a beautiful chorus. It was a very nice place, Bill thought, but not as enticing as Hell.
Bill looked up, cupped his hands around his mouth and yelled for God and Bill Gates was sent to Hell for eternity.
Time passed, and God decided to check on the late billionaire to see how he was progressing in Hell. When he got there, he found Bill Gates shackled to a wall in a dark cave amid bone thin men and tongues of fire, being burned and tortured by demons.
"So, how is everything going?" God asked.
Bill responded with a crackling voice filled with anguish and disappointment, "This is awful! It's nothing like the Hell I visited the first time!! I can't believe this is happening! What happened to the other place....with the beaches and the mountains and the beautiful women?
"That was the demo," replied God.
 |
|
|
|
|
 | ||||
Bill pushed up his glasses, looked up at God and replied, "Could you briefly explain the difference between the two?" Looking slightly puzzled, God said, "Better yet, why don't I let you visit both places briefly, then you can make your decision. Which do you choose to see first, Heaven or Hell?"
Bill played with his pocket protector for a moment, then looked back at God and said, "I think I'll try Hell first." So, with a flash of lightning and a cloud of smoke, Bill Gates went to Hell.
When he materialized in Hell, Bill looked around. It was a beautiful and clean place, a bit warm, with sandy beaches and tall mountains, clear skies, pristine water, and beautiful women frolicking about. A smile came across Bill's face as he took in a deep breath of the clean air. "This is great," he thought, "if this is Hell, I can't wait to see heaven."
Within seconds of his thought, another flash of lightning and a cloud of smoke appeared, and Bill was off to Heaven. Heaven was a place high above the clouds, where angels were drifting about playing their harps and singing in a beautiful chorus. It was a very nice place, Bill thought, but not as enticing as Hell.
Bill looked up, cupped his hands around his mouth and yelled for God and Bill Gates was sent to Hell for eternity.
Time passed, and God decided to check on the late billionaire to see how he was progressing in Hell. When he got there, he found Bill Gates shackled to a wall in a dark cave amid bone thin men and tongues of fire, being burned and tortured by demons.
"So, how is everything going?" God asked.
Bill responded with a crackling voice filled with anguish and disappointment, "This is awful! It's nothing like the Hell I visited the first time!! I can't believe this is happening! What happened to the other place....with the beaches and the mountains and the beautiful women?
"That was the demo," replied God.
microsoft buys church
MICROSOFT Bids to Acquire Catholic Church
VATICAN CITY (AP) -- In a joint press conference in St. Peter's Square this morning, MICROSOFT Corp. and the Vatican announced that the Redmond software giant will acquire the Roman Catholic Church in exchange for an unspecified number of shares of MICROSOFT common stock. If the deal goes through, it will be the first time a computer software company has acquired a major world religion.
With the acquisition, Pope John Paul II will become the senior vice-president of the combined company's new Religious Software Division, while MICROSOFT senior vice-presidents Michael Maples and Steven Ballmer will be invested in the College of Cardinals, said MICROSOFT Chairman Bill Gates.
"We expect a lot of growth in the religious market in the next five to ten years," said Gates. "The combined resources of MICROSOFT and the Catholic Church will allow us to make religion easier and more fun for a broader range of people."
Through the MICROSOFT Network, the company's new on-line service, "we will make the sacraments available on-line for the first time" and revive the popular pre-Counter-Reformation practice of selling indulgences, said Gates. "You can get Communion, confess your sins, receive absolution -- even reduce your time in Purgatory -- all without leaving your home."
A new software application, MICROSOFT Church, will include a macro language which you can program to download heavenly graces automatically while you are away from your computer.
An estimated 17,000 people attended the announcement in St Peter's Square, watching on a 60-foot screen as comedian Don Novello -- in character as Father Guido Sarducci -- hosted the event, which was broadcast by satellite to 700 sites worldwide.
Pope John Paul II said little during the announcement. When Novello chided Gates, "Now I guess you get to wear one of these pointy hats," the crowd roared, but the pontiff's smile seemed strained.
The deal grants MICROSOFT exclusive electronic rights to the Bible and the Vatican's prized art collection, which includes works by such masters as Michelangelo and Da Vinci. But critics say MICROSOFT will face stiff challenges if it attempts to limit competitors' access to these key intellectual properties.
"The Jewish people invented the look and feel of the holy scriptures," said Rabbi David Gottschalk of Philadelphia. "You take the parting of the Red Sea -- we had that thousands of years before the Catholics came on the scene."
But others argue that the Catholic and Jewish faiths both draw on a common Abrahamic heritage. "The Catholic Church has just been more successful in marketing it to a larger audience," notes Notre Dame theologian Father Kenneth Madigan. Over the last 2,000 years, the Catholic Church's market share has increased dramatically, while Judaism, which was the first to offer many of the concepts now touted by Christianity, lags behind.
Historically, the Church has a reputation as an aggressive competitor, leading crusades to pressure people to upgrade to Catholicism, and entering into exclusive licensing arrangements in various kingdoms whereby all subjects were instilled with Catholicism, whether or not they planned to use it. Today Christianity is available from several denominations, but the Catholic version is still the most widely used. The Church's mission is to reach "the four corners of the earth," echoing MICROSOFT's vision of "a computer on every desktop and in every home".
Gates described MICROSOFT's long-term strategy to develop a scalable religious architecture that will support all religions through emulation. A single core religion will be offered with a choice of interfaces according to the religion desired -- "One religion, a couple of different implementations," said Gates.
The MICROSOFT move could spark a wave of mergers and acquisitions, according to Herb Peters, a spokesman for the U.S. Southern Baptist Conference, as other churches scramble to strengthen their position in the increasingly competitive religious market.
|
|
|
|
|
| ||||
VATICAN CITY (AP) -- In a joint press conference in St. Peter's Square this morning, MICROSOFT Corp. and the Vatican announced that the Redmond software giant will acquire the Roman Catholic Church in exchange for an unspecified number of shares of MICROSOFT common stock. If the deal goes through, it will be the first time a computer software company has acquired a major world religion.
With the acquisition, Pope John Paul II will become the senior vice-president of the combined company's new Religious Software Division, while MICROSOFT senior vice-presidents Michael Maples and Steven Ballmer will be invested in the College of Cardinals, said MICROSOFT Chairman Bill Gates.
"We expect a lot of growth in the religious market in the next five to ten years," said Gates. "The combined resources of MICROSOFT and the Catholic Church will allow us to make religion easier and more fun for a broader range of people."
Through the MICROSOFT Network, the company's new on-line service, "we will make the sacraments available on-line for the first time" and revive the popular pre-Counter-Reformation practice of selling indulgences, said Gates. "You can get Communion, confess your sins, receive absolution -- even reduce your time in Purgatory -- all without leaving your home."
A new software application, MICROSOFT Church, will include a macro language which you can program to download heavenly graces automatically while you are away from your computer.
An estimated 17,000 people attended the announcement in St Peter's Square, watching on a 60-foot screen as comedian Don Novello -- in character as Father Guido Sarducci -- hosted the event, which was broadcast by satellite to 700 sites worldwide.
Pope John Paul II said little during the announcement. When Novello chided Gates, "Now I guess you get to wear one of these pointy hats," the crowd roared, but the pontiff's smile seemed strained.
The deal grants MICROSOFT exclusive electronic rights to the Bible and the Vatican's prized art collection, which includes works by such masters as Michelangelo and Da Vinci. But critics say MICROSOFT will face stiff challenges if it attempts to limit competitors' access to these key intellectual properties.
"The Jewish people invented the look and feel of the holy scriptures," said Rabbi David Gottschalk of Philadelphia. "You take the parting of the Red Sea -- we had that thousands of years before the Catholics came on the scene."
But others argue that the Catholic and Jewish faiths both draw on a common Abrahamic heritage. "The Catholic Church has just been more successful in marketing it to a larger audience," notes Notre Dame theologian Father Kenneth Madigan. Over the last 2,000 years, the Catholic Church's market share has increased dramatically, while Judaism, which was the first to offer many of the concepts now touted by Christianity, lags behind.
Historically, the Church has a reputation as an aggressive competitor, leading crusades to pressure people to upgrade to Catholicism, and entering into exclusive licensing arrangements in various kingdoms whereby all subjects were instilled with Catholicism, whether or not they planned to use it. Today Christianity is available from several denominations, but the Catholic version is still the most widely used. The Church's mission is to reach "the four corners of the earth," echoing MICROSOFT's vision of "a computer on every desktop and in every home".
Gates described MICROSOFT's long-term strategy to develop a scalable religious architecture that will support all religions through emulation. A single core religion will be offered with a choice of interfaces according to the religion desired -- "One religion, a couple of different implementations," said Gates.
The MICROSOFT move could spark a wave of mergers and acquisitions, according to Herb Peters, a spokesman for the U.S. Southern Baptist Conference, as other churches scramble to strengthen their position in the increasingly competitive religious market.
airplanes running an os
Here are some basic descriptions of what may happen if airplanes had different operating systems running them.
DOS: Everybody pushes it till it glides, then jumps on and lets it coast till it skids, then jumps off, pushes, jumps back on, etc.
DOS with QEMM: Same as DOS, but with more leg room for pushing.
Macintosh: All the flight attendants, captains and baggage handlers look the same, act the same and talk the same. Every time you ask a question, you are told you don't need to know, don't want to know and everything will be done for you without your knowing, so just shut up.
OS/2: To get on board, you have to have your ticket stamped 10 different times by standing in 10 different lines. Then you fill out a form asking how you want your seating arranged--with the look and feel of an ocean liner, a passenger train or a bus. If you get on board and off the ground, you will have a wonderful trip, except when the rudder and flaps freeze, in which case you have time to say your prayers before you crash.
Windows: Colorful airport terminal, friendly flight attendants, easy access to a plane, and an uneventful takeoff. Then, all in a sudden, boom! You blow up without any warning whatsoever.
NT: The terminal and flight attendants all look like those the Windows plane uses, but the process of checking in and going through security is a nightmare. Once aboard, those passengers with first class tickets can go anywhere they want and arrive in half the time, while the vast majority of passengers with coach tickets can't even get aboard.
Unix: Everyone brings one piece of the plane. Then they go on the runway and piece it together, all the while arguing about what kind of plane they're building.
CAIRO: The airplane is distributed among 47 different hangars in 13 airports scattered over 8 states, 4 Canadian provinces, and a remote mountain hideaway in Nicaragua. But you don't need to know where the airplane is or who it belongs to in order to fly it. Actually, you don't fly the airplane itself; you fly a simulation that behaves just like the real thing except that you don't go anywhere. But that's okay, because when the world is at your fingertips you never need to leave home.
|
|
|
|
|
| ||||
DOS: Everybody pushes it till it glides, then jumps on and lets it coast till it skids, then jumps off, pushes, jumps back on, etc.
DOS with QEMM: Same as DOS, but with more leg room for pushing.
Macintosh: All the flight attendants, captains and baggage handlers look the same, act the same and talk the same. Every time you ask a question, you are told you don't need to know, don't want to know and everything will be done for you without your knowing, so just shut up.
OS/2: To get on board, you have to have your ticket stamped 10 different times by standing in 10 different lines. Then you fill out a form asking how you want your seating arranged--with the look and feel of an ocean liner, a passenger train or a bus. If you get on board and off the ground, you will have a wonderful trip, except when the rudder and flaps freeze, in which case you have time to say your prayers before you crash.
Windows: Colorful airport terminal, friendly flight attendants, easy access to a plane, and an uneventful takeoff. Then, all in a sudden, boom! You blow up without any warning whatsoever.
NT: The terminal and flight attendants all look like those the Windows plane uses, but the process of checking in and going through security is a nightmare. Once aboard, those passengers with first class tickets can go anywhere they want and arrive in half the time, while the vast majority of passengers with coach tickets can't even get aboard.
Unix: Everyone brings one piece of the plane. Then they go on the runway and piece it together, all the while arguing about what kind of plane they're building.
CAIRO: The airplane is distributed among 47 different hangars in 13 airports scattered over 8 states, 4 Canadian provinces, and a remote mountain hideaway in Nicaragua. But you don't need to know where the airplane is or who it belongs to in order to fly it. Actually, you don't fly the airplane itself; you fly a simulation that behaves just like the real thing except that you don't go anywhere. But that's okay, because when the world is at your fingertips you never need to leave home.
real software engineers
Real software engineers eat quiche.
Real software engineers don't read dumps. They never generate them, and on the rare occasions that they come across them, they are vaguely amused.
Real software engineers don't comment their code. The identifiers are so mnemonic they don't have to.
Real software engineers don't write applications programs, they implement algorithms. If someone has an application that the algorithm might help with, that's nice. Don't ask them to write the user interface, though.
If it doesn't have recursive function calls, real software engineers don't program in it.
Real software engineers don't program in assembler. They become queasy at the very thought.
Real software engineers don't debug programs, they verify correctness. This process doesn't necessarily involve executing anything on a computer, except perhaps a Correctness Verification Aid package.
Real software engineers like C's structured constructs, but they are suspicious of it because they have heard that it lets you get "close to the machine."
Real software engineers play tennis. In general, they don't like any sport that involves getting hot and sweaty and gross when out of range of a shower. (Thus mountain climbing is Right Out.) They will occasionally wear their tennis togs to work, but only on very sunny days.
Real software engineers admire PASCAL for its discipline and Spartan purity, but they find it difficult to actually program in. They don't tell this to their friends, because they are afraid it means that they are somehow Unworthy.
Real software engineers work from 9 to 5, because that is the way the job is described in the formal spec. Working late would feel like using an undocumented external procedure.
Real software engineers write in languages that have not actually been implemented for any machine, and for which only the formal spec (in BNF) is available. This keeps them from having to take any machine dependencies into account. Machine dependencies make real software engineers very uneasy.
Real software engineers don't write in ADA, because the standards bodies have not quite decided on a formal spec yet.
Real software engineers like writing their own compilers, preferably in PROLOG (they also like writing them in unimplemented languages, but it turns out to be difficult to actually RUN these).
Real software engineers regret the existence of COBOL, FORTRAN and BASIC. PL/I is getting there, but it is not nearly disciplined enough; far too much built in function.
Real software engineers aren't too happy about the existence of users, either. Users always seem to have the wrong idea about what the implementation and verification of algorithms is all about.
Real software engineers don't like the idea of some inexplicable and greasy hardware several aisles away that may stop working at any moment. They have a great distrust of hardware people, and wish that systems could be virtual at ALL levels. They would like personal computers (you know no one's going to trip over something and kill your DFA in mid-transit), except that they need 8 megabytes to run their Correctness Verification Aid packages.
Real software engineers think better while playing WFF 'N' PROOF.
|
|
|
|
|
| ||||
Real software engineers don't read dumps. They never generate them, and on the rare occasions that they come across them, they are vaguely amused.
Real software engineers don't comment their code. The identifiers are so mnemonic they don't have to.
Real software engineers don't write applications programs, they implement algorithms. If someone has an application that the algorithm might help with, that's nice. Don't ask them to write the user interface, though.
If it doesn't have recursive function calls, real software engineers don't program in it.
Real software engineers don't program in assembler. They become queasy at the very thought.
Real software engineers don't debug programs, they verify correctness. This process doesn't necessarily involve executing anything on a computer, except perhaps a Correctness Verification Aid package.
Real software engineers like C's structured constructs, but they are suspicious of it because they have heard that it lets you get "close to the machine."
Real software engineers play tennis. In general, they don't like any sport that involves getting hot and sweaty and gross when out of range of a shower. (Thus mountain climbing is Right Out.) They will occasionally wear their tennis togs to work, but only on very sunny days.
Real software engineers admire PASCAL for its discipline and Spartan purity, but they find it difficult to actually program in. They don't tell this to their friends, because they are afraid it means that they are somehow Unworthy.
Real software engineers work from 9 to 5, because that is the way the job is described in the formal spec. Working late would feel like using an undocumented external procedure.
Real software engineers write in languages that have not actually been implemented for any machine, and for which only the formal spec (in BNF) is available. This keeps them from having to take any machine dependencies into account. Machine dependencies make real software engineers very uneasy.
Real software engineers don't write in ADA, because the standards bodies have not quite decided on a formal spec yet.
Real software engineers like writing their own compilers, preferably in PROLOG (they also like writing them in unimplemented languages, but it turns out to be difficult to actually RUN these).
Real software engineers regret the existence of COBOL, FORTRAN and BASIC. PL/I is getting there, but it is not nearly disciplined enough; far too much built in function.
Real software engineers aren't too happy about the existence of users, either. Users always seem to have the wrong idea about what the implementation and verification of algorithms is all about.
Real software engineers don't like the idea of some inexplicable and greasy hardware several aisles away that may stop working at any moment. They have a great distrust of hardware people, and wish that systems could be virtual at ALL levels. They would like personal computers (you know no one's going to trip over something and kill your DFA in mid-transit), except that they need 8 megabytes to run their Correctness Verification Aid packages.
Real software engineers think better while playing WFF 'N' PROOF.
Page 11 of 20 «« Previous | Next »»