On 5/18/26 7:11 PM, Thomas McGuire wrote:
> Include me on the invite.
>
> One thing I have done to help Claude code is to take the some of
> documents that come with the J interpreter and convert them into
> Markdown. That helps reduce the processing on the LLM side since they
> don't have to deal with PDFs which can take time. So I have a docs
> directory that I didn't put under Git because though it's freely
> provided it is copyrighted material so that would be something to
> discuss. Can we produce a set of J documentation tailored for LLMs.
I'm an anti-AI luddite, so please don't invite me to the meeting.
However, an offline text version of the J documentation would be
helpful as a human user. At least, all of NuVoc, not just a
cheatsheet. An offline download of the NuVoc wiki HTML pages would be a
good start. I'm not always online.
The February discussion about "help and man" between Jan-Pieter Jacobs
and Eric Iverson is a promising step in that direction when you know
what to search for. But complete text serves serendipity.
IMO, the J documentation is very good once you learn how to read it. I
believe it is very terse because it was written with the expectation
that users have and are willing to put in the effort to understand it.
I appreciate the brevity compared to the Python docs, and I wouldn't
want the user-facing docs to balloon to provide training material for LLMs.
On 5/18/26 6:51 PM, 'Pascal Jasmin' via forum wrote:
> One idea is an intermediate language. The above expression could be written as [dyad verb *][adverb returns verb /][adverb returns verb ([monad verb -:][conjunction returns verb @])] 1 2 3
Putting my elitist gatekeeper hat on, "notation as a tool for thought"
is for my thoughts, not a machine's. Once you learn (or lookup) the
properties of a primitive, such annotations aren't necessary.
That said, it would be a win when supporting LLMs also helps human users
learn J without LLMs. A modifier or verb that executes/parses some code
and outputs an annotated IL could be useful for humans trying to
understand a line of unfamiliar code. Like a text-only version of
dissect, or how 13&: transforms code into a tacit form.
-Remington
PS. I admire the array language family for the amount of human thought
that has gone into the design and implementation, how much effort the
users put into learning them, and how much the community teaches. Maybe
something good will come out of LLMs, but I will be sad it it's mostly
used to circumvent real learning and teaching.