all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-devel@gnu.org, Phillip Lord <phillip.lord@russet.org.uk>
Subject: Re: emacs-26 3fc05cf: Scripts to automate windows binary distribution
Date: Wed, 25 Oct 2017 10:53:33 +0000	[thread overview]
Message-ID: <CAFyQvY1HargHhg8YTTAxLPqFCVSDAhzAwEcAOX16uK9SuYnjJw@mail.gmail.com> (raw)
In-Reply-To: <87lgjzfs6c.fsf@gmx.de>

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

On Wed, Oct 25, 2017, 6:17 AM Michael Albinus <michael.albinus@gmx.de>
wrote:

>
> If it were me, I would have taken Perl, I don't speak Python. Other
> people would prefer Guile.
>
> Before we continue with this, I would like to see a general
> agreement. Or at least a go by the maintainers.
>
> (Pls ignore this, if it was discussed and decided already)
>
> The GNU Coding Standards claim:
>
> "The standard extensibility interpreter for GNU software is Guile
> (<http://www.gnu.org/software/guile/>), which implements the language
> Scheme (an especially clean and simple dialect of Lisp).  [...]  We
> don't reject programs written in other "scripting languages" such as
> Perl and Python, but using Guile is the path that will lead to overall
> consistency of the GNU system."
>
> <https://www.gnu.org/prep/standards/standards.txt>
>

Just a bystander's observation:

It would be bad if this contribution is reverted *just because* the script
is written in Python. I have gone through pain in real world where just
because the upper management doesn't like one language, stuff written in
that language has to be rewritten in another. In my experience, it's simply
a waste of time, demoralizing, and a source for introduction of new bugs.

While the "introduction of bugs" might not apply to this 1 standalone
script, it would be nice if the same bike shedding doesn't happen in the
Emacs world too.

I code in Perl, Python, Bash and other scripts. While I might have a
preference to work with one over others, it's best to keep on maintaining
the scripts written in their original languages.

If Phil is actually proficient in Guile too, then may be rewriting that
script in Guile makes some sense to support the Gnu Coding standards. But
if he is not, then I believe it will be a waste of time and loss of
motivation.

> --

Kaushal Modi

[-- Attachment #2: Type: text/html, Size: 2756 bytes --]

  reply	other threads:[~2017-10-25 10:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20171024173456.23065.52677@vcs0.savannah.gnu.org>
     [not found] ` <20171024173457.C45BE2031F@vcs0.savannah.gnu.org>
2017-10-25  7:27   ` emacs-26 3fc05cf: Scripts to automate windows binary distribution Michael Albinus
2017-10-25  8:37     ` Phillip Lord
2017-10-25 10:16       ` Michael Albinus
2017-10-25 10:53         ` Kaushal Modi [this message]
2017-10-25 11:06           ` Michael Albinus
2017-10-25 14:44         ` Eli Zaretskii
2017-10-25 14:59           ` Michael Albinus
2017-10-25 15:08             ` Óscar Fuentes
2017-10-25 15:19             ` Eli Zaretskii
2017-10-25 15:27               ` Michael Albinus
2017-10-25 11:03       ` Noam Postavsky
2017-10-25 15:42         ` Phillip Lord
2017-10-25 12:11     ` Stefan Monnier
2017-10-25 15:45       ` Phillip Lord
2017-10-26  3:42     ` Richard Stallman

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=CAFyQvY1HargHhg8YTTAxLPqFCVSDAhzAwEcAOX16uK9SuYnjJw@mail.gmail.com \
    --to=kaushal.modi@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=michael.albinus@gmx.de \
    --cc=phillip.lord@russet.org.uk \
    /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.