Path: utzoo!utgpu!watserv1!watmath!att!att!pacbell.com!ucsd!usc!zaphod.mps.ohio-state.edu!lavaca.uh.edu!menudo.uh.edu!sugar!ficc!peter From: peter@ficc.ferranti.com (Peter da Silva) Newsgroups: comp.misc Subject: Re: A tirade about inefficient software & systems Message-ID: Date: 30 Oct 90 21:28:26 GMT References: <9886@milton.u.washington.edu> <=YN6UN5@xds13.ferranti.com> <8460@scolex.sco.COM> <11R6593@xds13.ferranti.com> <1534@svin02.info.win.tue.nl> Reply-To: peter@ficc.ferranti.com (Peter da Silva) Organization: Xenix Support, FICC Lines: 30 In article <1534@svin02.info.win.tue.nl> rcpieter@svin02.info.win.tue.nl (Tiggr) writes: > peter@ficc.ferranti.com (Peter da Silva) writes: > >Finally, be careful *what* application you get to do a given task. For > >example, window refreshing belongs in the display server task, not duplicated > >in every application. > Bad example. Nope, a good example. An example everyone agreed with would be a bad example. > You should have mentioned MS-DOS where every application > is very bad because the programmer spends ages on writing display and > printer drivers instead of writing a Good Program. I don't think there's anyone here who needs to be enlightened about MS-DOS. > Window refreshing must be done by the task owning the window. Even if it's at the other end of a 2400 baud SLIP link from the display server? > Having the window manager store bitmaps is stupid, > restricting and it consumes much too much memory. It consumes just as much memory either way, and it requires the client be able to respond in real-time... something that's just plain not possible in UNIX. It makes as much sense to have "xman" handle update events as it does to have "cat" do erase and kill processing. -- Peter da Silva. `-_-' +1 713 274 5180. 'U` peter@ferranti.com