ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Hans Åberg" <haberg-1@telia.com>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Latin setupmathematics
Date: Sun, 15 May 2016 23:55:38 +0200	[thread overview]
Message-ID: <E330E47B-91DD-4EEE-8958-AECF2DF5B8B2@telia.com> (raw)
In-Reply-To: <d5815d82-f204-5e93-2ff7-0e10b6d7a956@wxs.nl>


> On 15 May 2016, at 23:18, Hans Hagen <pragma@wxs.nl> wrote:
> 
>>> but eventually typesetting will become a niche and end up in the arts but i will probably not live long enough to see that happen
>> 
>> From the point of computer language design, TeX is not very good. One of the pitfalls of macro programming is that it gives the impression of lambda calculus efficiency without having it so one ends up spending a lot of time figuring out trivialities, which is why eventually was added, I gather.
> 
> it's not that bad .. the tex language has a certain charm that one needs to get accustomed to (as does metapost) ... and, combined with lua it's even more fun

Ideally, there should have been only one language with lambda capacity, and better syntax, though it is a problem figuring out what it might be.



___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2016-05-15 21:55 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-14 17:11 Hans Åberg
2016-05-15 13:37 ` Hans Hagen
2016-05-15 14:15   ` Hans Åberg
2016-05-15 14:28   ` Hans Åberg
2016-05-15 14:44     ` Wolfgang Schuster
2016-05-15 16:06       ` Hans Åberg
2016-05-15 16:36       ` Hans Åberg
2016-05-15 17:12         ` Hans Hagen
2016-05-15 17:28           ` Hans Åberg
2016-05-15 18:06             ` Hans Hagen
2016-05-15 18:34               ` Hans Åberg
2016-05-15 17:08     ` Hans Hagen
2016-05-15 17:42       ` Hans Åberg
2016-05-15 17:59         ` Hans Hagen
2016-05-15 18:31           ` Hans Åberg
2016-05-15 18:42             ` Hans Hagen
2016-05-15 20:06               ` Hans Åberg
2016-05-15 21:18                 ` Hans Hagen
2016-05-15 21:55                   ` Hans Åberg [this message]
     [not found]                     ` <f175caa5-45df-5df6-d5a9-5bf9340a6f0d@wxs.nl>
2016-05-16  8:27                       ` Hans Åberg
2016-05-16  8:48                         ` Hans Hagen
2016-05-16  8:59                           ` Hans Åberg
2016-05-16  9:10                             ` Hans Hagen
2016-05-16 12:07                               ` Hans Åberg
2016-06-16 19:15                 ` Hans Åberg
2016-06-16 21:48                   ` Hans Hagen
2016-06-16 23:02                     ` Hans Åberg
2016-06-17  4:20                       ` Alan BRASLAU
2016-06-17  8:15                         ` Hans Åberg

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=E330E47B-91DD-4EEE-8958-AECF2DF5B8B2@telia.com \
    --to=haberg-1@telia.com \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).