From owner-freebsd-current  Mon Aug  4 14:03:06 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id OAA27472
          for current-outgoing; Mon, 4 Aug 1997 14:03:06 -0700 (PDT)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA27465
          for <current@FreeBSD.ORG>; Mon, 4 Aug 1997 14:03:03 -0700 (PDT)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id OAA02226; Mon, 4 Aug 1997 14:00:19 -0700 (PDT)
To: Terry Lambert <terry@lambert.org>
cc: helbig@MX.BA-Stuttgart.De, andreas@klemm.gtn.com, current@FreeBSD.ORG
Subject: Re: Current is currently really a mess (was: Re: Tk/Tcl broken(?)) 
In-reply-to: Your message of "Mon, 04 Aug 1997 10:18:55 PDT."
             <199708041718.KAA04267@phaeton.artisoft.com> 
Date: Mon, 04 Aug 1997 14:00:19 -0700
Message-ID: <2222.870728419@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> Actually, the main failing of Apple, historically, has been that
> any time there was a tradeoff between ease of use for the user and
> ease of use for the developer, it was the policy that the user won.
> 
> This won Apple a lot of die-hard users, who are still around.
> 
> It won them few developers.

This is an overly simplistic summary of the situation, however.

We *do* support the developers, and the very existance of -current
goes quite a bit beyond anything Apple ever did to let developers in
on their plans for future OS technologies.  This whole ports thing has
been a tempest in a teapot, and while I don't argue that the ports
collection is useful to developers and users alike, I don't think that
it's tantamount to saying that our support for developers has suddenly
dried up and disappeared because of this one problem in supporting
ports for -current.

					Jordan