Well, I've got some not so positive feedback for your list... See
comments in-line.
Herman Knief
On Tue, 8 Aug 2000, Jack Barnett wrote:
->>> Talking Points: Features and benefits that everyone in the Linux
->>> community agrees to and presents to the newbie population in unison.
->>>
->>> Top Ten Talking Points In Linux
->>>
->>> After all the responses, I like the following:
->>>
->>> (Talking Point List Version 0.02)
->>> 1. Linux is stable ---- does not need to reboot to refresh itself, a
->>> production system rarely crashes
Not true. I run one of the largest public web sites in the world, using
Linux as a front end (I think we are second to Google.) We have a LOT of
problems with systems crashing, but generally under very high loads.
->>> 2. Freedom / Here to stay ---- Due to Open Source users and vendors are
->>> sure of the staying power of the OS. (Will not go out of business -
->>> thus not be supported)
Freedom yes, but try getting REAL support for kernel problems. I happen
to know Linus personally and have dealt directly with Alan Cox on some of
our issues, and still have problems getting fixes.
->>> 3. Flexible ---- Could be a workstation, webserver, firewall, router,
->>> ftp server, proxy server, email server, file server, backup server, and
->>> more right out of the box.
->>> 4. Scalable ---- True 32 bit preemptive multitasking, multi-user. -
->>> can run in multi-processor machines. Clustering capability.
Scalable within limits... Linux's scheduler and thread model are pretty
immature.
->>> 5. Streamlined ---- Can use Linux in older systems without major
->>> performance problems. Can use in embedded applications.
Depends on your applications.
->>> 6. Secure ---- A properly updated system is very secure. Linux does not
->>> consider allowing external inputs of unknown origin.
Is this one a joke? If you want secure, look at OpenBSD!
->>> 7. Bug Detection ---- With Linux, claims of software fixes are
->>> *independantly verifiable*. many people are looking at code allowing
->>> for faster fixes.
Yeah right... it depends on the fix and how easy it is to identify and
incorporate.
->>> 8. Corporate Backing ---- Increasing numbers of public companies are
->>> supporting and develop Linux services and products.
Corporate backing is one thing, but getting actual development cycles to
get things fixed is a complete waste of time.
->>> 9. Roaming Users Easy to implement ---- No cumbersome policy
->>> replication.
->>> 10. New functionality ---- Programming may cost someone time or money,
->>> but is then included in the 'collective' source code, for all to
->>> benefit. The original programmer does not have to recode functinality
->>> into new releases.
->>>
->>>
->>> I took the virus references out... as they are too vague
->>> They all still need to be condensed and become more precise, this still
->>> needs serious work and/or needs to be re-arranged.
->>>
->>> Thanks to all of the responses last time (my apologies if I missed you
->>> :):
->>>
->>> Arjen Runsink