9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "rob pike, esq." <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /sys/src/^(9 boot)^/pc/memory.c
Date: Tue, 17 Sep 2002 19:13:59 -0400	[thread overview]
Message-ID: <0228435e85db81c478249ac5b9e1a6ca@plan9.bell-labs.com> (raw)

> Can someone remind me why we can't use software cursors in 4e?

Another way of saying is that when the draw code was written, replacing
the bitblt driver, software cursors were left out in order to simplify things.
If you don't attempt to remove support for old cruft, it accumulates forever.
Complete rewrites are an excellent opportunity to eliminate unnecessary
compatibilities, and I think the case for software cursors  remains
weak unless you're in the 0.1% of the population that needs the support.
How much complexity should the kernel have - and require people to
maintain -  for low-deployment devices?

-rob



             reply	other threads:[~2002-09-17 23:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-17 23:13 rob pike, esq. [this message]
2002-09-18  4:18 ` Lucio De Re
2002-09-18 16:42   ` rob pike, esq.
2002-09-18 12:08     ` Lucio De Re
  -- strict thread matches above, loose matches on Subject: below --
2002-09-18 16:46 Charles Forsyth
2002-09-18 11:38 Russ Cox
2002-09-18 23:21 ` paurea
2002-09-18  4:49 Russ Cox
2002-09-18  5:02 ` Lucio De Re
2002-09-18  1:26 Russ Cox
2002-09-18  5:31 ` paurea
2002-09-17 22:58 Russ Cox
2002-09-17 23:41 ` paurea
2002-09-17 22:56 rob pike, esq.
     [not found] <dhog@plan9.bell-labs.com>
2002-09-17 22:04 ` David Gordon Hogan
2002-09-17 22:08   ` Scott Schwartz
2002-09-17  7:57 Charles Forsyth
2002-09-17 15:13 ` Axel Belinfante
2002-09-17 20:08   ` Axel Belinfante
2002-09-17 20:37     ` Axel Belinfante
2002-09-17  4:19 YAMANASHI Takeshi
2002-09-17  2:58 Russ Cox
2002-09-17  2:40 YAMANASHI Takeshi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0228435e85db81c478249ac5b9e1a6ca@plan9.bell-labs.com \
    --to=rob@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).