Newsgroups: comp.sys.amiga.advocacy Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!menudo.uh.edu!sugar!peter From: peter@sugar.hackercorp.com (Peter da Silva) Subject: Re: NeXT Press Release Message-ID: <1991Apr28.125746.14051@sugar.hackercorp.com> Organization: Sugar Land Unix -- Houston, TX References: <47889@ut-emx.uucp> Date: Sun, 28 Apr 1991 12:57:46 GMT In article <47889@ut-emx.uucp> greg@ccwf.cc.utexas.edu (Greg Harp) writes: > Of course, NeXT went and stuck you with Obj-C if you want to use their > Interface Builder. It'd be nice if you could select the language like most > other interface design packages I've used. You can. Just link your application in C or C++ to the UI part in ObjC (to me, it's a tossup which one is more likely to make me toss my cookies anyway. C++ and ObjC are like Ratfor and EFL... bags on the side of a language to make it do stuff it wasn't intended to. When a better OO language gets a few good implementations under its belt, it will blow C++ away, as C blew away Ratfor. Eiffel might do it, but I suspect it'll end up like TRAC... another forgotten proprietary language). I don't understand your complaint here, anyway. You don't like the fact that NeXT stuck you with ObjC for their IB because it's not portable. So? Anything that depends on their IB isn't portable in the first place. -- Peter da Silva. `-_-' .