From owner-freebsd-current Sat Jun 22 14:11:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA09270 for current-outgoing; Sat, 22 Jun 1996 14:11:01 -0700 (PDT) Received: from mail.think.com (Mail1.Think.COM [131.239.33.245]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA09264 for ; Sat, 22 Jun 1996 14:10:58 -0700 (PDT) Received: from Early-Bird-1.Think.COM by mail.think.com; Sat, 22 Jun 96 16:49:31 -0400 Received: from compound.Think.COM by Early-Bird.Think.COM; Sat, 22 Jun 96 17:10:46 EDT Received: (from alk@localhost) by compound.Think.COM (8.7.5/8.7.3) id QAA02156; Sat, 22 Jun 1996 16:13:04 -0500 (CDT) Date: Sat, 22 Jun 1996 16:13:04 -0500 (CDT) From: Tony Kimball Message-Id: <199606222113.QAA02156@compound.Think.COM> To: wosch@cs.tu-berlin.de Cc: current@freefall.freebsd.org Subject: Re: tcl -- what's going on here. Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk From: Wolfram Schneider Date: Sat, 22 Jun 1996 16:59:16 +0200 You can't remove perl from the main tree ;-))) Many sytem tools are written in perl. Don't waste your time to rewrite them in C because you don't like perl! This misses the point. The point is not that perl is unliked. Perl is almost universally acknowledged as the right tool for its job. The point is that it does not belong in the base system. I will invariably install perl on every system I install, with the exception of those which essentially serve as embedded controllers or routers or the like. But including perl in the base OS inflates the base OS by several megabytes (which one cannot afford in important special cases) locks it into obsolete software, annoys and confuses users of the up-to-date version, and is just plain evil. I suggested that I would be willing to rewrite those few perl kludges which are current. I was rebuffed.