Barbarians Led by Bill Gates: Microsoft from the Inside: How the World's Richest Corporation Wields Its Power


"Microsoft, a rather new corporation, may not have matured to the position where it understands how it should act with respect to the public interest."-U.S. District Judge Stanley Sporkin. Teamed with the daughter of one of Bill Gates's closest associates, thirteen-year Microsoft veteran Marlin Eller shows us what it was like at every step along Gates's route to world domination, making all that's been written before seem like a rough guess. If the Justice Department had Eller and Edstrom investigating the current-headline-making antitrust case,

... See more details below
Available through our Marketplace sellers.
Other sellers (Hardcover)
  • All (37) from $1.99   
  • New (4) from $2.95   
  • Used (33) from $1.99   
Sort by
Page 1 of 1
Showing All
Note: Marketplace items are not eligible for any coupons and promotions
Seller since 2015

Feedback rating:



New — never opened or used in original packaging.

Like New — packaging may have been opened. A "Like New" item is suitable to give as a gift.

Very Good — may have minor signs of wear on packaging but item works perfectly and has no damage.

Good — item is in good condition but packaging may have signs of shelf wear/aging or torn packaging. All specific defects should be noted in the Comments section associated with each item.

Acceptable — item is in working order but may show signs of wear such as scratches or torn packaging. All specific defects should be noted in the Comments section associated with each item.

Used — An item that has been opened and may show signs of wear. All specific defects should be noted in the Comments section associated with each item.

Refurbished — A used item that has been renewed or updated and verified to be in proper working condition. Not necessarily completed by the original manufacturer.

0805057544 Only 1 copy left. Clean, unmarked copy. Hardcover, with dust jacket- In great shape! Got any questions? Email me; I'm happy to help!I can send expedited rate if you ... chose; otherwise it will promptly be sent via media rate. We recommend selecting Expedited Shipping to get your book as fast as possible. Read more Show Less

Ships from: Los Angeles, CA

Usually ships in 1-2 business days

  • Canadian
  • International
  • Standard, 48 States
  • Standard (AK, HI)
  • Express, 48 States
  • Express (AK, HI)
Seller since 2011

Feedback rating:


Condition: New
USA 1998 Hardcover First Edition New in New jacket New First Edition Copy.

Ships from: Garland, TX

Usually ships in 1-2 business days

  • Standard, 48 States
  • Standard (AK, HI)
  • Express, 48 States
  • Express (AK, HI)
Seller since 2015

Feedback rating:


Condition: New
Brand New Item.

Ships from: Chatham, NJ

Usually ships in 1-2 business days

  • Canadian
  • International
  • Standard, 48 States
  • Standard (AK, HI)
  • Express, 48 States
  • Express (AK, HI)
Seller since 2015

Feedback rating:


Condition: New
Brand new.

Ships from: acton, MA

Usually ships in 1-2 business days

  • Standard, 48 States
  • Standard (AK, HI)
Page 1 of 1
Showing All
Sort by
Sending request ...


"Microsoft, a rather new corporation, may not have matured to the position where it understands how it should act with respect to the public interest."-U.S. District Judge Stanley Sporkin. Teamed with the daughter of one of Bill Gates's closest associates, thirteen-year Microsoft veteran Marlin Eller shows us what it was like at every step along Gates's route to world domination, making all that's been written before seem like a rough guess. If the Justice Department had Eller and Edstrom investigating the current-headline-making antitrust case, they would have on the record many of Microsoft's most respected developers directly contradicting the "authorized" version of events being presented in court. They would know the real scoop on how Windows was developed in the first place, shedding new light on the 1988 Apple v. Microsoft lawsuit over the alleged copying of the Mac. They would even know the real story of how Microsoft killed off Go Corporation, told for the first time by the man who did the deed, Marlin Eller himself. Revealing the smoke-and-mirror deals, the palms greased to help launch a product that didn't exist, and the boneyard of once-thriving competitors targeted by the Gates juggernaut, this book demonstrates with often hilariously damning detail the Microsoft muddle that passes for strategic direction, offset by Gates's uncanny ability to come from behind to crush whoever's on top.

Read More Show Less

Editorial Reviews

From Barnes & Noble
The Barnes & Noble Review
Bill Gates, the genius behind Microsoft, has always been something of an enigma in public perception. Shaped largely by PR wizardry and spin doctors, Gates has succeeded, for the most part, in controlling both his public image and his portrayal in the media. In recent months, though, this brilliantly crafted image has begun to unravel as Gates and Microsoft have been increasingly challenged by antitrust accusations and allegations of unfair play. Trustbusters, lawyers, and the media have willingly pounced, nipping at Gates's heels and demanding to know more about the business-as-usual Microsoft. The public begs to know: What exactly has been going on behind the doors of Microsoft?

Enter Jennifer Edstrom and Marlin Eller, who will appear in the Auditorium on July 22nd to chat about their controversial new book, Barbarians Led by Bill Gates: Microsoft from the Inside. Already making tidal waves, Barbarians furnishes the first truly inside look at America's most intriguing company. Edstrom, the estranged daughter of one of Gates's closest associates, and Eller, a 13-year Microsoft veteran and lead developer of the original Windows software, unearth the real story of Gates's Microsoft — told not by the flacks or the lawyers but by the people who actually design the software and write the code.

The portrait that emerges in Barbarians is certainly not one of organizational brilliance, but neither is it of corporate evil incarnate. The belly of this beast would more resemble a "Dilbert" cartoon if it weren't for the serious reality that Gatesisuncannily successful in crushing whoever's on top.

From the epoch-making 1983 Las Vegas launch of Windows to the ongoing Internet Explorer versus Netscape antitrust suit, Barbarians sets the record straight on a number of hotly debated — and often hotly litigated — turning points in the short but colorful history of the information age. Here, exclusive and remarkably candid interviews with senior Microsoft developers — some conducted just days before the Justice Department announced its inquiry into the company's business practices — inform us about the real and checkered history of the company. You'll learn the answers to these questions:

  • How interrelated — or unrelated — are Windows 95 and Internet Explorer?
  • How did Microsoft miss the Internet boat, letting Netscape capture the lead in web browsers, and then bounce back to nearly sink its burgeoning competitor?
  • How exactly was — or wasn't — Microsoft ripped off in the original development of the Windows interface?
  • How did Microsoft come from behind in pen computing to drive Go Corporation out of business (the truth of which eluded even Go CEO Jerry Kaplan in his own book)?

Barbarians Led by Bill Gates proves that the truth is always more outrageous than what you learn through outside reporting, corporate PR, or carefully worded legal documents. It is also clear that the Justice Department should have approached Edstrom and Eller to get the real story.

The daughter of Microsoft public relations guru Pam Erdstom ("Gate's Keeper") and a former lead Windows' graphics developer wax knowledgeably about whether billionaire Bill Gates heads an evil software empire clashing with US anti-trust laws, or is a sour grapes' victim of competitors like Netscape jealous of his phenomenal success. Annotation c. by Book News, Inc., Portland, Or.
Ray Duncan

A Developer's Eye View

The authors of Barbarians Led by Bill Gates are billing their book as a techno-expose: "Microsoft from the Inside." But it's mostly a confused mishmosh of anecdotes and pseudo-history. Marlin Eller's name is familiar to those of us who wrote applications for Windows during the early years. He worked as a mid-level programmer on Windows' graphics engine (GDI.EXE) for most of the last decade, and also had some involvement with Microsoft networking, Pen Windows, and video compression projects. Jennifer Edstrom, as you might have guessed, is the daughter of Microsoft PR tycoon Pam Edstrom. Jennifer's contribution to the book is unclear, except perhaps to pass on juicy stories overheard at Mom's house and give Eller pointers about which names to drop to make the book more marketable.

Those who buy this book for "smoking gun" evidence about Microsoft's predatory strategies will not learn anything new. It's clear from his own words that Eller had little access to Microsoft executives at the level where real decisions are made. His encounters with Gates, Ballmer, Myhrvold, Silverberg, and other Microsoft movers and shakers were limited to parties, project launches, technical reviews, and postmortems. Many of the quotes in the book have been lifted from interviews that have appeared in trade journals and newspapers and Microsoft court documents. Consequently, Eller's tales of conversations and industry events outside his limited programming domain must be viewed as dubious and third-hand at best. Jennifer Edstrom's mother had much a tighter relationship with the Microsoft leadership cadre than Eller.

Those who might buy this book for some insight into the dynamics of the PC software marketplace will also be disappointed. At one point Eller asserts:

"At any given time, Microsoft has lagged behind in networking, desktop, applications, on-line services, Internet technologies, and Web browsers. And yet the landscape is littered with the bones of Microsoft's competitors: VisiCorp, Lotus, WordPerfect, Novell, GO Corporation ... This corporate body count exists because Microsoft has always had one asset that no other company could touch -- Windows -- which Microsoft could leverage with unrivaled effectiveness." -- p. 207

This statement alone tells us that Eller has essentially no understanding at all of the history of Windows, even though he lived through it and was intimately involved with the product. If there's one asset that Microsoft had that no other company could touch -- and which made Windows' ultimate success possible in spite of its brain-damaged user interface, lousy performance, mountains of bugs, and Eller's own dismally-architected graphics engine -- it was Microsoft's cash cow MS-DOS. VisiCorp, for example, dropped off the radar screen years before anyone anywhere was convinced that Windows would ever be a viable platform for applications.

One characteristic Barbarians Led by Bill Gates does offer that is relatively unique is some of the most execrable writing and editing ever to be inflicted upon an unsuspecting public by an otherwise reputable mainstream book publisher. Portions of it were actually painful to read. For example, on page 109, we find the sentence:

"LAN Man is piss ant."

I have to admit that this sentence stumped me at first. I slogged my way through the rest of the book, but the meaning of these five words continued to nag at me, and eventually I puzzled out two possible interpretations. One is that the intended word is "pissant" (an obscure old slang word for an insignificant or contemptible person or thing), and that the manuscript went straight from the transcriptionists to the typographers without ever being touched by an editor. The other is that the intended word is "puissant" (mighty, strong, powerful), and that the Microsoft programmers being quoted are not only ignorant of the word's origins and spelling, but have inverted its meaning as well.--Dr. Dobb's Electronic Review of Computer Books

Read More Show Less

Product Details

  • ISBN-13: 9780805057546
  • Publisher: Holt, Henry & Company, Inc.
  • Publication date: 6/15/1998
  • Edition description: LST ED.
  • Edition number: 1
  • Pages: 272
  • Product dimensions: 6.26 (w) x 9.28 (h) x 1.05 (d)

Meet the Author

Jennifer Edstrom is the daughter of "Gates's Keeper," Pam Edstrom, Microsoft's PR guru since 1982. Marlin Eller was from 1982 to 1995 principle architect of Windows, the development lead on Pen Windows, and central to Microsoft's first foray into Internet communications.

Read More Show Less

Read an Excerpt

Chapter One


Microsoft, a rather new corporation, may not have matured to the
position where it understands how it should act with respect to
the public interest and the ethics of the marketplace.

—U.S. District Judge Stanley Sporkin

    Nathan Myhrvold's pudgy fingers whirred across the keyboard as he peered into his 21-inch computer monitor. Most Microsoft developers would have killed for such a luxury, but Myhrvold was not just some hacker. He was a Ph.D. physicist who had worked on quantum field theories of gravitation with Stephen Hawking at Cambridge. He was also Gates's handpicked technovisionary, chosen to lead Microsoft into the future. Myhrvold had always indulged himself with the newest and best—whether in technology or gourmet cuisine—even before his own company, DSR, was acquired by Microsoft in 1986.

    He finished running a spell check through his latest interoffice memo, "Formats and Protocols for Consumer Information." Myhrvold typed blindingly fast. He had early on rejected the old-fashioned QWERTY keyboard developed to keep typewriter keys from sticking if people typed too fast. Instead he used the DVORAK keyboard, designed in 1936, which allowed him to type up to 100 percent faster.

    And Myhrvold typed a lot.

    The distribution list for this latest opus included the usual suspects: Bill Gates, Mike Maples, Paul Maritz, Charles Simonyi, along with key developerssuch as Marlin Eller and Murray Sargent. In total the memo would reach forty-four people, and it would change the direction of the company.

    Leaving his secretary to disperse his literary output, Myhrvold walked into Eller's office. It was just two doors down from his in Building 9, one of the original structures that looked out over the fountain in the center of Microsoft's campus. Eller was a bright developer and also conceivably one of Microsoft's more stubborn ones. He had been there for years before Myhrvold arrived, and he maintained the healthy skepticism of an old-timer.

    "Marlin, is your group fully staffed yet?" Myhrvold asked.

    Eller looked up from his 17-inch screen and stopped typing.

    "Ah, yeah," Eller said. "Thanks for sending Gordo."

    Nathan grinned. Gordon Whitten was another bright old-timer and completely unmanageable, just like Eller. Myhrvold had decided they were the perfect match, hoping, maybe, that they'd cancel each other out.

    Myhrvold turned and headed out the door.

    "By the way," he said over his shoulder, "take a look at my memo. I've outlined everything your group is doing."

    Eller rolled his eyes.

    The memos Myhrvold wrote were internal sales pitches, mostly to convince Gates that the technologies Myhrvold talked about were worth funding. The memos were also territory markers, notifying other executives to stay off Myhrvold's turf. "This is what MY group is doing. WE will handle it." Included, also, were implicit warnings about any outside competition.

    Myhrvold's memos often caused heated reactions among people at Microsoft. Developers like Eller gnashed their teeth over them because they included marching orders for technologies that were obviously decades into the future. And while some of Myhrvold's ideas were truly visionary, others were just plain bizarre. Myhrvold was a very broad thinker—he read a lot—but he was not necessarily a deep thinker, People who read Myhrvold's memos couldn't always discriminate between what was real and possible, and what was pure sci-fi. Myhrvold himself never appeared to worry much about that distinction, making his memos all the more dangerous because it was so hard to argue against them. How could you prove he was wrong when he was referring to something that might not happen for another ten years?

    Eller had no reason to dread this particular memo. The research in his own group was going beautifully, and there was no reason to think Myhrvold's latest diktat would change that.

    He left his office and walked down the corridor to the center of Building 9. All the buildings at Microsoft were shaped like an X. Supply rooms, mail rooms, and cafeterias were all in the center of the X. Microsoft had adopted the building design from IBM. This way the company could optimize the number of window offices.

    Eller grabbed a Coke from the refrigerator, a freebie Microsoft provided for all its 11,000-plus employees, and headed for the mail room. He set down his drink and grabbed the pile of papers soon to be coming his way. On top was Myhrvold's memo. It looked thick.

    Eller walked back to his office. The even thicker stack of papers on his desk seemed to have accreted since he left just a few minutes before. He much preferred the company's internal E-mail system. With E-mail he could just delete random messages and memos instead of filling up his in-basket and then his garbage can with slush. He spent two hours each morning pouring through hundreds of electronic messages, but as soon as 11:00 A.M. rolled around, he just pushed "delete." If the message was important enough, Eller assumed, the sender would try again.

    He sat at his desk and glanced through Myhrvold's twelve-page report. The memo described the projects Myhrvold had in place to secure Microsoft's dominant position in the emerging market represented by the convergence of television and computers. Actually, it wasn't exactly Myhrvold's vision. It was a collection of other people's ideas brought together in coherent form. Myhrvold was simply the only one with the time to put the ideas on paper. Besides, he was one of the few Softies with a secretary to copy and distribute memos.

    Eller tilted back his ever-present black beret and took a sip of Coke. Even in the summer he wore his trademark chapeau to keep his balding head out of the sun. In winter he wore a beard, in summer his smiling face shined through. He licked his finger and flipped to page four, which detailed the technology that Eller himself was working on.

    Eller was in ACT, the advanced consumer technology group, which Myhrvold had recently set up. Gates had decided to make Microsoft the first software company with an internal division fully dedicated to advanced research. It would serve two purposes: to develop add-on products for Windows, and, as analysts have often speculated, to absorb some of the company's outrageously high profits, and thereby, ideally, lower the potential for further government scrutiny. Since 1988, prosecutors had kept Microsoft staked out as if they were the Gambino family, a trend that would only intensify as time went on.

    ACT's initial effort was to focus on interactive television and other broadband network applications as well as low-bandwidth on-line services, a.k.a. Internet technologies. Myhrvold had several pet projects in place, the most realistic of which was the low-bandwidth Internet strategy, outlined in the memo.

    Just a month earlier, Myhrvold had been standing with a marker at the white board, outlining different strategies.

    "Low bandwidth is the way to make money now," Eller said.

    Myhrvold scratched his beard and nodded in agreement. At least Eller thought Myhrvold's nod meant agreement.

    The low-bandwidth idea was to connect computers together over the humble telephone line using standard protocols to exchange information in the on-line world. It was, in short, the World Wide Web. Of course, in 1992, the Web didn't exist at Microsoft or anywhere else.

    Even so, the opportunity ripe for Microsoft at this moment was to create a standard protocol for the on-line world that everyone could adopt. Microsoft could then own the standards for all subsequent Internet applications—the Next Big Thing.

    Gates should have been a natural at this. After all, he was the Standardization King. Before Gates arrived on the computer scene in the mid-1970s, a wide variety of different machines cohabitated, but none of them could communicate with one another, and they had little in common. Gates's first bolt of genius was to unify them with Microsoft's BASIC programming language.

    Then, less than ten years later, Microsoft did it again. It brought graphics to the PC and set the new standard with Windows. So it was not a far-fetched idea that Microsoft could lay the same claim now to the Net. The Soft already had the knowledge to bring graphics on-line—Myhrvold said as much in his memo:

I believe that we will see a replay of this situation. There will be
dozens of crazy new consumer machines, each trying to do its
own thing. Almost all of them will fail in the end, just as all
early PCs failed. The ashes of these spirited attempts will be
the incubator for a small number of standard platforms which
will attain critical mass and ignite a mass market. Owning a
standard on all of the candidates is an incredibly powerful
thing because it makes it very unlikely indeed that you will be
blind-sided by new developments. The trick for a software
company in a time of hardware chaos is to make sure to have a
bet placed on the eventual winners, and there is no better way
to do this in early stages than to have a way in which you can bet on
all of them.

    But Myhrvold did not spend the whole memo talking about low bandwidth or Internet standards. He and Gates were also excited about an evolutionary dead end called high bandwidth.

    In 1992, Myhrvold was not the only futurist in the computer industry talking about the "grand convergence" of television and computers, a high-bandwidth strategy. Speculation ran rampant about a world with five hundred TV channels, video on demand, online shopping, and interactive games. Massive servers would house all of this information and shoot it down through fast wires into consumers' homes. It all sounded very intriguing. But also very far off in time. This was the Jetson-like world that captivated Bill Gates's geek imagination.

    The emerging low-bandwidth Internet could have been a starting place for Microsoft to facilitate that kind of convergence, but low bandwidth simply didn't turn Gates on. It was too ... mundane.

    David F. Marquardt, a general partner of Technology Venture Investors in Menlo Park, California, and a Microsoft board member, recalled his amazement that Microsoft was putting so little into the Net. "They weren't in Silicon Valley. When you're here you feel it all around you," he told Business Week in July 1996. He brought up the topic of the Internet at a board meeting in April 1994. Marquardt described Gates's response this way: "His view was the Internet was free. There's no money to be made there. Why is that an interesting business?"

    Gates instead would rhapsodize about a world with infinite channel choices, digital art on the walls, and computerized sound, light, and temperature controls throughout the home.

    Ironically, these hubristic notions had already placed what could have been the key to success in Microsoft's hands. In early 1992, they had established a project called Homer to look at setting communications standards for the home. Gates would later use some of these ideas for his $53.4 million mansion on Lake Washington. And it was this initiative that eventually gave rise to the Remote Information Protocol.

    The idea behind RIP, a concept that Netscape would later realize so beautifully, was to create a graphical user interface that would allow computer users to connect to information providers, much like today's World Wide Web. Microsoft already had an installed base of tens of millions of DOS and Windows users ready to go online. If Microsoft had simply bundled the RIP technology in the next version of its operating systems, the World Wide Web may have evolved in a very different way, leaving nothing for Netscape to create.

    Myhrvold gave Eller funding and staffing for the Remote Information Protocol group, and Eller took a handful of people with him from the Homer project. In searching the company to fill the other positions, he wanted to make sure he avoided QVers—Microsoft argot for people who were "Quietly Vesting." Usually they didn't have more than six months before their stock options fully vested. Typically they were already worth a few million, so during their last six months, QVers weren't exactly motivated.

    Microsoft was much more lenient about funding and forming groups in the early 1980s. In those days a developer would float an idea by Gates, and if it sounded reasonable, the money followed. Development leads were free to staff their groups with as many people as needed. The problem was, it was still hard to find enough truly first-rate minds to staff all of the groups.

    The hiring policy for the company had always been an open call for bright developers. Microsoft had plenty of work available, so when a talented person was spotted, they were hired—they weren't necessarily hired for a specific position.

    As standard Microsoft protocol, a dozen lead developers would interview each candidate, and of course everyone wanted the good ones. The head of the Excel group would decide they needed a certain developer. Someone from the Word group would claim they needed the person more. It became a shouting match.

    Eventually, Eller emerged with about a dozen people for his group, most of them from within Microsoft. Some had just finished other projects in networking or applications, others were just tired of the groups they were in, and some had been in the old Homer group.

    At this moment, Netscape didn't even exist. Sun Microsystems, a behemoth in the workstation market, was riding on hardware revenues from its UNIX business. They weren't focused on software—certainly they had not yet commercialized Java, Sun's now-dominant interpreted scripting language for the Internet.

    So the Net just loomed there like a great white whale on the horizon, and Eller was finally in a position to build what he had always wanted—an interpreted object-oriented scripting language. It had to be lightweight, portable, and secure, just like Sun's Java is today. But the interpreted scripting language was only one part of the Remote Information Protocol. RIP encompassed a number of Internet technologies including a browser, like Netscape's Navigator, compression and decompression technologies, and encryption.

    By December, Eller's group was rolling along. One day, Myhrvold caught Eller in the hall to discuss their progress.

    "Hey," Myhrvold said. "I had this cool idea for doing image compression. Check this out."

    Eller followed Myhrvold into his office. He sat on the leather couch while Myhrvold walked around the room waving his hands in the air, his eyes lit up, his voice giddy.

    "You know that shaded computer graphics stuff we've been talking about. It occurs to me you could represent the shading by the electric field given off by an electron charge. Think about it—if you've got a collection of static electric charges, they create this electric field. It's more intense around the charges, and it falls off as you move away from the charges as an inverse square." "Uhh, yeah," Eller said, pursing his lips.

    "Well, but you see ..." Myhrvold paused as he went to the white board and started drawing E and M equations. "There's all this machinery for solving electrostatic charge distribution problems, like Maxwell's equations. So you ought to be able to take a given electric field and figure out what the charge distribution would be to yield that particular field. Then you could compress the picture by solving for the electron charge distribution, and then just shipping down the locations of the electrons and what their charges are. Then the machine on the other end can reconstruct the picture by solving the field equation for the charges."

    Eller scratched his head beneath the beret. It had been eighteen years since his college mathematics major. He didn't remember any of the equations for doing charge distribution on electrons, and he didn't want to look them up. It wouldn't have done any good anyway. Myhrvold was just throwing out some random and utterly convoluted way of doing the same thing Eller was already going after on a much more direct path.

    Talking to Myhrvold was a little like smoking dope. It could give you "insights," but in the light of day those insights often didn't make any sense. Eller walked out of Myhrvold's office reeling and dizzy and looking for food.

    How could Gates put this guy in such a powerful position? It's not that Myhrvold wasn't smart—he was exceedingly smart. But Myhrvold was a cosmologist. Cosmologists studied physics, but then they wandered off into the big bang and exploding stars and what happened in the first nanosecond. Among experimental physicists, cosmologists were known to be flakes. While physicists were rounding out to the thirteenth decimal, cosmologists were talking about wormholes and super strings and what happened before the universe began.

    Plenty of developers resented Myhrvold. They were the ones who actually wrote code and knew the nitty-gritty. Myhrvold, being a big-picture guy, tended to forget how long it actually took to build something. Myhrvold argued that you could design a new graphics architecture in only two weeks. People like Eller, who had personally spent three years developing graphics for Windows, knew better.

    Eller was still trying to regain his balance as he walked down the stairs to check on one of his people.

    Everyone in Eller's group was in the same building, though spread apart. Microsoft's rapid growth had filled in all the nearby offices before his group had been fully staffed. Still, Eller worked hard to insulate his developers from upper-management politics, to allow them to focus on what they did best: code.

    Ideally, Eller wanted to enable users to have a highly interactive—and very cool—user interface. He didn't want a huge server doing all of the processing work. If the server was doing it all, the server quickly became bogged down, and users lost their interactivity. The idea was to be able to take an application—a shopping form, for instance—download most of it to the user, or client, so that it was running on the PC, then let the user play with the form and customize it.

    Eller had assigned a handful of people in his group to explore which interpreted scripting language they should use. Two people were looking at the C language, and one person was looking at transport layers, or how two computers would connect and communicate.

    Two of Eller's people were working on hacking up Visual BASIC, and two others were working on the Forth language. The Forth language was originally invented by physicist Charles Moore in the late 1960s. It was a widely used, but little known, computer language, and it was very easy to port to different machines. It was tiny and fit in about 3 kilobytes of memory, versus today's systems, which require megabytes, a difference of five orders of magnitude.

    Eller concluded that it was crucial to write an entirely new interpreted scripting language, and the issue was still a bit of a sore point with both Myhrvold and Gates.

    "The last thing this company needs is another fucking language," Myhrvold had said.

    Eller saw Myhrvold's mouth move, but when the cosmologist talked, it was Gates's voice that Eller heard. Gates wanted all of the languages to be the same—BASIC. After all, Gates had written it. But despite Chairman Bill's monument to code, the computer world needed to move on.

    And Eller knew BASIC wouldn't work in this application anyway because the scripting language in RIP had to be compact and object oriented. So Eller's group forged ahead.

    By the spring of 1993, the RIP group had made significant progress developing their lightweight interpreted scripting language. In fact, if they had stayed on track, they could have gotten RIP bundled into the then upcoming version of Windows 3.11, which was released in November 1993. What would Judge Penfield Jackson have made of that?

    But things were already starting to disintegrate.

    Myhrvold, who had earlier agreed with Eller that low bandwidth was the way to go, now seemed bored with the project. Instead, he was putting all his energy into the high-bandwidth interactive TV project.

    Matters weren't helped any when, four months into the project, a buddy of Myhrvold's named Craig Mundie was brought in to be Eller's manager. Mundie, in his forties, had been the CEO of Alliant Computer—before the company went bankrupt. Alliant was a supercomputer shop that had focused on high bandwidth.

    When Mundie came on board he promptly went to Eller's office to check on the RIP team's focus. This was December 1992, and he was not pleased to find Eller and his troops still working on low-bandwidth solutions.

    "You're going to have so much bandwidth in the short term, it won't even be funny," Mundie told Eller. "Furthermore, wasting time on 9600 baud lines is just stupid. And last, but not least, you need to get with the program. You better get the message to your troops, 9600 baud is bullshit. You should be focusing on broadband!"

    "Yeah, sure," Eller lied. "We can have a joint meeting, and I'll review the troops. No problem, Craig."

    When Mundie came back a week later, he was surprised to find that Eller's troops hadn't got the message. They looked at Mundie with glazed eyes as he talked about how broadband was going to be all over the planet. They stared blankly as Mundie explained how people wouldn't need low bandwidth and that everything Eller's group was doing, squeezing bytes here and there to fit on a 9600 baud line, was just a waste of time.

    Eller said nothing, and the entire group gazed back at Mundie with a placid look that, deep down, silently expressed, "Screw you."

    Mundie followed Eller back to his office for a closed-door post-meeting and demanded to know why Eller's troops weren't on board.

    "Well, you know, Craig, they're a hard bunch of guys, and they're kind of focused on the low-bandwidth strategy."

    Eller paused for a moment, adjusting his grip for the proper spin. "And I don't know that we need to diffuse that thrust. I mean I'm sure that broadband is going to be great stuff in the future ... and I'd be all over it if I weren't all over this project. But I am."

    That's when it became apparent to Mundie that Eller was unmanageable.

    Eller had been at Microsoft for more than a decade. He had spent three years in the "death march" to develop the Windows graphics subsystem, GDI, the graphics still used in Windows 95 today, He had also created Pen Windows, Gates's pet project at the time.

    But as Microsoft grew, even top developers like Eller no longer had a direct line to Gates. In the early days of Windows 1.0, Eller had squabbled and sparred with Gates regularly. People on the Windows team had gone to movies together and worked till 2:00 A.M., happily hacking as the rock music blasted. Now there were vice-presidencies growing like kudzu. There were too many people to placate, to convince, to cajole.

    Plowing through Microsoft's weed-infested org chart, Eller knew the only way to keep RIP alive was to take it straight to Bill.

    A recruit party was coming up at the Seattle Museum of History and Industry, and Eller was responsible for chaperoning his newbies to the function. Recruit parties, according to a recent Gates memo, were no longer optional. This was a command performance.

    Once upon a time, a recruit party consisted of a case of beer and pizzas in cardboard boxes. The developers would all sit in the lobby of the Northrup building talking to Gates about how great the world would be with their new software. But even now, with oldtimers chumming up acne-faced kids over prawns and chardonnay, Eller still knew that, once the caterers started cleaning up, it would be an opportune time to talk to the boss.

    After Eller's new hires had gone, he walked up to Gates in the "Keys to History" exhibit. The caterers were breaking down tables and chairs, and Gates was standing at the buffet chewing on a shrimp the size of Manhattan.

    "Hey, Bill," Eller said.

    Gates acknowledged Eller with a nod.

    "I think we've got a good group here," Eller went on. "Especially that new kid who's gonna work with me on RIP."

    Gates nodded again, but the richest man in America seemed otherwise engaged.

    "You know," Eller said. "I don't think you're giving enough attention to low bandwidth."

    Gates continued chewing, and Eller picked up a shrimp himself. Gates looked at him and pushed the bridge of his glasses back up onto his nose.

    "We have low bandwidth today," Eller continued. "Everybody has a modem. People can exchange information at 9600 baud. We don't need to wait for fiber. This way it's an evolution where everyone keeps their existing software and computers. We should do that now."

    A long silence hung suspended between the two. Eller knew Gates had heard him. But Gates gazed off in the distance, seemingly oblivious to the Willits canoe, to the black and white stills of early Seattle settlers—and to Eller's point.

    "Uh huh," Gates muttered.

    And at that moment, Microsoft missed the technology boat. Millions of future Web surfers bearing the Microsoft logo simply turned and paddled back out to sea.

    In the early days of pizza and beer, Gates would have been animatedly talking ideas with a developer. He would have been all over the issues, saying, "Why will this be more important than that? Is this really the right thing?"

    Now Microsoft had become so big that Gates could no longer focus. Eller realized that Gates wasn't going to encourage anyone to support RIP. But Eller was tired of fighting, tired of persuading, tired of convincing. He walked away from the party disillusioned, but also realizing that maybe this moment of blindness was not really so unusual. Knee-jerk reactions and panic had always been a way of life at Microsoft. Working for Chairman Bill had been like white-water rafting, not ocean cruising. There were so many other near misses and episodes of dumb luck that the public and Microsoft investors never knew about. Now that the company had turned into its nemesis and become just another lumbering giant like IBM, Eller wondered how long market momentum would continue to carry it. Then again, Microsoft had three very substantial attributes to see it through: a lush array of laurels to rest on, enormous cash reserves, and a bone-crushing hold on the ultimate core asset—total control of the operating-system business.

    If the past was any indication, Gates would be able to leverage that asset, wielding it like a club if need be, well into the future. And woe betide any competitor who got in his way.

A Journey Among the Christians of the Middle East


Henry Holt and Company, Inc.

Copyright © 1997 William Hamilton-Dalrymple. All rights reserved.

Read More Show Less

Table of Contents

Prologue 3
1 The Road behind 5
2 The Making of the Microsoft Marketing Machine 21
3 Be Like the Mac 45
4 Death March 59
5 Anything for IBM 71
6 The Clandestine Effort 87
7 Bad Marriages End in Divorce 97
8 Pen Ultimate Warfare 113
9 Go-ing Down 129
10 Meet the Jetsons 145
11 High Road to Memphis - Low Road to MSN 161
12 Dodging Bullets 181
13 Windows 95 - Power in Numbers 189
14 Continual Chaos 207
Epilogue 229
Notes 233
Index 245
Read More Show Less

Interviews & Essays

Q:  Jennifer, you came to this book project with a unique background, in that your mother has handled Microsoft's public relations since 1982. How did growing up inside Microsoft, so to speak, influence the writing of this book?

A:  It certainly didn't influence my decision to write the book. When Marlin asked me to be coauthor, I wasn't signing up to write a book about my experiences and views of Microsoft; I was writing his story, the story of the developers.

I grew up inside the world of Microsoft executives. I went to Microsoft functions, including industry conferences, weddings, dinner with Gates, and even though I watched my mother create the "Chairman Bill" mythology, I bought the whole thing. Gates was "good," a great developer who built great software that didn't have any bugs; he was personally responsible for all of the innovative decisions made at Microsoft. All Microsoft competitors were evil. Microsoft could do no wrong, and any competitor or industry pundit who said otherwise was blatantly off the mark.

Now, thanks to years interviewing Marlin and other hands-on developers, I feel like Dorothy when she finally got to Oz and peeked behind the curtain. Bill Gates is a very smart guy, but also very human. He's been as much monkey wrench as wizard, and he hasn't always walked the straight and narrow.

Q:  Given that you are the daughter of Pam Edstrom, Gates's PR guru, some people are questioning your reasons for writing this book.

A:  I'm a journalist. Marlin got me inside the guts of one of the largest companies in the world, Microsoft, to talk with the developers who actually wrote the software that made the company so successful in the first place. I wanted to hear, and then tell, their experiences. I don't know any journalist who would turn down that kind of opportunity, regardless of who they were or weren't related to.

This book is neither PR nor sour grapes. It is also not a story about my mother. Nor is it a story of Microsoft. I've simply reported the developers' accounts of Microsoft from the inside. It's my job as a journalist to report the facts. And that's exactly what I've done.

Q:  Marlin, is it true that Microsoft was poised to take control of the Internet long before Netscape took the lead with web browsers?

A:  We were working on something similar to Java in '91, but Microsoft had just become a noisy development environment where it was hard to get the right projects funded. The idea was to include it in Windows so that people could do distributed applications across slow telephone networks, i.e. the Internet. The project got reorganized out of existence in a turf war.

Q:  Marlin, your book suggests that Windows happened accidentally and essentially in spite of Bill Gates. Explain that.

A:  Windows was several years late when it first came out, and IBM wasn't buying it. IBM convinced Bill that he should junk Windows and work on OS/2. The entire company was ready to ditch Windows and was banking on OS/2. A small maintenance team was left to tie up the loose ends. It was the best thing that ever happened to Windows -- now that it was no longer strategically important, the little development team was free to hack and slash away on it however they chose, without Bill's "help." Lo and behold, the small fleet team outproduced the huge, blundering team. Upper management was pretty surprised when Windows whupped OS/2 in the marketplace.

Read More Show Less

Customer Reviews

Be the first to write a review
( 0 )
Rating Distribution

5 Star


4 Star


3 Star


2 Star


1 Star


Your Rating:

Your Name: Create a Pen Name or

Barnes & Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation


  • - By submitting a review, you grant to Barnes & and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Terms of Use.
  • - Barnes & reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously
Sort by: Showing 1 Customer Reviews
  • Posted October 31, 2008

    more from this reviewer


    An interesting look an insiders view of Microsoft. Was Windows 3.0 really a project on the backburner that someone worked on in their spare time? A bit too much technical jargon and praising of the author's mother.

    Was this review helpful? Yes  No   Report this review
Sort by: Showing 1 Customer Reviews

If you find inappropriate content, please report it to Barnes & Noble
Why is this product inappropriate?
Comments (optional)