all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Alain.Cochard@unistra.fr
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [RFC] Backend vs. back-end (was: 2 'echo' bash instructions produce a table)
Date: Thu, 06 Apr 2023 09:57:56 +0000	[thread overview]
Message-ID: <87ile9fi3f.fsf@localhost> (raw)
In-Reply-To: <25587.35235.779651.612028@gargle.gargle.HOWL>

[-- Attachment #1: Type: text/plain, Size: 1546 bytes --]

Alain.Cochard@unistra.fr writes:

>  > I looked further, and the situation is not as simple.
>  > https://grammarhow.com/backend-back-end-or-back-end/, for example,
>  > claims that only "back-end" is grammatically correct.
>  > 
>  > I am now thinking to do the following:
>  > 1. Use "backend" in the code symbols
>  > 2. Use "back-end" in docstrings and the manual.
>  > 
>  > Would it make sense?
>
>
> It is not clear to me why it would be a problem to use 'backend' in
> code symbols as well, but the only important thing for me as a user is
> that the terminology be consistent throughout the documentation.  So
> yes, it makes sense.
>
> The link you provide is very convincing.  Will it still hold in 5 or
> 10 year from now?  (see end of
> https://www-cs-faculty.stanford.edu/~knuth/email.html)

Well. This is a tricky subject.
5-10 years from now the grammar itself may change.
At the end, even Oxford Dictionary my link is referring to, when
defending that "backend" without hyphen is wrong, is not setting
standards, but just reflecting the existing ones.

If we look into
https://ell.stackexchange.com/questions/117383/what-is-the-correct-term-back-end-back-end-or-backend
and https://en.wikipedia.org/wiki/Frontend_and_backend, "backend" is
also used.

I am attaching Google trends stats for search term usage of "backend",
"back-end", and "back end".

It looks like "backend" is more popular at the end.

I will go for it everywhere unless there are objections.

P.S. It really feels a bit silly trying to weigh on this subject.


[-- Attachment #2: backend-stats.png --]
[-- Type: image/png, Size: 66328 bytes --]

[-- Attachment #3: Type: text/plain, Size: 224 bytes --]


-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

  reply	other threads:[~2023-04-06  9:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-06  6:58 2 'echo' bash instructions produce a table Alain.Cochard
2022-11-07  2:31 ` Ihor Radchenko
2022-11-13 20:41   ` Alain.Cochard
2022-11-14  3:59     ` Ihor Radchenko
2022-11-15  6:00       ` [RFC] :var x=list-name should be resolved into simple lists (item1 item2 ...); not nested ((item1) (item2) ...) (was: 2 'echo' bash instructions produce a table) Ihor Radchenko
2022-11-26  1:54         ` Ihor Radchenko
2022-11-16  1:24       ` 2 'echo' bash instructions produce a table Ihor Radchenko
2022-11-21  9:04         ` Ihor Radchenko
2022-11-21  9:05         ` Ihor Radchenko
2022-11-16 16:35       ` Alain.Cochard
2022-11-19 12:28         ` Rudolf Adamkovič
2022-11-20  5:05           ` Ihor Radchenko
2022-11-22  8:16         ` Ihor Radchenko
2022-11-22 19:13           ` Alain.Cochard
2022-11-24  1:55             ` Ihor Radchenko
2022-11-22  8:31         ` [RFC] Backend vs. back-end (was: 2 'echo' bash instructions produce a table) Ihor Radchenko
2023-02-20 10:07           ` Ihor Radchenko
2023-02-20 14:54             ` Alain.Cochard
2023-04-06  9:57               ` Ihor Radchenko [this message]
2023-04-20 12:17                 ` Ihor Radchenko
2023-04-06 23:43           ` Samuel Wales
2022-11-22  8:37         ` [BUG] Make source block auto-completion work for all the loaded babel backends " Ihor Radchenko

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ile9fi3f.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=Alain.Cochard@unistra.fr \
    --cc=emacs-orgmode@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.