From owner-freebsd-hackers Sat Sep 21 10:27:20 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA21799 for hackers-outgoing; Sat, 21 Sep 1996 10:27:20 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA21779 for ; Sat, 21 Sep 1996 10:27:18 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id KAA11982; Sat, 21 Sep 1996 10:27:13 -0700 (PDT) To: Julian Elischer cc: Richard Heaton , hackers@freebsd.org Subject: Re: Job openings: Unix Network Programmers, Internet server In-reply-to: Your message of "Sat, 21 Sep 1996 09:49:06 PDT." Date: Sat, 21 Sep 1996 10:27:12 -0700 Message-ID: <11980.843326832@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Of course, as they are in direct competition with Whistle, > we hope you'll talk to us too :) Actually, since you mention it, you guys don't have to view this entirely as "competition" and could actually share some of the development work in areas where there's no "competetive advantage" to give away. Richard and I talked about this yesterday, and Empac feels that things like general PPP improvements or bug fixes to the system should not be viewed as competition points, it being in everyone's best interest to make FreeBSD as robust and reliable a development platform as possible. The competetive advantages lie in what is placed on top, not the foundation, and given that firms like Whistle and Empac are both relatively small (certainly when compared to the Mighty Microsoft), they'd do well to pool their resources if and whenever possible. Richard told me yesterday that Microsoft recently announced a multi-billion (yes, billion) dollar initiative to make NT *the* network operating system in 1997, and that's a whole heck of a lot of money. It's time for small companies involved with UNIX to pool their efforts or Bill is going to eat them all. He might eat them anyway, in the long run, but I'd really hate to look back on this time and reflect that we made it easy for him to do so by squabbling amongst ourselves while Microsoft raced ahead. I think the UNIX community has already done far too much of that already and it's time for a change. Perhaps we could set about identifying areas of common interest and open a discussion on mutual development priorities? Jordan