From: David Kastrup <dak@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Random832 <random832@fastmail.com>, emacs-devel@gnu.org
Subject: Re: Another iteration on the Emacs website
Date: Sat, 12 Dec 2015 10:55:47 +0100 [thread overview]
Message-ID: <876104kn30.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83bn9w6s46.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 12 Dec 2015 09:30:49 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Random832 <random832@fastmail.com>
>> Date: Fri, 11 Dec 2015 20:14:18 -0500
>>
>> Xue Fuqiao <xfq.free@gmail.com> writes:
>>
>> > On Sat, Dec 12, 2015 at 8:15 AM, Gregor Zattler <telegraph@gmx.net> wrote:
>> >
>> >> [2] The only other projects of similar age which come to
>> >> (my) mind are the X Window System and the TeX familiy of
>> >> programs.
>> >
>> > Maybe you forgot some GNU projects, like Hurd, glibc, Bash, GCC, GDB,
>> > Octave, and Texinfo.
>>
>> Depends on what you mean by similar age.
>>
>> 1978 TeX
>> 1983 AMS-TeX
>> 1984 X
>> 1984 Emacs
>> 1985 LaTeX
>> 1986 GDB
>> 1987 GCC
>> 1988 glibc
>> 1989 Bash
>> 1990 Hurd
>> 1992 Octave ("conceived" 1988)
>
> Emacs started the GNU project,
"Emacs" preceded the GNU project. The Gosling Emacs rat-out prompted
Richard to write the GPL and sketch out the definition and needs for
GNU. The Emacs code base was rewritten to be free of third-party
copyrights and then restarted as GNU Emacs.
> so it's a small wonder it predates any other GNU package. Also, first
> versions of GCC and GDB were written by Richard, which is another
> reason why they came after Emacs.
The main reason is that they were written as components for the GNU
project whereas Emacs was written as a tool for editing. The original
Emacs was free software but not copylefted, and that backfired. Once
copyleft was created and there was a formal definition of free software,
there was an incentive for creating a whole cohesive system relying on
copyleft protection for seminal parts and assembled with outside
components also providing the four software freedoms even if not the
copyleft's mechanism protecting them.
--
David Kastrup
next prev parent reply other threads:[~2015-12-12 9:55 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 10:34 Another iteration on the Emacs website Nicolas Petton
2015-12-11 11:03 ` Shakthi Kannan
2015-12-11 12:41 ` Nicolas Petton
2015-12-11 17:03 ` Shakthi Kannan
2015-12-12 0:35 ` Xue Fuqiao
2015-12-11 11:06 ` Eli Zaretskii
2015-12-11 12:42 ` Nicolas Petton
2015-12-11 12:26 ` John Yates
2015-12-11 13:51 ` Dmitry Gutov
2015-12-11 15:10 ` Rasmus
2015-12-11 17:11 ` Nikolaus Rath
2015-12-11 17:24 ` Nicolas Petton
2015-12-12 0:15 ` Gregor Zattler
2015-12-12 0:51 ` Xue Fuqiao
2015-12-12 1:14 ` Random832
2015-12-12 7:30 ` Eli Zaretskii
2015-12-12 9:55 ` David Kastrup [this message]
2015-12-13 6:50 ` Richard Stallman
2016-02-27 18:54 ` Mathias Dahl
2016-02-28 10:24 ` Richard Stallman
2016-02-28 17:25 ` Mathias Dahl
2016-02-28 18:15 ` H. Dieter Wilhelm
2016-02-28 23:33 ` John Wiegley
2016-02-29 13:31 ` Richard Stallman
2016-02-28 19:55 ` Paul Eggert
2016-02-29 13:31 ` Richard Stallman
2015-12-12 5:03 ` Richard Stallman
2015-12-14 8:46 ` Nicolas Petton
2015-12-15 3:57 ` Richard Stallman
2015-12-15 3:57 ` Richard Stallman
2015-12-12 0:25 ` Xue Fuqiao
2015-12-12 23:53 ` John Wiegley
2015-12-14 8:37 ` Nicolas Petton
2015-12-14 20:52 ` Christian Dietrich
2015-12-14 22:19 ` Xavier Maillard
2015-12-15 0:11 ` Stephan Mueller
2015-12-16 21:50 ` zv
-- strict thread matches above, loose matches on Subject: below --
2015-12-15 3:24 Brian Burns
2015-12-15 10:21 ` Nicolas Petton
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=876104kn30.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=random832@fastmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).