Web Server Quotes & Sayings

Once you understand that everybody's going to get connected, a lot of things follow from that. If everybody gets the Internet, they end up with a browser, so they look at web pages - but they can also leave comments, create web pages. They can even host their own server! So not only is everybody consuming, they can also produce. — Marc Andreessen

Today, Web services is really about developing for the server. What it means to developers is any set of systems services that you make a Web service you to access by any kind of device with a highly interactive client, not just a browser. — John Fowler

Ben, those silver bullets that you and Mike are looking for are fine and good, but our Web server is five times slower. There is no silver bullet that's going to fix that. No, we are going to have to use a lot of lead bullets." Oh snap. — Ben Horowitz

Web GIS allows us to take our systems of record - our traditional server and desktop technologies - and integrate them, bringing them together into a system of systems. — Jack Dangermond

Web projects aren't done until I'm happy, or someone changes the password to the server. A formal release does not stop me from working on it more. — Chris Milk

If you use a proprietary program or somebody else's web server, you're defenceless. You're putty in the hands of whoever developed that software. — Richard Stallman

The Domain Name Server (DNS) is the Achilles heel of the Web. The important thing is that it's managed responsibly. — Tim Berners-Lee

A zero-day exploit is a method of hacking a system. It's sort of a vulnerability that has an exploit written for it, sort of a key and a lock that go together to a given software package. It could be an internet web server. It could be Microsoft Office. It could be Adobe Reader or it could be Facebook. — Edward Snowden

The silicon microchips themselves might be cheap (relative to times past, anyway), but CPU cycles are not cheap. Every CPU cycle consumes clock time. Clock time is latency. A wasteful application makes its users wait longer than they need to, and if there's anything users hate, it's waiting. For web systems, latency in the application has a dual effect. The added processing directly increases the burden on the application servers themselves. Suppose that an application takes just 250 milliseconds of extra processing per transaction. If the system processes a million transactions a day, that extra 250 milliseconds per transaction makes for an extra 69.4 hours of compute time every day. Assuming an 80% load factor on each server, you'll need four additional servers to handle this load. — Michael T. Nygard