Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
Intel

The Big Technical Mistakes of History 244

An anonymous reader tips a PC Authority review of some of the biggest technical goofs of all time. "As any computer programmer will tell you, some of the most confusing and complex issues can stem from the simplest of errors. This article looking back at history's big technical mistakes includes some interesting trivia, such as NASA's failure to convert measurements to metric, resulting in the Mars Climate Orbiter being torn apart by the Martian atmosphere. Then there is the infamous Intel Pentium floating point fiasco, which cost the company $450m in direct costs, a battering on the world's stock exchanges, and a huge black mark on its reputation. Also on the list is Iridium, the global satellite phone network that promised to make phones work anywhere on the planet, but required 77 satellites to be launched into space."

Comment Re:Real answers... (Score 1) 502

Heh, yes, right on. More to those questions, then! As for me, I haven't worked in a library with thin client solutions; but I have worked in a library with stand-alone Win9x and hated it, and I have managed a large company site with Citrix thin clients and loved it.

I'd echo wcdw's upsides & downsides and add some comments:

Your thin client solution can be a real strength if you have a strong administrator. If s/he knows the system and how to tweak it, it can be secure from user meddling and strong enough to support a lot of clients from one server (60-70). But a newbie or unavailable thin client administrator may think that the job is easy (because it's quick to install the server and connect a few clients), but will be a detriment for the longhaul. Consider this in your planning: people cost a lot more than computers, espeically over time.

For your situation, a Windows 2003 Terminal Server would be quite reasonable. The Citrix tools would add a lot of security and monitoring tools as well as the ability to use DOS or Linux clients if you wanted to save a tiny bit on the client PCs, but for a small implementation (less than a few hundred) it's really not necessary.

The Terminal Server environment is flexible to lock down, configure exactly how you want it to appear, and upgrade or make changes; especially in a case like this, where everyone gets the same settings and you're closed at night so the admin can do upgrades as necessary. Yes, it's a downer that one problem is multiplied to everyone logged in; but at the same time, the solution takes effect immediately for everyone as well.

Anyway, that's enough rambling from me...

Slashdot Top Deals

Money is truthful. If a man speaks of his honor, make him pay cash. -- Lazarus Long

Working...