Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!thyme!kaleb
From: kaleb@thyme.jpl.nasa.gov (Kaleb Keithley)
Newsgroups: comp.windows.x.motif
Subject: Re: Motif Shared Library Licensing
Message-ID: <1991Feb11.211658.6267@thyme.jpl.nasa.gov>
Date: 11 Feb 91 21:16:58 GMT
References: <910209111013.22414@alphalpha> <9102111346.AA17876@twiddle.eng.umd.edu>
Distribution: inet
Organization: Jet Propulsion Laboratory, Pasadena, CA
Lines: 29

In article <9102111346.AA17876@twiddle.eng.umd.edu> stripes@ENG.UMD.EDU ("Stripes ", or Josh, if you must) writes:
>
>Kee Hinckley said:
>[...]
>
>>This has got to change.  OSF has got to get out of this vendor-oriented
>>view of the world (ISVs don't provide shared libraries, vendors do).
>
>If you ship your own copy of Motif, who are you going to share it with?  Or
>do you have more then one product that uses the same fixed fersion of Motif?
>If not then a shared lib will be no win over a shared lib (in fact a marginal
>loss, PIC code is a tiny bit slower then position dependent code).
>

Well, my $0.02 worth:  We are supplying our (internal) customer with
our own Motif based applications, eXclaim, and Island WPD, Motif version.
Our own applications number in the dozens, so shared libraries are a must.
We're using three screens on a Sun SparcServer, the users will be running
the programs simultaneously.  It would be a big plus if eXclaim and Island 
WPD used the shared libraries we've built for our own applications.

For one thing, it would ensure that the version of Motif that's being used
is the latest, greatest, and most bug free that there is, which is always
going to be suspect when it's statically linked to the application!
-- 
Kaleb Keithley                        kaleb@thyme.jpl.nasa.gov

As of right now, I'm in charge here now...                  Alexander Haig.
Voodoo Economics, that's what it is, voodoo economics.      George Bush