Article View: comp.os.os2.programmer
Article #3343Re: Why you should get everything in writing (long)
From: Jeff Urlwin
Date: Fri, 08 Jan 1993 00:26
Date: Fri, 08 Jan 1993 00:26
33 lines
2235 bytes
2235 bytes
In article <1993Jan7.220154.446@fcom.cc.utah.edu> brian@jaguar.cs.utah.edu (Brian Sturgill) writes: >In article <1ii7alINNon4@controversy.math.lsa.umich.edu> spexet@math.lsa.umich.edu (D. Robert Spexet II) writes: >>In article <1993Jan7.192103.16828@netcom.com> rcain@netcom.com (Robert Cain) writes: >>>I joined the Developers Assistance Program and through that arm >>>obtained a verbal assurance that there would be "no problem" obtaining >>>said source code since there was nothing proprietary. Based on this >>>assurance and the license I had negotiated for using the interpreter I >>>quit my day job to live off my savings and develop this product which I >>>was going to call SimpleScript. >> >>Not to question your judgement in this case, but do you think that it was >>really a wise move to do what you did on the basis of a verbal promise, >>with nothing backing it up in writing? > > >I think you misunderstand Bob's problem. All he wanted was a sample printer >driver. IBM should have had this available well before OS/2 2.0 GA shipped. >The point is that they didn't, and they still don't. >I would agree with you comment if Bob had wanted something unusual from >IBM, but this is standard stuff. Well, let's go back a little here. He wouldn't have had a problem if MS hadn't bailed out of OS/2. Don't be so quick to jump further on the IBM bash band wagon that you drive. In essence, all three are at fault. IBM *should* have remedied this by now, but I suspect MS is stonewalling and IBM is scurrying to try and get this stuff out... Jeff -- -------------------------------------- jurlwin@gandalf.umcs.maine.edu
Technical Details
Message-ID:
<1993Jan8.002640.5554@gandalf.UMCS.Maine.EDU>Path:
arc1-ca.pugleaf.net!sparky!uunet!spool.mu.edu!hri.com!noc.near.net!saturn.caps.maine.edu!gandalf!jurlwinReferences:
<1993Jan7.192103.16828@netcom.com> <1ii7alINNon4@controversy.math.lsa.umich.edu> <1993Jan7.220154.446@fcom.cc.utah.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!spool.mu.edu!hri.com!noc.near.net!saturn.caps.maine.edu!gandalf!jurlwin From: jurlwin@gandalf.UMCS.Maine.EDU (Jeff Urlwin) Newsgroups: comp.os.os2.programmer,comp.os.os2.advocacy Subject: Re: Why you should get everything in writing (long) Message-ID: <1993Jan8.002640.5554@gandalf.UMCS.Maine.EDU> Date: 8 Jan 93 00:26:40 GMT References: <1993Jan7.192103.16828@netcom.com> <1ii7alINNon4@controversy.math.lsa.umich.edu> <1993Jan7.220154.446@fcom.cc.utah.edu> Organization: University of Maine, Department of Computer Science Lines: 33