From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Philipp Gesang <pgesang@ix.urz.uni-heidelberg.de>
Subject: Re: why lua?
Date: Sat, 18 Dec 2010 14:04:46 +0100 [thread overview]
Message-ID: <4D0CB16E.4030007@wxs.nl> (raw)
In-Reply-To: <AANLkTinNw0J0eNco5XME0hBofXyXMJ+8WKARy3Wbnuyc@mail.gmail.com>
On 18-12-2010 1:50, Philipp A. wrote:
> but don’t get me wrong, i love context and luatext, i just like other
> languages better than lua (you weren’t content with latex and created
> context, so this shouldn’t be alien to you)
Sure, it's just that the core of context will be tex/lua only as it
needs to be portable and mixing languages will not help at that level.
Probably the best way to use other languages in applications of context
/ luatex is to do something lunatic that luigi did, the overhead of
wrapping is probably neglectable. We can look into that around luatex
version 1.0.
For me personally the only reason to look into pyton (or ruby or perl or
php or ...) would be that it's needed in a project but so far i never
had such projects i.e. could choose my own languages (so it was ruby at
some point and lua now). Who knows what the future brings.
Hans
ps. I once read about Icon as language and somehow that one also had
some appeal. I never had a running environment. Smalltalk is also nice,
esp the (original) books (esp the historic one), and Lisp (in relation
to tex) also has some appeal. Live is too short to learn all those
languages and stay fluent in them, i.e. one simply forgets a lot when
usage zeros.
-----------------------------------------------------------------
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-18 13:04 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
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 [this message]
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=4D0CB16E.4030007@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
--cc=pgesang@ix.urz.uni-heidelberg.de \
/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).