unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: "T.V Raman" <raman@google.com>
Cc: luangruo@yahoo.com, raman@google.com, emacs-devel@gnu.org
Subject: Emacs is not a research project
Date: Sat, 14 Jan 2023 01:07:04 -0500	[thread overview]
Message-ID: <E1pGZh2-0005C8-PM@fencepost.gnu.org> (raw)
In-Reply-To: <25536.7501.599000.992530@retriever.mtv.corp.google.com> (raman@google.com)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > Emacs from 40 years ago created a lot of innovations  that still shine
  > in today's world. Given that those innovations happened in a world
  > that distinctly lacked the  hardware ans the associated UI affordances
  >  that we have today; how might Emacs create the next round of
  >  innovation that will shine for the next 40 years?

Beyond simply being good to use, the overarching goal of the GNU
system, including GNU Emacs, is to give users freedom to control their
own computing.

Compared with freedom, innovation is a side issue.  Our society
generally overemphasizes innovation as a goal, often as a way of
distracting users from questions of their own freedom.

If in working on Emacs you think of a useful new feature and you
implement it in GNU Emacs, we will appreciate that innovation.  But we
won't measure the success of our work by how much the
user-disrespecting nonfree programs of 30 years from now are
influenced by our work.  We aim to replace them with free software,
not to enhance them.

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





  reply	other threads:[~2023-01-14  6:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87mt6pfpy5.fsf.ref@yahoo.com>
2023-01-11  8:14 ` Easy things for Android port Po Lu
2023-01-11 15:27   ` T.V Raman
2023-01-12  6:04     ` Po Lu
2023-01-12 12:50       ` Jean Louis
2023-01-12 14:46       ` T.V Raman
2023-01-14  6:07         ` Richard Stallman [this message]
2023-01-13 23:20       ` Björn Bidar
2023-01-13 23:22         ` Björn Bidar

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=E1pGZh2-0005C8-PM@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=raman@google.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).