worms worms worms

[Collins Richey]

On Sat, 16 Aug 2003 19:42:26 -0500
Alma J Wetzker <almaw at ieee.org> wrote:

[ other stuff snipped - see the thread for details ]


> >The essential situation is this.  Using M$ products is a recipe for
> >disaster (when will the latest worm strike again?), in spite of the
> >fact that some of the products provide a useful function that is
> >frequently more user friendly than almost equivalent open source
> >products.  So how does one convince users that they need to look for
> >ways to divest themselves of the products they feel (some truth, some
> >ignorance) they cannot do without?
> >
> >There are solutions in most cases, but most users are so locked into
> >the M$ mentality that they won't even make the effort.
> 
> I agree with the sentiment but the reality is much harsher.  Most
> linux apps just aren't up to their windoze counterparts.  This is
> especially true for personal productivity apps.  The server stuff is
> much closer.
> 

It would help to know exactly what you mean by "personal productivity
apps".

> The cogent argument for change doesn't address busines use.  There is 
> LOTS of custom code running in busines.  The life span of that code is
> 15 - 20 years.  Converting to C/Java/Perl/Python/??? is a huge 
> undertaking and has no busines payoff.  It also halts improvements for
> a year or two.  No busines on the planet can afford that in todays
> market.  And heaven help the companies that have gone to outsourcing,
> they have effectively zero say in infrastructure decisions.
> 

All of this is true, but companies have to deal with the (negative)
business payoff of loosing business productivity and/or data every time
a script kiddo comes up with a new worm.  There is a also big business
payoff in terms of licensing fees.  

> The only true option to pursue for linux desktop adoption is to
> continue interoperability plans with the M$ network du jour (com, 
> dcom, .net...) and start building functionality into linux friendly 
> architectures.  It requires long term thinking and a dedication to the
> strategy.  It also requires better personal productivity apps.
> 

One thing that would help (I've mentioned this frequently) would be for
the major open source support products (glibc, gcc, and the desktop
products like kde and gnome, perhaps even the kernel) to stop the
practice of changing the interfaces and releasing non-compatible new
versions every couple of years.

There is a dearth of long term thinking in the business world.  How to
cook the books for the current quarter is about as long term as it gets.

-- 
Collins Richey - Denver Area
if you fill your heart with regrets of yesterday and the 
worries of tomorrow, you have no today to be thankful for.