🚀 go-pugleaf

Mark Parker <condor@intele.net> wrote:
[snipt]
: How did you find out how efficiently it will be writen? Just curious.


The MacOS has 10 years of patches and kludges on top of patches and kludges.

My understanding is that those parts of Copland that are being taken 
native explicitly for Copland are being redesigned from the ground up (as 
opposed to simply being recompiled or having the algorithms put into 
native C code), thereby eliminating 10 years of hacking.

The kernel will be brand-new, and presumably optimized for speed. Ditto 
with the print-driver interface, the disk driver interface, the 
networking, and so on. The only things left untouched (algorithm-wise) 
will be human-interface stuff (QuickDraw and company) and the rest of the 
Mac toolbox, which would require several years to rewrite/redesign (hence 
Gerswin).

Any new Copland app will be able to take advantage of all-new designs for 
all non-Blue-box calls. The graphics will be native, but non-reentrant, 
just as they are now.


Process-switching, networking I/O, disk I/O, etc, should be faster for 
all apps, old and new.

Virtually any native app running on Copland should "feel" faster. 
Copland-savvy apps should actually BE faster, if they do anything outside 
of current System 7 calls.



--
-------------------------------------------------------------------------------
Lawson English                            __  __     ____  ___       ___ ____
english@primenet.com                     /__)/__) / / / / /_  /\  / /_    /
                                        /   / \  / / / / /__ /  \/ /___  /
-------------------------------------------------------------------------------