ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: "Hans Åberg" <haberg-1@telia.com>
Cc: ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Latin setupmathematics
Date: Mon, 16 May 2016 10:48:14 +0200	[thread overview]
Message-ID: <23faace2-8dce-f956-a771-e7cea2a75128@wxs.nl> (raw)
In-Reply-To: <0F04C44E-21DA-452C-9C0A-B64098BBFBFD@telia.com>

On 5/16/2016 10:27 AM, Hans Åberg wrote:
>
>> On 16 May 2016, at 01:00, Hans Hagen <pragma@wxs.nl> wrote:
>>
>> On 5/15/2016 11:55 PM, Hans Åberg wrote:
>>>
>>>> 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.
>>
>> just look at how many programming languages are there and will be there (no surprise with billions of people and taste)
>>
>> you see the same with markup languages: people want simple, then need more and so simple becomes more and when not well thought about beforehand simple then becomes ugly and it all starts anew
>
> Indeed computer tend to have natural life cycles, after they have matured, further development becomes difficult.
>
>> interesting tex was flexible enough to survive many decades
>
> Other survivors are C, C++, Scheme. With TeX, change may start as with Lua, only some better syntax for text input.

that always depend on the content; for complex docs tex or xml is ok 
(and best)

> I experimented a bit with giving Guile a C++ API, and then then there is a problem with that that C++ is statically typed whereas Guile is dynamic. For example, Guile does not distinguish statically between different types of numbers: integers, rationals, etc, so the proper way from the point of C++ is to only have open number type. But static typing is important in optimization.
>
> And giving implement traditional function syntax on top of Guile does not work well, because (f, x_1, …, x_k) does not correspond semantically exactly to f(x_1, …, x_n). And there is a problem with the Scheme strict evaluation.
>
> So such issues lead towards to the design of a new language, rather than relying on an already existing.

and then the not foreseen limitations in that language and ugly 
extensions spoil it ... (btw, the nice thing about lua is that it's so 
stable)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
       tel: 038 477 53 69 | 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
___________________________________________________________________________________

  reply	other threads:[~2016-05-16  8:48 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
     [not found]                     ` <f175caa5-45df-5df6-d5a9-5bf9340a6f0d@wxs.nl>
2016-05-16  8:27                       ` Hans Åberg
2016-05-16  8:48                         ` Hans Hagen [this message]
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=23faace2-8dce-f956-a771-e7cea2a75128@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=haberg-1@telia.com \
    --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).