Matt Mullenweg Quotes

It doesn't matter if it's a wireless or wired network. I think network management can be introduced that is equally sensible.

I am instinctively a network infrastructure plumber.

Any time you build a network, you have to help users find their friends.

I had so much fun in early days learning about networking, security, scalability and other geeky stuff.

I'm not an economist; I'm a hacker who has spent his career exploring and repairing large networks.

I also administer the Internet Assigned Names Authority, which is the central coordinator for the Internet address space, domain names and Internet protocol conventions essential to the use and operation of the Internet.

Nobody should have to be a systems integrator to make a convergence network work in their home.

One of my bosses happened to be one of the early architects of some of the ways Internet providers work. He taught me how the cables connect, how the telecom providers work... I learned how to make my own Ethernet cables, all the way up to running a small business.

The big deal about the Internet design was you could have an arbitrary large number of networks so that they would all work together.

The Internet was developed in large part by U.S. government research funding to develop new communications networks, starting with a network created by the Department of Defense.

The last thing I would ever do is try to become a network programmer.

Choosing a single most important development is incredibly hard to do because a lot of different things had to happen before the Internet could be deployed in the fashion it is today.

I started in time-sharing and networking with packet switching, which was the precursor to what became the Internet. Time-shared use on packet-switch networks, when you think about it, is the cloud.

The Internet is literally a network of networks.

So as I look at transitioning to the communication platforms of the future, I see that the beauty of Internet protocols is you get the separation of the layers between service and technology.

The ARPAnet was the first transcontinental, high-speed computer network.

The next Internet could be in the making somewhere in someone's lab.

The first commercial routers came out about 1986, and services came in 1987.

Unlike the phone system, which is engineered around an application, the Internet layered model allows you to, in essence, separate applications from infrastructure.

It's incredibly hard to program a network from scratch for 24 hours.

The Internet is a computing platform built on top of core technology. Applied technology is what gets built on top of that: It's Web services.

Companies that are hosting Web sites or do a lot of teleconferencing need a lot of bandwidth going both ways.

FreeBSD has a nicely tuned network stack and extremely good reliability.

I'm a big believer in using the best IP for a given application.

In the earliest days, this was a project I worked on with great passion because I wanted to solve the Defense Department's problem: it did not want proprietary networking and it didn't want to be confined to a single network technology.