Xref: utzoo comp.misc:6480 comp.sys.ibm.pc:30979 Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!microsoft!ericbr From: ericbr@microsoft.UUCP (Eric Brown) Newsgroups: comp.misc,comp.sys.ibm.pc Subject: Re: PC-WEEK Article / OS/2 obituary? Message-ID: <6221@microsoft.UUCP> Date: 4 Jul 89 00:44:40 GMT References: <238@imspw6.UUCP> Reply-To: ericbr@microsoft.UUCP (Eric Brown) Organization: Microsoft Corp., Redmond WA Lines: 28 In article <238@imspw6.UUCP> bob@imspw6.UUCP (Bob Burch) writes: >What I see really killing OS/2 dead is the following consideration: that in >the next few years, wherever you go, you'll see mid-sized computers all >running UNIX, database engines (such as the 100 tps Sequent) running UNIX, >workstations like the Suns and Appollos all running UNIX, and scores of 386 >and 486 desktop machines, and some poor slob will have to tie all of those >things together. He's going to think to himself: "Now, do I want those >desktops running OS/2 and me have to deal with two totally different software >worlds forever and with connecting them forever, or would it be simpler >to just run UNIX on everything and use simple uucp connections?" This >scenario will become the more prevalent as Sequents and machines running >new multi-processor versions of UNIX (the DG or MACH systems for instance) >replace traditional mainframes. > No, what I think you'll see is IBM mainframes talking to IBM minis talking to IBM desktops, and some poor slob is going to have to tie all of those things together, and he's going to think to himself: "Now, do I want those desktops running OS/2 and *IBM* having to deal with 3 totally different software worlds forever, or would it be simpler to just run UNIX on the desktops and have to connect them together myself?" The IBM mainframes are *NOT* going away, and IBM *is* delivering the goods to make everything talk together (granted, talking SNA/3270 simulation, but talking). And uucp is by *no* means simple to administrate or effective to use (compared to real remote file systems). Eric.