Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!snorkelwacker!bloom-beacon!eru!luth!sunic!mcsun!cernvax!chx400!sgzh!root
From: root@sgzh.uucp (Bruno Pape)
Newsgroups: comp.sys.sgi
Subject: Re: noport() vs. ginit()
Message-ID: <1990Mar26.084636.12046@sgzh.uucp>
Date: 26 Mar 90 08:46:36 GMT
References: <1990Mar22.142346.7801@sgzh.uucp> <5662@odin.corp.sgi.com>
Reply-To: root@sgzh.UUCP (Bruno Pape)
Organization: Silicon Graphics S.A., Zuerich, Switzerland
Lines: 30

In article <5662@odin.corp.sgi.com> robert@sgi.com writes:
>
>In article <1990Mar22.142346.7801@sgzh.uucp>, root@sgzh.uucp (Bruno
>Pape) writes:
>> 
>> Old habits like ginit() never go away, unless they quit working.
>			 		 	      ^^^^ ^^^^^^^
>and you know what many customers say when something stops working:
>
>	"HEY, YOU BROKE IT!"
>
>"But that old ginit() doesn't really apply anymore."
>	
>	"IT DOESN'T WORK ANYMORE!"
>
>"But if you use this whizzy new thing it works much better and you
>get all these new features."
>
>	"YOU BROKE IT!"
>

I did not mean to imply that you should start breaking things.  PLEASE NO,
NOT THAT.  I enjoy programming my 4D like a 2400 just as much as the next guy.

It was just my way of saying that some of the older techniques will be
my first choice until they quit working.  But lets not rush it along.

Thanks,

Bruno