Netscape Opens Mozilla Code to Fight Microsoft Before AOL Takeover
znoopy2k
Netscape's decision to open-source its browser failed to counter Microsoft's desktop monopoly, forcing an AOL buyout as revenues collapsed and engineers burned out before shipping a finished replacement.
AI-assisted summary of Netscape Mozilla Documentary 1998 - 2000 ProJect Code Rush - creative common licence — original source. Check the original for full context.
Source published:
Key ideas
- Faced with Microsoft bundling Internet Explorer into Windows, Netscape made the unprecedented move to open-source its flagship browser codebase under the project name Mozilla on March 31, 1998. (1:57)
- Netscape's standalone browser revenue collapsed from 50% of corporate turnover to 0% in just 18 months, while the division continued to cost approximately $30 million annually to maintain. (37:43)
- America Online acquired Netscape in a deal announced at $4.2 billion that swelled to roughly $10 billion upon closing in spring 1999 as Netscape stock surged from $20 to around $172 per share. (48:29)
- A federal antitrust judge formally ruled in late 1999 that Microsoft operated an illegal monopoly, even as Netscape struggled to ship a functional consumer browser from the open-source Mozilla codebase more than 18 months post-release. (54:34)
Detailed notes
## Background Published on YouTube by znoopy2k on July 15, 2009, this video presents Code Rush, a 2000 PBS documentary chronicling the frantic work culture of Silicon Valley during the height of the dot-com era. The film follows Netscape engineers as they pursue a groundbreaking strategy to save their embattled company by releasing the proprietary source code for their web browser to the public under the open-source Mozilla project.
## TL;DR Facing an existential threat from Microsoft's desktop monopoly, Netscape bets its corporate survival on releasing its proprietary browser codebase to the public under the Mozilla project by a strict March 31, 1998 deadline. The documentary tracks engineers and build managers through punishing shifts, cubicle living, and last-minute legal hurdles as they push the source code live to rally global developer contributions. Despite pulling off the technical release and attracting young volunteer prodigies, Netscape watches its browser revenues collapse to zero, accelerating internal restructuring and engineering burnout. The saga concludes with America Online acquiring Netscape for billions of dollars, generating massive paper wealth while disillusioned veteran engineers walk away just as federal antitrust authorities rule against Microsoft.
## Atmosphere & style The film carries a gritty, cinéma vérité intensity, immersing the viewer in the fluorescent-lit claustrophobia, sleeping-bag-under-the-desk exhaustion, and high-stakes pressure of late-1990s startup culture. It balances technical minutiae with an intimate, melancholic emotional arc, contrasting the caffeinated idealism of hacker purists against the relentless machinery of corporate monetization. Watching it feels raw and unvarnished, capturing the disorienting gold rush atmosphere where engineers sacrifice health and family life inside an intoxicating, monastery-like technological boom.
## Bulletin - [01:57](https://www.youtube.com/watch?v=u404SLJj7ig&t=117s) Faced with Microsoft bundling Internet Explorer into Windows, Netscape made the unprecedented move to open-source its flagship browser codebase under the project name Mozilla on March 31, 1998. - [37:43](https://www.youtube.com/watch?v=u404SLJj7ig&t=2263s) Netscape's standalone browser revenue collapsed from 50% of corporate turnover to 0% in just 18 months, while the division continued to cost approximately $30 million annually to maintain. - [48:29](https://www.youtube.com/watch?v=u404SLJj7ig&t=2909s) America Online acquired Netscape in a deal announced at $4.2 billion that swelled to roughly $10 billion upon closing in spring 1999 as Netscape stock surged from $20 to around $172 per share. - [54:34](https://www.youtube.com/watch?v=u404SLJj7ig&t=3274s) A federal antitrust judge formally ruled in late 1999 that Microsoft operated an illegal monopoly, even as Netscape struggled to ship a functional consumer browser from the open-source Mozilla codebase more than 18 months post-release.
## Key takeaways - [00:17](https://www.youtube.com/watch?v=u404SLJj7ig&t=17s) Silicon Valley at the peak of the dot-com boom operated like a high-stakes gold rush, where software engineers wielded outsized cultural and economic influence. - [01:57](https://www.youtube.com/watch?v=u404SLJj7ig&t=117s) Netscape gambled its survival on open-sourcing its browser code to establish Mozilla as a community-driven web standard while driving enterprise server sales. - [03:11](https://www.youtube.com/watch?v=u404SLJj7ig&t=191s) Preparing Mozilla for public release required auditing 2 to 2.5 million lines of code to eliminate proprietary third-party liabilities under an unforgiving public deadline. - [06:06](https://www.youtube.com/watch?v=u404SLJj7ig&t=366s) Engineering culture imposed extreme physical demands, with developers working round-the-clock shifts and sleeping under cubicle desks to resolve blocking bugs. - [09:06](https://www.youtube.com/watch?v=u404SLJj7ig&t=546s) The dot-com programming workforce drew heavily from a generational cohort immersed since childhood in computer logic, mathematics, and early coding. - [14:36](https://www.youtube.com/watch?v=u404SLJj7ig&t=876s) Microsoft's aggressive bundling of Internet Explorer directly triggered federal antitrust scrutiny and Senate hearings regarding monopolistic foreclosure of distribution channels. - [22:24](https://www.youtube.com/watch?v=u404SLJj7ig&t=1344s) A last-minute Apple intellectual property conflict forced an overnight clean-room rewrite hours before the scheduled public release of the Mozilla codebase. - [24:07](https://www.youtube.com/watch?v=u404SLJj7ig&t=1447s) On March 31, 1998, Netscape published the Communicator source code to mozilla.org, instantly creating an open public software asset. - [27:25](https://www.youtube.com/watch?v=u404SLJj7ig&t=1645s) The open-source model mobilized global outside contributors, including high school student Stuart Parmenter, who rewrote core rendering components remotely. - [30:26](https://www.youtube.com/watch?v=u404SLJj7ig&t=1826s) Financial analysts remained skeptical of the free-software strategy, demanding proof that open-sourcing client code could yield a sustainable corporate business model. - [34:29](https://www.youtube.com/watch?v=u404SLJj7ig&t=2069s) Stock option grants fueled intense labor mobility across Silicon Valley, minting dozens of new millionaires daily while leading some engineers to view equity as a lottery ticket. - [41:24](https://www.youtube.com/watch?v=u404SLJj7ig&t=2484s) Netscape agreed to a buyout by America Online, sparking deep cultural friction among engineers who viewed AOL as an unsophisticated marketing-driven service. - [45:02](https://www.youtube.com/watch?v=u404SLJj7ig&t=2702s) Key technical leaders, including Jamie Zawinski and Tara Hernandez, departed Netscape citing extreme burnout, corporate disillusionment, and the heavy personal toll of startup life. - [51:57](https://www.youtube.com/watch?v=u404SLJj7ig&t=3117s) Industry observers expressed growing alarm that the rapid commercialization and corporate consolidation of the internet risked turning an open digital frontier into broadcast television.
## Detailed walkthrough ### [00:17](https://www.youtube.com/watch?v=u404SLJj7ig&t=17s) The Silicon Valley Gold Rush and the Power of Code
People travel from all over the world seeking the mythical Silicon Valley experience, touching down with a single suitcase in hand before steering south down Highway 101. Instead of a futuristic wonderland, they are greeted by an unremarkable landscape of concrete freeways, generic office parks, and strip malls that look identical to any other place they have ever lived, leaving them to wonder why they came in the first place. Yet beneath that mundane exterior lies the invisible engine driving modern civilization. Code is described as the foundational lifeblood of modern society, turning computers into the central medium through which human culture operates.
Technology has evolved into an object of near-religious reverence, inspiring awe both for the machines themselves and for the small cadre of engineers who build them. The environment mirrors historical manias like the California Gold Rush or early 1920s Hollywood. A tiny group of software architects wields disproportionate influence over the future, quietly defining how the rest of humanity will navigate an increasingly digitized, computer-mediated existence.
```mermaid flowchart LR accTitle: Netscape Open Source Strategy accDescr: The cycle of releasing Mozilla source code to outside developers to counter Microsoft. subgraph Netscape ["Netscape Engineering"] A["Auditing & Bug Fixing<br/>2.5M Lines of Code"] --> B["Continuous Integration<br/>Tara Hernandez Builds"] B --> C["March 31 Release<br/>Mozilla Source Code"] end subgraph Community ["Open Source Community"] C --> D["Outside Hackers<br/>Community Patches"] D --> E["Browser Improvements<br/>Industry Standard"] end E -.->|"Rebuild Netscape Fortunes"| A ```
[01:57](https://www.youtube.com/watch?v=u404SLJj7ig&t=117s) Netscape’s Radical Gamble: Giving Away Mozilla
Just three years after a band of Netscape Communications engineers transformed computing by creating the browser that made surfing the World Wide Web accessible, the company faces an existential crisis. Microsoft, the software colossus, has leveraged its desktop monopoly to drive Netscape into the ground. Facing imminent ruin, Netscape’s leadership opts for a breathtakingly radical gamble: giving away the proprietary recipe of its core browser to outside programmers for free.
By publicly releasing the source code under the project name Mozilla, Netscape hopes external software developers will rally around the software, contribute improvements, and establish Mozilla as the universal internet standard. If successful, this open-source offensive will revitalize the company's sagging fortunes and funnel users toward its companion commercial server products. For the engineering team charged with pulling off this pivot, the directive marks the start of a grueling, year-long struggle to remake the software and rescue their company.
[03:11](https://www.youtube.com/watch?v=u404SLJj7ig&t=191s) The March 31 Deadline and the Engineering Roster
With the public launch date of March 31 looming only weeks away, internal panic begins to mount. Netscape previously promised the world it would deliver Netscape Communicator’s source code on that exact date, yet the sheer volume of unfinished work makes the timeline appear impossible. The team gathers in tense meetings, staring each other down to identify where their assumptions fell apart and trying to determine how to rectify their miscalculations before time runs out.
``` NETSCAPE CORE TEAM +------------------------------------------------+ | Michael Toy - Engineering Project Lead | | Jim Roskind - Software Security/Standards| | Jamie Zawinski - Open-Source Evangelist | | Tara Hernandez - Build / Release Manager | | Scott Collins - Late-Night Troubleshooter | +------------------------------------------------+ ```
Michael Toy, one of Netscape’s earliest employees, is appointed to lead the team readying Mozilla for the public release. Toy maintains a self-deprecating humor about the crushing pressure and the looming corporate giant in Redmond. As Toy puts it: “We're probably doomed, we're probably going to fail, Microsoft is probably going to squish us like a bug anyway, but just because we're doomed it doesn't mean you know we can't get up in the morning and do work.” Toy jokes that to his young children, who know only the office’s nerf dart guns, giant bouncing balls, and complimentary soda, their dad essentially works at Disneyland, even if his actual days consist of sitting through depressing meetings and wading through endless email.
Jim Roskind, an authority on software security, is brought in to impose rigorous engineering discipline, describing the schedule as an intense hybrid of a marathon and an all-out sprint where stopping to walk guarantees failure. At the same time, open-source evangelist Jamie Zawinski (jwz) attempts to rally outside hackers, hoping the broader programming counterculture will embrace the free-software ideology and contribute code to Netscape's cause. Before that can happen, the team faces the staggering task of manually auditing between two and two-and-a-half million lines of code, reviewing individual sections twice to ensure no proprietary or third-party liabilities slip through.
[06:06](https://www.youtube.com/watch?v=u404SLJj7ig&t=366s) Build Crashes, Cubicle Living, and the Nightmare of Debugging
The engineering floor operates in a state of continuous triage managed by build manager Tara Hernandez. She monitors automated dashboards where green builds signify stability, only to watch waves of incoming code check-ins crash the compiler and bring company-wide development to an abrupt halt. When catastrophic breakages occur, the burden falls on veteran programmers like Scott Collins, who stays awake through punishing 60-hour shifts to debug erratic code paths.
Collins has transformed his cubicle into a self-contained living module, outfitting it with a couch, an under-desk mattress, drawings from his children, and direct control over the overhead light switches. Reflecting on the sleepless nature of the job, Collins contrasts tech with standard corporate vocations: “Selling real estate you sell to people, the people are asleep at night, when they go to sleep you have to stop selling real estate, computers never sleep.”
Tracking and resolving thousands of subtle software bugs becomes an exercise in frustration. A single unresolved bug in a developer's queue can prevent the entire application from compiling, jeopardizing the hard launch date. Debugging complex software is compared to baking a massive, multi-ingredient recipe: - If twenty people build a physical car, a supervisor can stand forty feet back and clearly see if someone failed to attach a wheel. - In software, forty developers dump hundreds of thousands of discrete code fragments onto a disk, making individual defects impossible to detect by visual inspection alone. - Like finding a batch of bad flour or misshapen chocolate chips only after a cake has been baked and tasted, engineers cannot verify functionality until the entire multi-million-line codebase is compiled together. - Since Netscape's founding, Mozilla's codebase has expanded thirty-fold, requiring an excruciating search to pinpoint precisely which line of code broke the build while the project clock ticks down.
[09:06](https://www.youtube.com/watch?v=u404SLJj7ig&t=546s) The Techie Mindset and Growing Up with Code
Those who master software describe programming as a blend of alchemy, wizardry, and elite athletics. Just as legendary baseball batters often cannot articulate the subconscious instincts that allow them to strike a fastball, top-tier software engineers frequently struggle to explain their innate capacity to navigate complex computer systems. Within Netscape, this talent is tied to growing up "techie"—being immersed in computers, logic puzzles, and structural games like Erector sets and Legos long before reaching adulthood.
Jim Roskind recalls spending much of his childhood between ages 6 and 17 seeking refuge from an intimidating outside world by immersing himself in mathematics and problem-solving, finding that working through abstract puzzles elicited the exact same mental sensations required for high-stakes programming.
This culture also fosters generational tech families. One engineer recounts having a mother who serves as a high-ranking director at Sun Microsystems and jokes about the internal Netscape shorthand for user-friendliness: - Software usability across the industry is traditionally benchmarked against the question, “Can my mom use it?” - At Netscape, an engineer jokes that the standard breaks down because “My mom can write optimizing compilers.” - Having earned $50 an hour writing computer code by the age of 12, engineers view the Silicon Valley dot-com boom as a distinctive youth culture powered by young programmers willing to lay their entire personal lives on the line for software.
[11:24](https://www.youtube.com/watch?v=u404SLJj7ig&t=684s) The Modern Village and Silicon Valley Monasticism
Silicon Valley engineering culture demands total immersion, requiring what observers describe as a round-the-clock, 365-day-a-year life commitment. Engineers throw themselves entirely into high-stakes ventures with zero institutional stability, giving rise to a poignant contradiction: as one commentator puts it, “there's no stability here so it's very kind of a weird um irony that the very people who are inventing the future can't see their own future.” The work environment resembles a cloistered fraternity or an insular guild. A narrator notes, “this is a monklike existence there are very few women in these societies these are male societies they are secret societies they function very much like the Masons or some street gang.”
Inside the Netscape offices, this intense dynamic produces a blend of exhaustion, high stress, and dry, teasing camaraderie. In one meeting room, an engineer arrives late and is instantly accosted with mock outrage: “Did you not receive a mail saying if you have a source P1 bug you will be in here at 1:30?” When he sheepishly replies that he thought the meeting was at 2:30, a colleague snaps, “Now you're evil and stupid.” The engineer jokingly deflects, claiming he was merely operating in a different time zone. Because staff spend virtually all their waking hours at their desks, the workplace inevitably supplants external civic life, with one speaker observing, “all we have left to hold on to really is the workplace i mean it is the modern village.” It is the single space where people understand each other's histories, tolerate bad humor, and spontaneously invite colleagues out for late-night meals to blow off steam.
- Engineers endure a 24/7/365 lifestyle with little separation between personal and professional life. - Social interactions revolve almost exclusively around workplace relationships and shared deadlines. - The insular camaraderie mirrors an ancient trade guild or village community where colleagues rely on familiar routines and dark humor to survive stress.
---
[13:06](https://www.youtube.com/watch?v=u404SLJj7ig&t=786s) Herding Cats: The Hunt for Jeff Weinstein
At an all-hands status meeting, management attempts to shift the organization into crisis mode. The leadership makes clear that the casual pace of previous weeks is over: “the purpose of this meeting is to make sure that as a company we are incredibly focused on getting the bug count to zero uh we've been moderately focused up until now we need to be deadly focused from here on in.” However, the browser team immediately hits a wall because a critical contributor, Jeff Weinstein, is absent. He failed to check in over the weekend, neglected to answer emails, and let his phone ring out unanswered, with internal tracking systems merely suggesting he is somewhere on campus.
Managing software developers under extreme pressure is likened to an impossible balancing act: “The old saying is that trying to manage programmers is like trying to herd cats you know you you want them to be cats i mean if you like cats I mean because you want what's unique about that creature but they really don't all like to go in the same direction.” In less than four years, Netscape exploded from a tiny startup into an enterprise of over 2,000 employees spread across sprawling facilities. Locating a single programmer turns into an absurd physical scavenger hunt. Tara and a colleague comb the cubicles searching for Weinstein, declaring they are ready to “take a hit out on him” because critical work on the Macintosh platform is stalled waiting for his data. A staffer jokes that anyone wandering the floor should deliver a simple message to Weinstein when found: panic, run around, and warn everyone that the Mac build is completely doomed.
```mermaid flowchart TD accTitle: Bug Triage Bottleneck accDescr: Workflow showing how unassigned bug triage stalls until Jeff Weinstein is located. subgraph Management ["Management Directive"] M1["Status Meeting: Mandate Zero Bugs"] --> M2["Identify P1 Blocker Bugs"] end subgraph Bottleneck ["The Missing Engineer"] M2 --> B1["Jeff Weinstein Absent / Unreachable"] B1 --> B2["Macintosh Platform Stalled on Data"] B2 --> B3["Floor-by-Floor Search Across 2,000-Person Campus"] end subgraph Resolution ["Bug Resolution"] B3 --> R1["Weinstein Located at Desk"] R1 --> R2["Overnight Coding Marathon"] R2 --> R3["Critical Bug Count to Zero"] end ```
---
[14:36](https://www.youtube.com/watch?v=u404SLJj7ig&t=876s) David vs. Goliath: Netscape and Microsoft on Capitol Hill
Netscape's existential crisis traces directly back to Bill Gates and Microsoft. Recognizing Netscape Navigator as a foundational threat to Windows and his broader computing empire, Gates acted aggressively by bundling Internet Explorer directly into the Windows operating system at no charge. Netscape alleges that Microsoft systematically deployed coercive, exclusionary contracts to lock PC manufacturers into Internet Explorer and strangle Netscape's distribution channels.
The battle spills onto Capitol Hill, where the Senate Judiciary Committee convenes hearings to examine antitrust abuses in the software industry. Netscape CEO Jim Barksdale testifies directly opposite Bill Gates, striking a respectful yet firm posture: “And certainly nobody here on this panel is a greater admire of Mr gates or his company than I am but we do ask that Microsoft be held accountable for some of their actions actions that intimidate PC manufacturers to use their products and exclusionary practices that prevent them from using my products.” Gates mounts a staunch defense of unchecked market forces, arguing: “Not all companies succeed some failed to embrace change this is the way technology and the free market works.” He asserts that Silicon Valley's meteoric rise was achieved through unfettered innovation and the human desire to learn and excel, not government interference.
Thousands of miles away in Mountain View, engineers ignore the political drama and grind through sleepless shifts to hit the Mozilla public release deadline. Engineering leadership scoffs at academic theories of software methodology, recalling a visit from Harvard business academics who attempted to map Netscape's development against standard textbook doctrines: “A while ago some people from Harvard came and said 'Well how do you develop software we're writing a book.' And I talked about all the things that I thought were really important and they were just it felt to me like they were shaking their heads going 'Oh gee he doesn't know about principal 7 and oh he doesn't know about principal 22.' And in some ways they're right i really haven't got a clue right i really like to heir on the side of every day we wake up in the morning and say based on what I know today what's the best way to get to to where where we all want to go.” With more than two million lines of source code, leaders emphasize that no single team has time to inspect every line; they must act pragmatically on immediate daily realities.
- Microsoft leveraged OS dominance by giving away Internet Explorer for free and restricting original equipment manufacturer (OEM) channel access to rivals. - Jim Barksdale testified before the United States Senate, arguing that Microsoft's licensing tactics crossed antitrust boundaries. - Bill Gates defended Microsoft by framing corporate displacement as the natural outcome of a free market where companies that fail to adapt fall behind. - Netscape's internal engineering process prioritized iterative, pragmatic firefighting over formalized academic software development models.
---
[16:52](https://www.youtube.com/watch?v=u404SLJj7ig&t=1012s) Closing the Final Bugs and Achieving "Zorros"
With the March 31 open-source deadline only days away, the browser team finally tracks down Jeff Weinstein at his desk. As an expert in Netscape’s most arcane and convoluted subsystems, Weinstein is designated the most wanted man in the building, saddled with a list of blocking bugs that must be cleared before the code base can be packaged. Weinstein hunkers down for an all-night coding session, methodically closing issues one after another. By late evening—between 9:00 and 11:00 p.m.—he finishes the bulk of his assignments ahead of schedule, setting off relief across the team.
The milestone triggers informal celebrations among the exhausted staff. Engineers playfully chant Wayne’s World homage lines of “we're not worthy!” while congratulating their peers on performing the impossible under extreme time pressure. A single, stubborn bug remains before the 3:30 cutoff, but the overwhelming majority of critical blockers have been squashed down to minor, cosmetic defects. The team rallies around an engineering catchphrase coined by manager Michael Toy: “Zorros”—representing a practical zero-bug state where software is not technically flawless, but sufficiently polished and functional to ship to the public without catastrophic failure.
---
[18:28](https://www.youtube.com/watch?v=u404SLJj7ig&t=1108s) The Build Test and the PR Battle with Forrester
The development sprint moves to its ultimate practical test: verifying whether an outside developer, using clean hardware disconnected from internal development trees, can successfully compile Mozilla using the public build scripts. A spare monitor is hauled into a cubicle to simulate an external programmer's clean environment. An engineer notes that he expected the compilation room to look like a regimented, Soviet-style facility with hundreds of terminals in rows, to which another laughs that Netscape is nowhere near that organized.
```mermaid flowchart LR accTitle: External Mozilla Source Build Pipeline accDescr: Step-by-step compilation test proving external developers can compile Mozilla. A["Raw Source Code Archive"] --> B["Build Scripts Executed"] B --> C["Automated Module Compilation"] C --> D["Single Config Adjustment"] D --> E["Executable Mozilla Browser"] ```
The build scripts parse the modules and compile the source without major hitch, requiring only one minor configuration tweak. When the freshly compiled browser launches on screen, the engineers cheer, remarking that if an unassisted third party can get the browser to build on the first attempt, any software developer across the world will be able to do it.
While engineers celebrate the technical breakthrough, Netscape’s public relations team battles skepticism in the marketplace. Public relations representative Maggie Young dials industry research firm Forrester Research to brief key analysts Stan Dolberg and Eric Brown ahead of the release. The contrast with Netscape's history is stark: - During its historic initial public offering in August 1995, Netscape stock was priced at $28 per share and rocketed to $72 within minutes, setting a Wall Street benchmark as the most explosive IPO of its era. - Less than three years later, the public narrative has dramatically shifted from triumphant pioneer to struggling underdog.
On the analyst conference call, the reception is chilly and unconvinced. An analyst bluntly challenges the messaging, noting that the rationale sounds murky: “either I'm brain dead or it takes a lot of effort to communicate and so I'm concerned that while you all know what it means I'm I'm not confident that it's coming across to the press.” The PR team argues that releasing the code fundamentally alters the competitive landscape: “by opening up the source code we basically extend our developer community from those folks that are inside of Netscape to hundreds of thousands of developers outside of Netscape so you it's no longer Netscape versus Microsoft it's Netscape and all the Netscape you know virtual community.” Despite their insistence, tech analysts voice prevailing market skepticism that giving away the browser's crown jewels can halt Microsoft's relentless advance across the web ecosystem.
[22:24](https://www.youtube.com/watch?v=u404SLJj7ig&t=1344s) The Apple Patent Snag and Scott Collins' Replacement Code
With the source release deadline hanging over the team, the process appears deceptively tranquil until a critical legal roadblock emerges. Netscape discovers that Mozilla contains a small piece of proprietary code belonging to Apple that has not been approved for public release under their open-source license. As an engineer explains, “They just can't quite get themselves comfortable with the patent grant or with whatever we tried to do to fix it for them.” The response from Apple's legal counsel is blunt: “Gee, I don't know that we get enough protection.” Netscape staff attempt to escalate immediately; Marc Andreessen tries reaching Apple directly, leaving messages and remarking, “The problem is I can't get phone—there's no one at the Apple switchboard so I'm having a hard time getting phone numbers for people.”
```mermaid flowchart TD accTitle: Apple Code Escalation and Resolution accDescr: Sequence diagram showing how Netscape engineers resolved the unapproved Apple code block before release.
subgraph Problem["Licensing Barrier"] A["Apple legal refuses patent terms"] --> B["Unlicensed Apple code cannot ship"] end
subgraph ParallelTracks["Parallel Solutions"] B --> C["Marc Andreessen escalates to Apple"] B --> D["Scott Collins pulled in to write clean replacement class"] end
subgraph Resolution["Ship Authorization"] C --> E["Apple gives late permission"] D --> E E --> F["Source cleared for 10:00 AM release"] end ```
To prevent the entire release from derailing, engineer Scott Collins is summoned late into the night to code a clean-room replacement from scratch. Working exhaustively through the early morning, Collins views the task as a grueling final obstacle, stating, “It's my last bug. When I complete this bug I will be allowed to rest.” He works through the night:
> “So I stayed up until about 5:40 this morning writing this replacement class, cause it made my life a living hell. I got it basically running, it's all running, it's all really good, and thank heavens we got permission from Apple to ship the regular source.”
- Netscape faces an emergency because Apple has not authorized a proprietary component under Mozilla's public license. - Marc Andreessen scrambles late at night to locate executives via Apple's switchboard. - Scott Collins spends the night writing an alternative implementation, finishing at 5:40 AM just before word arrives that Apple has granted permission.
---
[24:07](https://www.youtube.com/watch?v=u404SLJj7ig&t=1447s) March 31 Deadline: Staging the Release
The morning of March 31, 1998, brings immense tension and organized media chaos across Netscape’s offices. Public relations prepares the team for a major media circus, arranging photo opportunities and notifying engineers that television crews will film the release. Inside the offices, developers joke nervously about the impending spectacle, suggesting management simply “hire actors to do this.” An engineer compares the brutal deadline culture to extreme survival motivation:
> “One way to learn to run a marathon is put a person out 26 miles into the desert and say, you know, that there's this bomb on your back that's going to go off in a certain length of time if you don't get into the town. Well, that'll motivate you to get in, but there's a certain chance that you'll be blown up.”
As the company conference call convenes to announce the availability of the Netscape Communicator 5.0 developer source code on mozilla.org, staff run back and forth between building wings and floors trying to locate target build archives. Software delivery at this intensity is described as pure pragmatism: “They don't have a theoretical framework to write software; they're just writing it. It's just like hitting the baseball: if their code gets a home run, nobody's asking questions... nobody cares why it works.”
At five minutes to ten, technical friction spikes when the machine directing the FTP transfer fails to respond to the push commands. After troubleshooting the directories and scripts, the files click into place across all major supported platforms: “Mac's there, Unix is there, Windows is there. We're done, we're done, it's up!” Jamie Zawinski walks into the packed press conference, deadpanning to the room that they had changed their minds:
> “Since Jamie is here, I'm told that means that we have now pushed the source out on the net, is that correct?” > “Actually, we decided not to. It was just a stupid idea.”
- Netscape formally announces the developer release of Communicator 5.0 source code on mozilla.org on March 31, 1998. - The release push encounters last-minute FTP server connection issues minutes before 10:00 AM. - Complete tarballs and binary files are verified simultaneously for Macintosh, Unix, and Windows platforms.
---
[27:25](https://www.youtube.com/watch?v=u404SLJj7ig&t=1645s) Pavlov and the Global Contributor Network
Following the initial release, the code is downloaded tens of thousands of times within hours, yet raw downloads offer no assurance that outside developers will submit meaningful fixes. Netscape relies heavily on a loose, worldwide coalition of volunteer hackers who contribute for the craft rather than pay. Among the most vital is a programmer known on IRC as “Pavlov” (Stuart Parmenter). A Netscape developer notes the immense reliance on his unpaid work: “He's Pavlov or Pav or Pav sleeping or Pav tired up too late, and without him I think we'd be, you know, months behind.”
The film cuts to rural Georgia to visit sixteen-year-old Stuart working in his home bedroom, dubbed “the cave.” His parents recall the surreal experience of software executives calling their household from major metropolitan areas, wanting to take their son to business lunches in Atlanta, entirely unaware that the engineer collaborating with them was a high school student:
> “It is flabbergasting to think that your child has done something for this worldwide company instead of his homework.”
Stuart reflects on diving into Netscape’s vast, tangled codebase to build the rendering subsystems: “I went and looked back at the older code, and I was really frightened by how incredibly messy and just awful the code looked. It would have taken you, you know, years to try and figure out what it was doing. So we basically did it from scratch. Pretty much I'm providing the code that makes the browser show everything faster and more efficiently than it used to.” His mother describes his total absorption at the terminal: “His keyboarding is almost just like talking... it's just totally unconscious almost, just a part of how he communicates.” Netscape leadership admits the entire business model is unproven, acknowledging that whether a corporation can survive by depending on outside volunteers to compete against an entrenched rival remains to be seen.
- Outside contributors communicate primarily through IRC and mailing lists under handles like “Pavlov.” - Stuart Parmenter rewrites core rendering code from his bedroom in rural Georgia at age sixteen. - Netscape veterans admit the original code base had become so convoluted that external volunteers chose to rewrite entire components from scratch.
---
[30:26](https://www.youtube.com/watch?v=u404SLJj7ig&t=1826s) Wall Street Skepticism and the Post-Release Grunt Work
While open-source advocates celebrate the ideological victory, Wall Street views the move through a colder lens. David Readerman, an investment analyst covering Netscape for a San Francisco investment bank, tracks the strategy for investors caught up in the internet stock boom. Readerman explains that stock prices are a referendum on concrete financial output:
> “The market is really kind of a voting machine. It's voting yes, I believe that vision statement; yes, I believe that's going to result in product sales; yes, that's going to drive earnings up, and you know, stocks should trade accordingly... Behind the vision and the slideware, there's a real, sustainable business model that can deliver earnings. And so I'm in a show-me mode for Netscape.”
For the engineering team inside the company, releasing the source brings no release from tension; instead, the workload multiplies. Developers realize they now must manage outside patch submissions, triage bugs, and keep shipping commercial products under the same relentless pace. One engineer laments, “Now my job will be three times as hard as it was yesterday, and was already ten times harder than it needed to be, right? Did I just work really hard to ship the company jewels out of the building and it's going to just end us dying and rolling in poison and misery?” The morning after the release, there is zero down time: “The day after the stuff goes out, you really don't get a letup. There is then this sort of day-in, day-out go to work, turn on the computer, code.”
- Wall Street analysts maintain a “show-me” stance regarding whether giving away browser source code can yield sustainable corporate earnings. - Engineers describe shipping the codebase as sending the “company jewels out of the building” without resolving internal survival pressures. - Rather than celebrating, developers immediately face an avalanche of new integration bugs and public code reviews.
---
[31:45](https://www.youtube.com/watch?v=u404SLJj7ig&t=1905s) The Human Toll of the Silicon Valley Treadmill
The grueling pace takes a visible physical and emotional toll on Netscape’s workforce. Tara Hernandez recounts a recent doctor visit: “My doctor said, interestingly enough, that I work too much, and that if I went to work today after my appointment, he would personally kill me.” Confronting the punishing tech culture, she shares her exit plan:
> “I have an agreement with myself that by the time I'm 35, I'm either going to be a high school teacher or a bartender, but something—anything other than a position in a high-tech industry. Otherwise, I'll probably die by the time I'm 40.”
Older engineers observe the unrelenting nature of Silicon Valley life, noting how easily one gets trapped on the treadmill where software demands force out family life, outside knowledge, and rest. Mike Toy recalls the steep personal cost during his tenure:
> “Christopher was born right after I started at Netscape, and I basically missed the first two years of his life because of the intensity. I'd work till about seven or 8:00, come home, eat dinner, put the kids to bed, and then go back to work or work from home until two or three in the morning. And I was like the dad zombie.”
His wife recalls waiting hours past promised arrival times as candles burned down, worrying he had run off the road, resigning herself to the fact that if a full day passed without contact, he was simply trapped at his desk. Seeking escape from the valley's monoculture, engineer Jim Roskind maintains a virtual commute from Michigan, returning only once every two weeks. He explains that leaving California was necessary to find genuine community, put roots down, and escape the crushing cycle, remarking on the cultural contrast between Silicon Valley and the Midwest: “There's quite a time change here. It's something like 12:01 in the morning, and there it's 1954.”
- Tara Hernandez resolves to leave technology by age thirty-five for teaching or bartending to avoid burning out completely. - Mike Toy recounts becoming a “dad zombie,” missing the first two years of his newborn son’s life due to sixteen-hour workdays. - Remote engineers like Jim Roskind commute from Michigan to distance their family lives from the exhausting Silicon Valley ecosystem.
[34:29](https://www.youtube.com/watch?v=u404SLJj7ig&t=2069s) Silicon Valley Churn, Life Sacrifices, and the Stock Option Lottery
Working in Silicon Valley tech culture stands in sharp contrast to traditional American employment. While older generations spent "30 years and out" at a single car factory, engineers in the Valley constantly jump from startup to startup, accumulating ten or more jobs across their resumes. One engineer reflects on how these moves often coincide with peak personal life upheaval, joking about telling a spouse, “Baby due in two months; I'm changing jobs now, dear.” For many, being in the center of the storm—where everything is constantly shifting, breaking, and rebuilding—is an addictive thrill they cannot imagine walking away from.
```mermaid flowchart LR accTitle: The Silicon Valley Startup Reward Cycle accDescr: Diagram illustrating how personal sacrifices and heavy hours feed into startup options, leading to either an acquisition windfall or worthless paper. subgraph Grind["Personal Investment"] A["60-80+ Hr Workweeks"] --> B["Sacrificed Personal Life<br/>(No kids, lost youth)"] end subgraph Equity["Financial Mechanism"] B --> C["Stock Options Granted<br/>(1-2 Years' Salary Equiv.)"] end subgraph Outcomes["The Startup Gamble"] C -->|"1 in 20 succeed"| D["Jackpot Windfall<br/>(64 millionaires/day)"] C -->|"19 in 20 fail"| E["Worthless Paper<br/>('Stupid Tax')"] end ```
Yet the intense pace exacts a severe toll on private life. Engineers confess to working grueling hours for the remote shot at financial independence while watching youth slip away childless, aware that once a portion of life is gone, it can never be retrieved. Across the nation, millions of workers write software in the fastest-growing and highest-paying mass sector in U.S. economic history. While elite athletes and movie stars earn fortunes, no industry employing millions has ever commanded such aggregate wages.
On Wall Street trading desks, tech tickers reflect the everyday obsession of Silicon Valley engineers and managers, where by one estimate sixty-four new millionaires are minted daily. Companies dangle options granting the right to purchase shares in the future at present prices—typically a grant equivalent to one or two years of salary. Early employees fortunate enough to cash out earn the moniker "Mosillionaires." But others view the entire framework with deep cynicism. Jamie Zawinski rejects the romanticization of tech compensation outright, arguing: “Stock options are a con; it's a carrot they dangle. It's like, ‘Oh, well, you know, if you give up your one and only youth, maybe someday you'll make money,’ right? It's—I've known so many people who gambled on the startup lottery and got nothing, you know? It's just like a lottery ticket; it's a stupid tax. I happen to win that particular lottery.”
- Millions of Americans make their living directly from writing software, making it the highest-paying mass industry in U.S. history. - An estimated 64 new millionaires are created every day in Silicon Valley during the late-1990s boom. - Typical startup option packages grant employees the equivalent of one to two years' salary in stock purchase rights. - Early Netscape employees who struck it rich on the company's initial public offering are known locally as "Mosillionaires."
---
[37:43](https://www.youtube.com/watch?v=u404SLJj7ig&t=2263s) The Collapse of Browser Revenue and Internal Mozilla Reorganization
Following Microsoft's aggressive push into the browser market, Netscape's stock enters a prolonged downward spiral, rendering employee options virtually worthless throughout 1998. The commercial core of the business has collapsed in real time. Eighteen months earlier, half of Netscape's revenue came from browser licensing sales; by late 1998, that revenue stream is down to zero. Even though Netscape builds web servers and enterprise software, the public and Wall Street regard it strictly as a browser company locked in a losing war against Microsoft. Observers openly question whether the company can endure, with analysts declaring, “I don't think that Netscape long-term can survive as an independent company.”
```mermaid flowchart TD accTitle: Netscape Revenue and Browser Division Crisis accDescr: Flowchart showing how Microsoft's free bundling wiped out Netscape's browser sales, leading to reorganization and source-tree dependency chaos. subgraph Crisis["Market Shock"] M["Microsoft bundles IE free into Windows"] --> R["Browser revenue drops from 50% to 0% in 18 months"] end subgraph OperationalStrain["Division Under Pressure"] R --> D["Browser division costs $30M/yr with near-zero return"] D --> Reorg["Reorganized twice in under 12 months"] end subgraph TechnicalDebt["Source Tree Friction"] Reorg --> S["Integrating outside Mozilla code"] S --> F["File collisions: Java & browser files colliding in identical directories"] end ```
The browser division—which burns nearly $30 million annually while generating practically nothing—is thrown into its second major corporate reorganization in less than twelve months. Inside engineering, opening up the codebase via Mozilla only compounds daily stress. Developers clash over incompatible directory structures, conflicting project build files, and Java components colliding in the same paths between the legacy Netscape tree and the new Mozilla source tree. Leadership attempts to reassure the ranks, acknowledging that nineteen out of twenty tech startups collapse, but newer hires never expected their seats at high-profile Netscape to evaporate in one to five years.
- Just 18 months prior, browser sales accounted for 50% of Netscape's total company revenues; by late 1998, browser sales generate 0%. - Operating the browser engineering division costs Netscape roughly $30 million per year. - The browser division is reorganized twice in under a single year as management scrambles to adjust to zero browser revenue.
---
[39:52](https://www.youtube.com/watch?v=u404SLJj7ig&t=2392s) Antitrust Allegations and the Dilution of Startup Culture
Throughout Silicon Valley, conversations center on Microsoft’s tactics. The prevailing belief across the tech community is that Microsoft used predatory, illegal methods rather than superior engineering to strip market share from Netscape. In a culture rooted in meritocracy and egalitarian competition, the realization that market dominance was won outside the boundaries of pure code deeply infuriates engineers. These grievances culminate in the U.S. Department of Justice filing formal antitrust charges against Microsoft for anti-competitive and exclusionary practices aimed at preserving its desktop operating system monopoly and extending it into internet software.
Even setting aside Microsoft's assault, Netscape has become a victim of its own ballooning headcount and an increasingly tangled, brittle codebase. It struggles to retain the agility and fire of its early startup days. As software companies scale up, their underlying nature shifts from restless invention to process-driven revenue extraction. Big companies treat technological breakthroughs as unacceptably risky bets, opting instead to wait for small ventures to take the initial risks before buying them out and wringing profits from their work.
- The U.S. Department of Justice formally charges Microsoft with anti-competitive and exclusionary practices to protect its Windows OS monopoly and capture the browser market. - Netscape suffers from internal bloat, code complexity, and shifting corporate priorities that choke off the vitality of its initial startup culture.
---
[41:24](https://www.youtube.com/watch?v=u404SLJj7ig&t=2484s) The AOL Acquisition: Cynicism, Soul-Searching, and the Open-Source Future
CEO Jim Barksdale abruptly moves up Netscape's all-hands meeting by a week, summoning the entire workforce to the Flint Center immediately after announcing quarterly financial numbers. Standing before an anxious auditorium, Barksdale reveals that as of 1:30 that morning, Netscape concluded negotiations and agreed to be acquired by Steve Case’s America Online (AOL), based in Dulles, Virginia. For many engineers, the announcement is a gut punch. Only months earlier, Netscape developers routinely mocked AOL's proprietary online service as training wheels for tech illiterates—deriding it with jokes like “Congratulations, Skippy, you've got mail!” Valley insiders widely sneered at Steve Case as a mere "soap salesman" because of his background at Procter & Gamble, only to find themselves bought out by that very salesman.
```mermaid flowchart TD accTitle: Aftermath of the AOL Acquisition accDescr: Breakdown of reactions and structural consequences following the buyout of Netscape by AOL. A["1:30 AM Agreement:<br/>AOL acquires Netscape"] --> B["Employee Reactions"] A --> C["Strategic Guarantees"]
B --> B1["Culture Shock:<br/>'Soap salesman' bought the pioneers"] B --> B2["Departures:<br/>Veterans cash out or reject corporate marketing focus"] B --> B3["Retention Strain:<br/>AOL corporate rules vs. Netscape ways"]
C --> C1["Mozilla.org Safety:<br/>Public license prevents code clawback"] C --> C2["Steve Case Reassurance:<br/>Explicit email support for open source"] ```
National press coverage immediately questions whether Netscape “lived fast, died young, and left a tired corpse,” speculating whether AOL can retain any of Netscape's critical technical talent. The deal delivers a substantial financial windfall for shareholders and allows vested employees to finally cash out, leading many to plan their immediate exits rather than submit to the "AOL way." Others choose to leave because Netscape’s trajectory has shifted from cutting-edge technical craftsmanship toward marketing, portal traffic, and ad delivery.
Yet within the open-source community, the acquisition sparks fears that AOL will dismantle Mozilla. Jamie Zawinski posts a worst-case scenario analysis to mozilla.org, reassuring developers that because the source code was already released to the public under an open license, it irrevocably belongs to the community and cannot be locked away by corporate parents. A few days later, Steve Case emails Zawinski directly to endorse the Mozilla project, promising that AOL views open source as a fundamental asset of the acquisition and intends to let it thrive. Reflecting on the chaos and his pending exit from the company, Zawinski shrugs off the upheaval as the inevitable tax of startup life: “AOL's focus and Netscape's growing focus has been marketing and advertising and all that stuff, and that's not nearly as interesting to someone who's sort of a techno-fetishist. You know, I'm switching jobs, I'm selling my house, I'm moving, switching towns. That's life for startup land.”
- The merger agreement between Netscape Communications and America Online (AOL) concludes at 1:30 AM prior to the emergency Flint Center all-hands meeting. - AOL CEO Steve Case personally emails Jamie Zawinski to confirm that AOL supports mozilla.org and intends to maintain Netscape's open-source commitments. - The acquisition triggers executive and engineering turnover as staff reject AOL's corporate culture and marketing-driven portal priorities in favor of new startup ventures.
[45:02](https://www.youtube.com/watch?v=u404SLJj7ig&t=2702s) Departures: Tara Hernandez and Jamie Zawinski
A farewell gathering is held for Tara Hernandez, celebrating her trajectory from engineer to management. A colleague recalls how Tara approached him a year and a half prior, saying she wanted to manage so badly she could taste it, only to confess a week into the role, “Why did you ever let me do this?” Despite the initial shock, she proved herself to be one of the company's finest, earning a toast as Netscape’s release team manager. Tara leaves Netscape to join an e-commerce startup, walking away from a surge in the value of her Netscape stock options in the hope of securing an even larger payout at the new venture.
Jamie Zawinski also decides to walk away, voicing deep disillusionment over the AOL acquisition. He observes that regardless of how AOL chooses to direct the business, the authentic Netscape is gone: “It’s not Netscape anymore, that part’s over, and you know, that’s really sad. I wish Netscape could have gone it on their own.” Frustrated by what he sees as an absence of genuine commitment to open-source development, Zawinski resigns from Netscape exactly one year after the day he helped release Mozilla source code to the public. Reflecting on the romanticized depiction of programming culture, he quips about the film *Hackers*, observing that while he wishes software life involved roller-skating in spandex and battling villains, real engineering is simply sitting inside an office typing all day.
[46:28](https://www.youtube.com/watch?v=u404SLJj7ig&t=2788s) Counting the Cost: Jim Roskind and Michael Toy
Jim Roskind walks through a serene residential neighborhood, describing it as an essential escape from the high-stress jungle of the tech industry after living out west for four or five years. Following his promotion to Netscape’s highest engineering rank, Roskind reflects on the compulsive drive behind late-night programming sprints. After staying at the office until 4:00 AM on a non-deadline evening, he describes software development as an adrenaline rush and an addiction where engineers relentlessly chase perfection, pushed ever harder by immediate feedback loops.
Meanwhile, Michael Toy works on building an outdoor wooden playhouse with a planned front porch and flowers. Looking back on the gold-rush mentality of the dot-com era, Toy admits he went to Netscape because its core purpose was to cash in on the internet and get rich, but confesses the lifestyle exacted a severe toll on his personal life. His wife notes that Michael eventually hit a wall of total burnout where the cost simply grew too high. Toy offers a direct warning to those enticed by easy money: “If people would look at this and say, ‘Oh hey, this is a cool thing, I’m going to start a startup and get rich quick,’ you know, I would just have to say you need to count the cost, because you can’t ever retrieve the time that’s lost.” Having achieved financial independence as Netscape employee number six, Toy retires shortly after Mozilla’s public release.
[48:29](https://www.youtube.com/watch?v=u404SLJj7ig&t=2909s) Silicon Valley Churn and the AOL Windfall
In the culture of Silicon Valley, remaining at a single company for more than three years prompts peers to wonder what is wrong with you or why you cannot find another post. Programmers typically change jobs every two years, behaving much like worker ants dispatched toward an objective: as the unit marches toward its goal, ants continually drop out while new ones enlist, until an entirely different group completes the mission. Scott Collins, continuing his commute between Michigan and Netscape, reflects on this transient landscape alongside the sheer financial frenzy surrounding the company.
```mermaid flowchart LR accTitle: Netscape Acquisition Valuation Surge accDescr: Growth of Netscape's valuation from the initial merger announcement to deal completion. A["Merger Announcement<br/>($4.2 Billion Valuation)"] -->|"Stock Appreciation<br/>(Value more than doubles)"| B["Merger Closes (Spring 1999)<br/>($10 Billion Valuation)"] B --> C["$5B - $6B in New Wealth Created"] B --> D["Jim Barksdale Swaps Shares<br/>(>$500 Million AOL Stock)"] ```
When the merger deal with AOL closes in the spring of 1999, Netscape's stock value has more than doubled from the initial announcement. As Collins points out, with shares leaping from $20 to around $172, “It’s hard to be depressed about the amount of work you have to do when every other cube holds a millionaire.” A financial analyst notes that Netscape hitched its fortunes to AOL with exquisite timing, seeing an implied valuation of roughly $4.2 billion swell to $10 billion by completion, creating $5 to $6 billion in fresh net worth. While other executives sold shares during the final year, CEO Jim Barksdale purchased more, ultimately swapping his stake for upwards of half a billion dollars in AOL stock.
[50:38](https://www.youtube.com/watch?v=u404SLJj7ig&t=3038s) Fresh Blood: Stuart Parmenter (Pavlov) Arrives
Even as veterans depart, new hopefuls head west to Silicon Valley to seek their fortunes. Stuart Parmenter (known online as "Pavlov") arrives with his father from 4,000 miles away for an engineering interview at Netscape. His father acknowledges the emotional distance but observes that Silicon Valley offers an environment where his son's distinct talents fit right in, surrounding him with people he can truly relate to. During the technical discussion, Stuart states his primary objective plainly: he wants to optimize the Unix build until it runs faster than the Windows version. Netscape hires Stuart, who chooses to postpone college to work directly on the codebase, participating in what investors herald as the single greatest legal accumulation of wealth in human history.
[51:57](https://www.youtube.com/watch?v=u404SLJj7ig&t=3117s) The Changing Landscape and the Sorcerer’s Apprentice
Investment banker David Ruderman inspects a newly constructed data center packed with dense bundles of cable and optical fiber, establishing the core trading and communications infrastructure for a major merchant bank. Ruderman operates on the conviction that the internet will reshape every aspect of commerce, positioning his firm to finance the enterprises driving that transformation. Standing on a street corner, he points out a physical bank branch and a Gap store undergoing renovation, questioning why companies invest in brick-and-mortar storefronts when commerce is inexorably shifting online.
Veteran engineers reflect on the breathtaking pace of this revolution. In the early days, HTML and the World Wide Web were completely unknown to the general public; suddenly, point-and-click software placed the full power of the internet into everyone's hands. One engineer compares the emergence of the web to *Fantasia*, where Mickey Mouse reads the sorcerer's open spellbook atop the mountain and unleashes forces he cannot comprehend or control: > “We’re at the beginning of an industry, and who knows where that industry is going to go. This could all turn into television again. It could be controlled by a small number of companies who decide what we see and hear, and there’s a lot of precedent for that.”
The engineer notes that while he is laying down railroad tracks as speeding trains roar past, it would be a tragic legacy if the true outcome of Netscape and the internet revolution was merely forcing human beings to perform under crushing pressure at ever more exhausting speeds. He points out that Netscape was born, peaked, and overtaken within a brief four-year span.
[54:34](https://www.youtube.com/watch?v=u404SLJj7ig&t=3274s) Epilogue: The Millennium Closes
By late 1999, the open-source community and the broader public are still waiting for Netscape’s first browser based on the Mozilla source code, more than a year and a half after the original release of the recipe. Concurrently, landmark events reshape the technology sector:
- In the Department of Justice’s antitrust trial, the presiding federal judge determines that Microsoft operates as an unlawful monopoly that stifles industry innovation. - AOL prepares to enter the new millennium by orchestrating an even larger corporate acquisition. - Wall Street investors funnel unprecedented capital into tech equities, driving trading to heights of extreme volatility.
As internet connectivity embeds itself across the globe, legions of software engineers continue working late into the night, racing against time to write the code that will power the digital world.
## Notable quotes > [48:29](https://www.youtube.com/watch?v=u404SLJj7ig&t=2909s) It’s hard to be depressed about the amount of work you have to do when every other cube holds a millionaire. — Scott Collins
## Mentioned Netscape Communications, Netscape Communicator, Netscape Navigator, Mozilla, mozilla.org, Microsoft, Internet Explorer, Windows, Apple, Sun Microsystems, America Online (AOL), Forrester Research, United States Senate Judiciary Committee, U.S. Department of Justice, Michael Toy, Jim Roskind, Jamie Zawinski, Tara Hernandez, Scott Collins, Jeff Weinstein, Jim Barksdale, Bill Gates, Marc Andreessen, Maggie Young, Stan Dolberg, Eric Brown, Stuart Parmenter, David Readerman, Steve Case, David Ruderman, Procter & Gamble, Flint Center
## Video description Code Rush, produced in 2000 and broadcast on PBS, is an inside look at living and working in Silicon Valley at the height of the dot-com era. The film follows a group of Netscape engineers as they pursue at that time a revolutionary venture to save their company - giving away the software recipe for Netscape's browser in exchange for integrating improvements created by outside software developers. The copyright to the film is now available under Creative common licence vers. 3 for interested viewers to download and use. In the future the original footage from which this film was made will be accessible under the same terms.
Please visit : www.clickmovement.org/coderush
[Source](https://www.youtube.com/watch?v=u404SLJj7ig)