Threads is a library designed to make threading under C++ simpler. It provides a "pthread" class, with an abstract method called "thread". It also provides classes for mutual exclusion of parallel processes and condition signalling, and a semaphore class that comes in handy when synchronizing constructor and threaded method. The aim of the threads library is to provide a simple, yet powerful means of threading applcations, and to provide shared memory and process scoping to C++ programs.
Old, rusty machines
I think your very basis here, at quoting CP/M is wrong in all its forms. First of all, if you recall ... when CP/M was about, was at the era when computers were becoming popular as personal computers. The commodore pet, later the cbm became famous and the favorite, before ms dos ever came into the market place. What did commocore have? A basic interpreter, a very simple interface and commands that any user could acquaint him/herself with. The same applied to IBM PC as it came onto the market, it had a basic interpreter built in and users could use it to do simple things without having to learn a lot of hanky panky and god knows what. The same story, applied to the Macintosh when it came out.
And MS-WORD ... it simply killed it's competition, which was mostly the older CP/M originated word perfect. Why? because word perfect was hard to use, hard to get complete control of ... while Word was simple, and easy. In these days, *this* was the key... power combined with ease of use.
Today however, you can't say that about Windows, or Office. Open Office and KOffice are products that give the ease of use, you originally got from MS Word. And Linux is fastly becoming an operating system, that is easy and simple to use as well. While Office and Windows become overly bloated, and highly unstable. Something, if anyone cares to remember, was a thing of CP/M.
Nobody cared, in the old days, no matter how functionally complete Unix was... to spend a lot of time a day, to find out something about a simple error... do a lot of C programming, to make a simple calculation or remember tons of command parameters to start a word processor, which accidentally wasn't available and was one of the key items that that handicapped Unix. Guru meditation, was for amiga users ... and bomb shells was for Atari and Mac users. And although a graphical user interface was created for the Commodore 64 (yes, indeed) ... those programs were not in every computer store shelf, at $9.99 a pieace. But only found in the small print of a computer enthusiasts magazine, and then at the price of $99.99. Which makes a world of a difference, especially at a time when the hype around computers has convinced everyone that Megaherz and Megabytes rule.
Today, who can afford to buy Windows? It's expensive, you might even say that today Windows fills the same role as IBM or Dec, Mainframe O/S'd did. You couldn't buy these OS's, you had lease them at outrageous prices. ... and later, Sun's and other medium sized operating systems. Of course, every person in the office knows Word and Windows. Just like, 15 years ago, every person in the office knew CP/M and Word perfect... and it's only the winner that goes home with the price. Trying to emulate Windows and Office, every hour on the hour, only gives you second place ... as a meager copy, that will never be as good as the original... never do things as accurately as the original, no matter how good the programming team is.
Let's put it differently ... does anyone here, even consider that MS-DOS would have become as popular as it is, if it had tried to be a complete look alike, to CP/M? or does anyone consider that Word would have become so popular, if it had tried to be exactly like Word perfect?
Noble, but hardly practical...
I think most companies are rather into the line that
they do not want the customer to even think, that
any failure in services, is on the service providers end
of the line.
Gone are the days of unix admins, gurus that had all
the answers... had a problem, you went to the
sysadmin and his fingers jumped over the keyboard
and acradagabra... solved.
Today, its a virus... the phone lines are shut, it was a
gigantic volcanic eruption, or the user simply failed to
take the course of how to use the system properly.
Or the user, is a nasty kid who is abusing the
Current system administrators don't solve problems,
they wait for the next service pack from Microsoft...
or the next version of AntiVirus kit. If something
goes wrong, its you who are making things wrong...
because neither the company, nor the administrator
can afford to allow the word to spread out, that there
is something wrong that is wrong because of their
lack of doing things, one way or the other... it would
make them seem less professional...