Juan David Campolargo

Mosaic: Marc Andreessen & Eric Bina

I’ve never met Marc Andreessen or Eric Bina, though I tried more than once.

With Marc, I talked to his assistant and even invited him to The UIUC Talkshow.

With Eric, I heard he still lived around campus, and I wanted to talk to him, but never could.

So I don’t have much to say about either of them, other than a few cautionary tales from their time on campus that I think you can learn from.

A Brief Cautionary Tale

Eric and Marc created Mosaic, one of the first web browsers that could actually show images and text together in the same window. Before that, the internet was basically all text. Mosaic made the web visual, clickable, and easy enough for regular people to use, which is why it kicked off the modern internet.

After graduation, Marc moved west and co-founded a new company with Jim Clark. They reportedly rewrote the code from scratch, but kept the word “Mosaic” in the company name.

According to Andreessen’s account, the university didn’t sue them directly. Instead, it contacted prospective customers to assert trademark and intellectual property concerns, which slowed deals and introduced legal uncertainty.

The result was a settlement, a name change, and a masterclass in how quickly institutional bureaucracy can turn your rocket ship into paperwork.

Netscape was born. The university received a settlement and, by Andreessen’s own later account, lost a lot of goodwill.

Be Careful With The University (and win anyway)

If you build something on campus that catches fire, the institution will show up with a clipboard.

That’s not cynicism; that’s pattern recognition. Protect yourself early:

  • Names before fame. Don’t ship or pitch under a name the university (or anyone else) can plausibly claim. Do the boring thing: check USPTO for trademarks, do basic clearance, and register early. Changing names mid-takeoff is a tax on your momentum.
  • Know who owns what. Read what you signed—student IP policy, RA contracts, lab agreements. If grant money or lab space touched your project, the rules change. Get a lawyer to map this out before you talk to investors.
    • Read the Student Ownership Manual (here or here and here and here) and know exactly what you need to do.
  • Start clean. If you are leaving a lab, start a brand-new repo on a brand-new machine. No lab laptops, no shared drives, no reused code. Keep a documented timeline and save receipts.
  • Separate resources. Don’t build your company on school servers, emails, or credits tied to your .edu. If you start there, move it off quickly.
  • Talk to the TTO (Technology Transfer Office) on your terms. They can be helpful… or not. Go in with a plan, know what you’ll give (non-exclusive license, attribution) and what you won’t (control of your company).
  • Document your origin story. Keep a founder diary: when you conceived the new product, when you wrote the first non-lab line, who contributed, on what hardware. It is boring now and invaluable later if ownership is questioned.

Do these things and you’ll spend your energy actually building valuable things in the world, not wasting time explaining yourself to people whose incentives are not the same as yours.

Midwest Engineers Run The Valley

The quiet Midwest tinkerer is one of the most powerful archetypes in tech.

It is the person who would rather spend a Saturday fixing something than talking about it. Someone who ships from a Champaign apartment the same way others ship from an office on Sand Hill Road.

One lesson from Mosaic is that the “Midwest engineer” archetype is real. The path from Mosaic to Netscape helped accelerate the modern web. Years later, the same pattern appears in the PayPal network and beyond. People who tinker first, talk second, and do not wait for the right zip code to start building.

That pattern existed earlier too. Robert Noyce, who grew up in Iowa, helped found Intel a generation before Silicon Valley became a brand. The horizon really can be wide without being coastal. You do not need a Bay Area address to build a Bay Area class company.

That’s the story I carry from Marc and Eric: build boldly, lawyer early, and don’t let a campus badge convince you the world stops at Green Street.

What Happened to Eric Bina? (aka: The Quiet-Builder Path You Can Choose)

We all know Marc. But what about Eric? Did he ever leave Champaign? Why didn’t he move to the Bay right away? And why don’t we hear his name every five minutes?

I did a lot of digging, and finally, here’s the story (if there are mistakes, let me know).

So… what happened right after Mosaic blew up?

In 1993, Mosaic took off at the National Center for Supercomputing Applications at UIUC. Its two primary authors, Andreessen and Bina, initially went their separate ways.

Marc graduated that December and moved to Silicon Valley. Eric did not. He was eight years older, a full-time NCSA staff programmer, and an Illinois native. At that point, Mosaic remained under NCSA’s control. University administrators were still considering how to manage and commercialize the software, which later included licensing it to Spyglass. Bina stayed in Champaign-Urbana and continued his work at NCSA rather than immediately following Andreessen west.

Did he ever move to Silicon Valley?

Jim Clark, a Silicon Valley veteran, was looking for his next idea. He started asking around who was doing interesting work in tech. Marc Andreessen’s name kept coming up. Clark found a way to get in touch, reached out, and suggested they meet. They did, got along, and decided to start a company together. That company would later become Netscape.

In April 1994, Andreessen and Clark flew to Illinois to recruit Eric Bina and several other NCSA colleagues to join the new startup, which was initially called Mosaic Communications. Faced with a concrete opportunity, Bina accepted. Along with Rob McCool, Aleks Totić, Chris Houck, and John Mittelhauser, he walked into NCSA the next day and resigned. Soon after, he packed up and headed to Silicon Valley.

Bina did leave central Illinois, just on his own terms and timing. He moved to California and became a co-founder of the new company, soon renamed Netscape Communications after NCSA objected to the use of “Mosaic.”

Later that year, Netscape released the first version of Netscape Navigator, with Bina serving as one of its principal engineers. His move west came only a few months after Andreessen’s initial departure.

Then why don’t we hear about him like we hear about Marc?

By many accounts, Bina was a “quiet, intense” programmer who wasn’t dreaming of Silicon Valley riches.

Different archetype.

Marc is the evangelist, the “let’s remake the world” voice.

Eric is the quiet and intense coder who loves the technical challenge more than the spotlight. He’s said flat-out that Marc was the driving force for changing the world, and that on his own he wasn’t trying to change anything beyond his own situation.

This telling observation from a 1995 Newsweek profile captures their dynamic: Andreessen was enthralled by the idea of changing the world through a web browser, whereas Bina was more interested in the browser’s practical uses and technical challenges, not the hype.

Bina himself has downplayed any world-changing aspirations.

In a rare interview, he praised Andreessen’s drive and admitted “Marc is much more responsible than me for the way things happened. Marc is a strong driving force for changing the world… We were friends and worked together, but on my own I don’t feel driven to change anything but my own situation.”

Bina did not share a crusading entrepreneurial mindset. He liked building software and solving technical problems. He has also pointed out that Tim Berners-Lee and other early browser developers deserved more credit, and that if Mosaic had not succeeded, similar software would likely have emerged from someone else.

Did he stay in the Valley forever?

Eric did not make a long career of climbing the Silicon Valley ladder. He contributed immensely to Mosaic and Netscape’s early success, he didn’t stick around in the industry trying to replicate that success ad infinitum.

In the late 1990s, as Netscape navigated the browser wars and was eventually acquired by AOL, Bina kept a low profile. Ultimately, he decided to leave tech altogether and moved back to Illinois.

With the riches from Netscape, Bina stepped away from programming professionally and pursued personal hobbies. “I obsess over fruit trees,” he told Popular Mechanics from his Illinois home, noting he’d cultivated eleven types of pawpaw trees from seed.

So what’s the lesson here?

You don’t have to be the marquee name to have an outsized impact. You can be the quiet builder. You can make your money, go home and live exactly how you want.

In Bina’s case, that meant a self-directed life far from Silicon Valley after his work there was done.

Meanwhile, Andreessen continued building companies and later co-founded a major venture capital firm.

Learn more

  • Avoid getting steamrolled by the university:
    • Read the Student Ownership Manual (here or here and here and here) and know exactly what you need to do.

Intellectual property created by a student in the course of typical classwork is likely owned by the student as long as the student was only using University resources that are usually and customarily provided. Examples of resources customarily provided to students are office space, dorm rooms, library facilities, and ordinary access to computers and networks.

However, when a student creates intellectual property using University facilities, equipment or funds, then standard University ownership rules apply. For example, when a graduate student conducts research in a faculty lab, then it is likely that the University owns any resulting intellectual property. The Office of Technology Management can help you determine ownership.

—Office of Technology Management, A Student’s Guide to Intellectual Property Ownership at the University of Illinois at Urbana-Champaign

Yikes!

Front cover for The Jailbroken Guide to the University
Use the appendixThe back of the book is part of the book.

The appendix keeps the examples, guides, profiles, and source trails close. The book gives them sequence, context, and a way to turn curiosity into action.