Global Alert For All: Jesus is Coming Soon

Gerard Kleijwegt gerard at rigel.bmc.uu.se
Sun Jan 23 16:37:07 EST 1994


In article <1994Jan18.235010.25293 at csi.uottawa.ca>, misrael at csi.uottawa.ca (Mark Israel) writes:
|> In article <2hhcc2$kmg at corax.udac.uu.se>, Gerard Kleijwegt <gerard at rigel.bmc.uu.se> writes:
|> 
|> > OOPS is NOT compatible with FRODO.
|> 
|>    Ha!  We have the *source code* for Frodo, so we can make 
|> it compatible with *anything*!  No such luck with O.

Good luck !

|> 
|> > Real men don't use FRODO, they write O macros.
|> 
|>    What kind of "real men" we be talking about here, boy?

Those with a sense of humour.  (And, please, don't call
me "boy"; I'm at the other end of the Atlantic, so
"old chap", "lad" or "old bean" would be acceptable).

|> 
|>    Some real people are end-users; others are programmers.
|> 
|>    End-users don't *want* to waste their time writing macros.
|> They want a *program* that does what they want -- not a 
|> subroutine library!

Then, for Heaven's sake, do *NOT* use O.  Wait until one of the
me-too O-rip-offs offers you a precooked command.  Or, better still,
use a Richard's box (doesn't coredump, doesn't waste CPU;
may collapse under its own weight and crush you, though;
therefore not recommended for large proteins and viruses).
Even better: wait until Biosym or Mol. Sim. come with a
user-friendly O-clone ("yesterday's science with today's
user-interface at tomorrow's prices") and spend three
PhD-students' worth of cash on that instead !

|> 
|>    As for programmers, we realise that macros can't do 
|> everything.  Try writing a *macro* that will prevent O from
|> sucking CPU cycles while doing nothing!  (*Don't* tell me
|> to "just iconize the graphics window".  Even if the user
|> pauses for *just a few seconds*, niceness demands that the 
|> graphics program desist and give background jobs a crack at 
|> the CPU.)

See my previous posting for a one-line macro which does just that.
On the other hand, if you can afford it, you should have two
types of machine: graphics and compute engines.  You do not
want to run XPLOR in the background when you use any graphics
program.

|> 
|>    In April of 1991 we tried out an early version of O for
|> the SGI.  It didn't have side-by-side split stereo.  (Yes,
|> I *know* this subsequently been added.)  I sent Alwyn Jones
|> a message, saying that we were unlikely to use O until split
|> stereo was available.  His e-mailed response was two words
|> long:  "your loss".  It's attitudes like that that make me
|> distrustful of monopolies, even by Alwyn.

First of all, I think it violates "netiquette" to quote from
private E-mails without asking people's permission to do so.
Apart from that, there's a thing called psychology.  Alwyn is
not sitting behind his computer anxiously waiting for requests
for new options and bug reports.  If you send *ANYONE* in
the xtallographic community who develops software which you
(almost) get for free, a mail saying "I am NOT going to use
your program until you implement this or that", what do you
think the response will be (if any) ???
By the way, Alwyn doesn't read Usenet, so he can't defend
himself in this forum.
As for "Alwyn's monopoly":
- originally, O was intended to be his private play-thing;
  it was not intended for world-wide distribution; still,
  no one is forced to use O.  If you rate user-friendliness
  higher than versatility and "state-of-the-art-ness", fine.
- in the case of FRODO, there was no monopoly and source code
  was freely distributed and not copyrighted.  Thanks to this,
  FRODO-off-rippers can now make money by selling their product
  to companies (without paying a penny to Alwyn).  I can't
  blame him for not handing out source code anymore.

|> 
|> > OOPS will look for bad or suspect disaster areas.  It then 
|> > generates a set of O macros which automatically take you 
|> > from one disaster area to the next and tell you what's 
|> > wrong/suspect about it, thereby reducing the time it takes 
|> > you to rebuild your world by a factor of 2 to 10.
|> 
|>    O.K., it's true we don't yet have Real Space Fit in 
|> Frodo/TOM.  We've got rotamers, an O-inspired DgLp, and mouse 
|> controls, but I admit I envy you the Real Space Fit.  Given 
|> the will, we'll find a way.
|> 
|> misrael at csi.uottawa.ca			Mark Israel

--Gerard

******************************************************************
               Gerard J. Kleywegt              ___  
  Department of Molecular Biology              | |  /\
                Biomedical Centre             /\ -- ||
            University of Uppsala             || || ||
                          Uppsala             || || ||
                           SWEDEN             || \/ --
                                              --  |__|
  E-mail: gerard at xray.bmc.uu.se
******************************************************************
           "He's probably pining for the fiords ..."
******************************************************************
  The opinions in this mail/post are fictional.  Any similarity
   to actual opinions, living or dead, is purely coincidental.
          (Nevertheless, they're mine, mine, MINE !)
******************************************************************





More information about the Xtal-log mailing list