Fifteen years ago, few people other than programmers had ever heard of "beta" software. Then came the Web, and with it the hype of the dot-bomb bubble. "Beta" quickly became a buzzword as non-professionals slowly started reading what industry people wrote and mixed with them in forums and newsgroups where all had a common interest, such as rec.aviation.piloting, alt.usage.english, even alt.swedish.chef.bork.bork.bork.
Getting access to a beta program in 1996 generally required either knowing someone at a software company or stumbling across an announcement of an upcoming version, registering, providing information on your technical background and explaining why you should be allowed to participate. If you got in, you were pummeled with warnings about the software being unfinished and buggy, that it was definitely Not Ready for Prime Time, and that you shouldn't install it on any machine you weren't prepared to rebuild completely.
x-posted to da brog, sans poll.
There are a few benefits to consolidating all your servers in a couple locations rather than having them spread out all over the world in each major center. Administration is centralised and only a couple people have to spend their days babysitting them. Patching is centralised. And... that's about it. A short list of consolidation suckage:
- Loss of power kills all centers
- Loss of communications kills all centers
- Inability to work with the base hardware
- Bureaucracy
- Admin ego
x-posted to da brog, sans poll.


