home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!overload!dillon
- From: dillon@overload.Berkeley.CA.US (Matthew Dillon)
- Newsgroups: comp.sys.next.misc
- Subject: Re: NRW- coming soon
- Distribution: world
- Message-ID: <dillon.0t3s@overload.Berkeley.CA.US>
- References: <1gitslINNnat@gap.caltech.edu> <1992Dec15.120131.5165@lth.se> <1gugnqINNbmt@mirror.digex.com> <1992Dec20.222546.8660@cubetech.com>
- Date: 22 Dec 92 20:51:01 PST
- Organization: Not an Organization
- Lines: 35
-
- In article <1992Dec20.222546.8660@cubetech.com> andrew@cubetech.com writes:
- >In article <1gugnqINNbmt@mirror.digex.com> hacker@access.digex.com (Dark Hacker) writes:
- >
- >Start writing multithreaded apps now so they scream if NeXT puts out a
- >multi-cpu box in the future...
-
- NeXT doesn't properly support multithreading and they say so... I'm
- talking about NeXTStep here, not mach. Objective-C call overhead
- tripples and many NS subsystems are not thread-safe. Furthermore,
- NeXTStep itself does not support threads well... take distributed
- objects, for example. It's nearly impossible to move a distributed
- object *entirely* into its own thread. The most obvious application I
- can think of and NeXT doesn't support it properly. (The few examples
- they have in that area either do not work or do not move the object
- entirely to its own independant thread).
-
- Until this stuff becomes standard instead of optional, it isn't going
- to happen.
-
- -Matt
-
- >andrew
- >--
- >andrew@cubetech.com | "I'm allergic to cigarette smoke, but THIS
- >Andrew Loewenstern | kind of smoke I can handle!"
- >Cube Technologies, Inc. | John Draper, aka Captain Crunch Dec 18, 1992
- >0000000701B61D1ADF0DFC9C16185CEA055200000007EB4A9FEB1922065D471A89E905B5
-
- --
-
- Matthew Dillon dillon@Overload.Berkeley.CA.US
- 1005 Apollo Way uunet.uu.net!overload!dillon
- Incline Village, NV. 89451 ham: KC6LVW (no mail drop)
- USA Sandel-Avery Engineering (702)831-8000
-
-