On Mon, Nov 11, 2024 at 01:04:08PM +0100, Hans Hagen wrote:
> On 11/11/2024 12:17 PM, Vítek Starý Novotný wrote:
> > ConTeXt, likewise, is Lua-focused, with users more accustomed to Lua
> > than to TeX macros.
>
> That's not true. Most users use the tex input language. They might kick in
> soem metapost (metafun) and lua, or use a mix with lua when data has to be
> massaged, but coding mostly text document input in a programming language
> like lua is counter productive and especially for more complex and rich
> coding also a pain (think passing arguments and evaluation in a function
> based language with multiple layers of nesting).

I am sure they use TeX for the document markup but generally, ConTeXt
users seem more comfortable setting up code that calls out to Lua
and to external tools. In contrast, LaTeX users seem to rely more
on packages and expect TeX code with little-to-no visible Lua code.

Therefore, whereas a LaTeX user might expect the `markdown` package to
provide an environment \begin{markdown} ... \end{markdown} that does the
expected thing (even with legacy engines such as pdfTeX), a ConTeXt user
can be more reasonably expected to set up a buffer that will filter the
buffered text through the library `markdown.lua` themselves.

It helps that ConTeXt provides format-level primitives such as buffers,
whereas LaTeX seems more focused on the division of labor between
programmers and authors, where authors should mostly rely on packages
and only ever use high-level document markup.

Best,
Vitek

> Hans
>
> -----------------------------------------------------------------
>                                           Hans Hagen | PRAGMA ADE
>               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -----------------------------------------------------------------

Attachment: signature.asc
Description: PGP signature

_______________________________________________
dev-context mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to