Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!sdd.hp.com!elroy.jpl.nasa.gov!decwrl!ogicse!milton!serval!yoda.eecs.wsu.edu!wbonner From: wbonner@yoda.eecs.wsu.edu (Wim Bonner) Newsgroups: comp.os.msdos.misc Subject: Re: OS/2 2.0 is here! (speed of OS/2) Message-ID: <1991May10.024853.19971@serval.net.wsu.edu> Date: 10 May 91 02:48:53 GMT References: <1991May8.193731.15929@Informatik.TU-Muenchen.DE> <940@slammer.UUCP> <3888@d75.UUCP> Sender: news@serval.net.wsu.edu (USENET News System) Organization: Washington State University Lines: 20 In article <3888@d75.UUCP> woan@cactus.org writes: >needs to do is write a killer app for OS/2 that can't be easily done >on MSDOS or MSDOS/Windows. Hmmm... How about GNU EMACS for OS/2? Well, I really hate all of the speculation based on OS/2 2.0, partly because I'm still running OS/2 1.3 on my fastest machine - a 10mhz286, but When OS/2 2.0 comes out things like Emacs will be easier t port to OS/2 for the simple reason that you can ignore segments and access HUGE data spaces. I know I've been thinking I'd love to do that some with my programs not so much to use lts f space, but t simply nt have t wrry abut near r far pinters. I think I read that the reasn Emacs had nt been ported t Os/2 was because it seemed too hard to deal with segments. Wim. -- | wbonner@yoda.eecs.wsu.edu | The Loft BBS | 27313853@wsuvm1.csc.wsu.edu | (509)335-4339 | 72561.3135@CompuServe.com | USR HST Dual Standard HST/V.32