From owner-freebsd-chat Wed Apr 2 10:46:26 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA15680 for chat-outgoing; Wed, 2 Apr 1997 10:46:26 -0800 (PST) Received: from mail.konnections.com (mail.konnections.com [192.41.71.11]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA15675 for ; Wed, 2 Apr 1997 10:46:23 -0800 (PST) Received: from castle (root@ip205.konnections.com [192.41.71.205]) by mail.konnections.com (8.8.3/8.8.3) with SMTP id LAA28246; Wed, 2 Apr 1997 11:43:52 -0700 (MST) Message-ID: <3343F926.5BA1B96E@konnections.com> Date: Thu, 03 Apr 1997 11:38:30 -0700 From: mike allison Organization: Publisher -- Burning Eagle Book Company X-Mailer: Mozilla 3.0 (X11; I; Linux 2.0.0 i486) MIME-Version: 1.0 To: Terry Lambert CC: Nate Williams , proff@suburbia.net, chat@freebsd.org Subject: Re: Internal clock References: <199704020110.SAA12652@phaeton.artisoft.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-chat@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert wrote: > > > Since I don't believe even you think a person can have intimate > > fore-knowledge of what someone intends to do with a piece of software, > You plan to allow as close to "any reasonable use" as you can, and > when it falls down againsts someone's "reasonable use", you correct > it. > > It's not a matter of knowing how someone will use it, it's a matter > of not closing off possible uses through poor design considerations. It's not so much a matter or reasonable use, but reasonable use within a set of established parameters. If you run into soething that wasn't planned for, but later think might be reasonable, AND won't work. You must decide whether it's important enough to rebuild the whole system or move on. I think we've seen that too often since MSDOS 1.0, System 7, OS/2 and all the proprientary minicomputer systems. The implementation team has to decide what's reasonable and what hooks to leave in. The later programmers are charged with using those hooks and not building something into their application which damages other apps through poor or irresponsible programming. I think that's Terry's point in "design considerations". The Linux folks have the problem of EVERYONE being part of the design team. It win't be long before there are SERIOUS and INHERENT incompatabilities between different distributions of the same LINUX release. That's why you have and must use the core team to set the parameters. You're never going to be able to anticipate what's even reasonable. The design team DICTATES what's reasonable on their system. -Mike