🚀 go-pugleaf

In article <1992Dec21.134531.3253@athena.mit.edu>, solman@athena.mit.edu (Jason W Solinsky) writes:

| In how many of these examples are we actually concerned with processor
| performance? In editors and word processors we certainly aren't.

  Sorry, you obviously edit only small documents. Search, or search and
replace, on a large document, can take a great deal of CPU. A global
reformat can eat the cpu. Things as simple as making the printed text
one column smaller can take many seconds in a WYSIWYG editor, since page
breaks all need to be checked or changed, page numbers in the index and
table of contents change, etc.

  It will take a massive increase in CPU to bring operations like this
down to reasonable (ie sub second) response time, so I don't think
there's any lack of market in the word processing field.

-- 
bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
    Keyboard controller has been disabled, press F1 to continue.