public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Frysk List <frysk@sourceware.org>
Subject: Re: Roadmap beginnings
Date: Fri, 11 Jul 2008 21:37:00 -0000	[thread overview]
Message-ID: <m3r6a0cdd5.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20080711205531.GA15721@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Fri\, 11 Jul 2008 22\:55\:31 +0200")

>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:

Thanks for sending this to the list.
Open critique is important.

Tom> based on Python.  From our perspective, Python is the best
Tom> choice because it is popular and generally acceptable.

Jan> This is already your personal bias, it may be worth to design the
Jan> scripting support easy enough to add more language bindings there
Jan> (such as Perl XS).  (I do not track your GDB patches to say more
Jan> about them.)

Yeah.  This is my bias -- though FWIW I personally am not a big Python
fan.

There are two parts to this idea: one scripting language, and the
particular choice.

Why one language?  I think the most important reason to prefer a
single scripting language is that this enables an ecosystem of useful
scripts.

Why Python?  Python is popular at Red Hat and beyond, and is more or
less a critical part of the distro.  I think it is fair to describe it
as the de facto default scripting language choice at Red Hat.

Finally, I think projects that try to be scripting-language-neutral
often fail to be good at any of them.


Kinda OT, but: the choice of Python for gdb has more or less the same
rationale; but there I didn't pick it -- I just picked up Volodya's
initial code, and I think he followed the outcome of a discussion on
the gdb list in early 2007.

Tom

  reply	other threads:[~2008-07-11 21:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-11 19:53 Tom Tromey
2008-07-11 20:56 ` Jan Kratochvil
2008-07-11 21:37   ` Tom Tromey [this message]
2008-07-11 21:54     ` Daniel Jacobowitz
2008-07-11 23:11   ` Kris Van Hees
2008-07-11 21:53 ` Daniel Jacobowitz
2008-07-14 16:34   ` Tom Tromey
2008-07-14 16:45     ` Daniel Jacobowitz
2008-07-14 16:58       ` Phil Muldoon
2008-07-14 17:09         ` Daniel Jacobowitz
2008-07-14 17:19     ` Ian Lance Taylor
2008-07-14 17:34       ` Daniel Jacobowitz
2008-07-14 18:04         ` Tom Tromey
2008-07-14 18:12           ` Daniel Jacobowitz
2008-07-14 18:11         ` Ian Lance Taylor
2008-07-14 17:35       ` Tom Tromey
2008-07-14 18:13         ` Ian Lance Taylor
2008-07-22 20:29   ` Debugger Work (Was: Roadmap beginnings) Tom Tromey
2008-07-11 22:48 ` Roadmap beginnings Phil Muldoon

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=m3r6a0cdd5.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=frysk@sourceware.org \
    --cc=jan.kratochvil@redhat.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.
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).