unofficial mirror of emacs-tangents@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Christopher Dimech <dimech@gmx.com>
Cc: emacs-tangents@gnu.org
Subject: Re: Emacs website, Lisp, and other
Date: Wed, 23 Oct 2024 22:41:35 +0300	[thread overview]
Message-ID: <ZxlRbxipITvTk-Lb@lco2> (raw)
In-Reply-To: <trinity-095d4d25-5510-4167-81eb-124105b9eaf2-1722973850111@3c-app-mailcom-bs08>

* Christopher Dimech <dimech@gmx.com> [2024-08-06 22:53]:
> Flamewars begin when discussions employ inflated descriptions of a language

I like it.

> For instance, a statement like "The great power of the Lisp language makes it
> ideal for other purposes, such as writing editing commands" can be seen as
> provocative. Irking those who prefer other languages or who have experienced the
> limitations of Lisp in their work.

Isn't praise for each programming language found in their books?!

Nothing wrong about it.

> Words like "great power" are subjective and can be interpreted differently by
> different people. Some might view them as an accurate reflection of Lisp's
> capabilities, while others might see them as an overstatement, leading to
> disagreements.

The context remains relevant, particularly regarding great
power. There are very few editors like Emacs, and that context is
still applicable today.

> To avoid flamewars, documentation should strive for balanced and
> factual descriptions, providing historical context.

I was thinking fun started, and now you wish to avoid it.

> A balanced documentation example would be
> 
> Emacs Lisp (Elisp) is a dialect of the Lisp programming language, chosen by
> Richard Stallman for its flexibility and his familiarity with it from projects
> like the Incompatible Timesharing System (ITS) and the Lisp Machine Operating
> System at MIT.

That above is Boring, come on, here is better version:

Emacs Lisp (Elisp) is not just any programming language; it's the
beating heart of the ultimate text editor, Emacs. Chosen by the
brilliant Richard Stallman for its unparalleled flexibility, Elisp
empowers users to customize their editing experience in ways that are
simply impossible with other editors. Stallman’s expertise, honed
through groundbreaking projects like the Incompatible Timesharing
System (ITS) and the Lisp Machine Operating System at MIT, solidified
Elisp as the backbone of Emacs, transforming it into an editor that
transcends mere text editing. With Elisp, users tap into a world of
infinite possibilities, tailoring Emacs to fit their every need,
making it the best choice for anyone serious about productivity and
creativity. Why settle for less when you can harness the power of
Elisp in the finest editor ever created? Emacs truly sets the
standard!

Emacs is not just an editor; it is a revolution in the world of text
manipulation, a sophisticated powerhouse that redefines the very
concept of what an editor can be! Its design, meticulously crafted
with unparalleled attention to compatibility with Unix, catapults it
to a level of portability that no other editor can even dare to
approach.

With the incredible capabilities of Elisp, the very lifeblood of
Emacs, users have at their fingertips a relentless, supercharged tool
for writing editing commands that eclipses the functionality of all
other editors combined! The possibilities are limitless—commanding
every aspect of your workflow with elegance and precision that’s
simply unattainable in any other editing environment.

While other programming languages might boast their unique strengths,
they pale in comparison to the sheer versatility of Emacs and
Elisp. Why settle for mediocrity when you can wield the best? Emacs is
not merely suited for specific tasks; it is a universal toolkit that
transforms the mundane into the extraordinary, empowering every user
to achieve feats of productivity that would leave mere mortals in awe.

Emacs is, without a doubt, the ultimate editor, the crown jewel of
software development, a perennial favorite for those who value true
mastery over their editing experiences. Embrace the greatness of
Emacs, and you will never look back!


-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

✡️🛡️ Proudly standing with Israel, a nation rooted in history and culture. Let's condemn hatred and promote understanding.

In support of Richard M. Stallman
https://stallmansupport.org/

---
via emacs-tangents mailing list (https://lists.gnu.org/mailman/listinfo/emacs-tangents)

  parent reply	other threads:[~2024-10-23 19:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87sevj9b50.fsf@jeremybryant.net>
     [not found] ` <871q33rj7v.fsf@dataswamp.org>
2024-08-05 20:03   ` Emacs website, Lisp, and other Alan Mackenzie
2024-08-05 21:07     ` Christopher Dimech via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
2024-08-06  7:42     ` Jean Louis
2024-08-06 11:14     ` Immanuel Litzroth
     [not found]   ` <trinity-dae5eb6f-9f3b-451e-ac64-5d82d5ea1bef-1722849793865@3c-app-mailcom-bs04>
     [not found]     ` <86ed73qhly.fsf@gnu.org>
     [not found]       ` <87frrjoryg.fsf_-_@dataswamp.org>
2024-10-23 19:25         ` 10 problems with Elisp, part 10 (was: Re: Emacs website, Lisp, and other) Jean Louis
2024-10-23 21:13           ` Emanuel Berg
2024-10-23 21:36             ` Jean Louis
2024-10-25  6:44               ` Emanuel Berg
2024-10-28  3:27                 ` 10 problems with Elisp, part 10 Joel Reicher
2024-10-24  6:48             ` Dr. Arne Babenhauserheide via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
     [not found] ` <86h6bzqj2v.fsf@gnu.org>
     [not found]   ` <87ed718o45.fsf@jeremybryant.net>
     [not found]     ` <trinity-095d4d25-5510-4167-81eb-124105b9eaf2-1722973850111@3c-app-mailcom-bs08>
2024-10-23 19:41       ` Jean Louis [this message]
2024-10-24  6:39         ` Emacs website, Lisp, and other Dr. Arne Babenhauserheide via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
     [not found]       ` <BLAPR10MB5219692C7A9F536BCA442ABDF3BF2@BLAPR10MB5219.namprd10.prod.outlook.com>
     [not found]         ` <87wmktb8w7.fsf@web.de>
     [not found]           ` <DS7PR10MB52323E8786643BA9ADC6E45DF3BF2@DS7PR10MB5232.namprd10.prod.outlook.com>
2024-10-23 19:45             ` [External] : " Jean Louis
2024-10-23 20:25               ` Drew Adams via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
2024-10-23 20:50                 ` Jean Louis
2024-10-23 21:21                   ` Drew Adams via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
2024-10-23 21:37                     ` Jean Louis
     [not found]         ` <87le186g3f.fsf@dataswamp.org>
     [not found]           ` <m3v802l9vn.fsf@leonis4.robolove.meer.net>
     [not found]             ` <87ed6qbah6.fsf@dataswamp.org>
     [not found]               ` <m3o75ukuvn.fsf@leonis4.robolove.meer.net>
     [not found]                 ` <87cyma5crl.fsf@dataswamp.org>
2024-10-23 19:48                   ` Jean Louis
     [not found]             ` <87bk1ub98z.fsf@dataswamp.org>
2024-10-23 19:52               ` Jean Louis
     [not found] <O3bfP50--7-9@tuta.io>
     [not found] ` <87ikwc6bd2.fsf@dataswamp.org>
2024-10-23 19:59   ` Jean Louis

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=ZxlRbxipITvTk-Lb@lco2 \
    --to=bugs@gnu.support \
    --cc=dimech@gmx.com \
    --cc=emacs-tangents@gnu.org \
    /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.
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).