From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Jonas Stein <news@jonasstein.de>
Subject: Re: why lua?
Date: Fri, 17 Dec 2010 23:48:20 +0100 [thread overview]
Message-ID: <4D0BE8B4.4090203@wxs.nl> (raw)
In-Reply-To: <vmbst7-pc2.ln1@news.jonasstein.de>
On 17-12-2010 4:20, Jonas Stein wrote:
> i'd like to make a small presentation for friends about
> context.
> Why do we use lua and not python or perl or...
> Where can i find the features for lua for this job?
you can find arguments in presentations and articles and mk.pdf
- nice language (pascal like, nu obscure $characters, tolerant spacing)
- easy to learn and no complex concepts
- good manual that covers all
- mature when we started using it
- small footprint and no truckload of libs to carry along (packaging tex
is already enough work)
- pretty fast and efficient
- no feature creep, proper academic research project, tightly managed
- it fits tex pretty well
- designed with embedding in mind
- most of all: we like it
(I first ran into lua when I was playing with scite's extension
mechanism and immediately thought of how nice it would be to have it in
tex. Hartmut made the first variant that gave access to registers and
provided printing to tex, then Taco stepped in and fundamental opening
up started etc etc etc)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-12-17 22:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-17 15:20 Jonas Stein
2010-12-17 21:46 ` Martin Schröder
2010-12-17 22:35 ` Philipp A.
2010-12-17 22:51 ` Hans Hagen
2010-12-18 8:35 ` luigi scarso
2010-12-17 22:48 ` Hans Hagen [this message]
2010-12-17 23:27 ` Philipp Gesang
2010-12-17 23:46 ` Hans Hagen
2010-12-18 0:50 ` Philipp A.
2010-12-18 5:56 ` Aditya Mahajan
2010-12-18 11:03 ` Philipp Gesang
2010-12-18 11:35 ` Hans Hagen
2010-12-18 13:06 ` Philipp Gesang
2010-12-18 13:20 ` Hans Hagen
2010-12-18 14:17 ` Philipp Gesang
2010-12-18 18:54 ` Hans Hagen
2010-12-18 11:31 ` Taco Hoekwater
2010-12-18 13:04 ` Hans Hagen
2010-12-18 13:18 ` luigi scarso
2010-12-18 13:24 ` Hans Hagen
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=4D0BE8B4.4090203@wxs.nl \
--to=pragma@wxs.nl \
--cc=news@jonasstein.de \
--cc=ntg-context@ntg.nl \
/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 NNTP newsgroup(s).