Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!samsung!umich!sharkey!msuinfo!convex.cl.msu.edu!jap From: jap@convex.cl.msu.edu (Joe Porkka) Newsgroups: comp.sys.amiga.misc Subject: Re: Multitasking workbench 2.0 Message-ID: <1991Feb9.190059.26278@msuinfo.cl.msu.edu> Date: 9 Feb 91 19:00:59 GMT References: <588+H8*@irie.ais.org> <51567@cornell.UUCP> <7717@sugar.hackercorp.com> Sender: news@msuinfo.cl.msu.edu Organization: Michigan State University Lines: 20 jms@vanth.UUCP (Jim Shaffer) writes: >In article <7717@sugar.hackercorp.com> peter@sugar.hackercorp.com (Peter da Silva) writes: >>What he means is that WB 2.0 is still single-threaded. When it's doing something >Huh? Way back when various magazines were printing previews of "1.4", that Hm, its a little multithreaded now. It still waits for opening drawers, but you don't hafta wait after an application launch. Apparently the actual code for WorkBench is similar to the output of fortran-to-c converters -> very icky and hard to change. One of the projects is a complete rewrite, but this won't happen till some version after the (hopefully) RSN 2.0 However, I still think that the workbench under 2.0 as it is now is a GREAT DEAL better than under 1.3 -> thanks to Mike S. at cbm. It is quite usable, + theres lotsa new goodies in it for future applications to take advantage of.