aplette VS json

There is Aplette which supposedly integrates nicely with other Unix tools. It's a port/update of the earlier openAPL source code, which I think was done by Ken Thompson? Here:

https://github.com/gregfjohnson/aplette

If you're interested in recent developments in array languages, I recommend checking out:

BQN https://mlochbaum.github.io/BQN/

ngn/k https://git.sr.ht/~ngn/k/tree/master/item/readme.txt (Previous discussion: https://news.ycombinator.com/item?id=22009241)

aplette, which is a modernization of Ken Thompson's APL https://github.com/gregfjohnson/aplette (Previous discussion: https://news.ycombinator.com/item?id=21740536)

I'd also recommend checking out J, which isn't a recent development, but has the best syntax out of all array languages, has the best development environments, is the easiest to learn (it has a way to learn it built into the language itself!), and is the only one that treats making GUIs as a first-class feature: jsoftware.com (Has so many previous discussions I just recommend using HN search to find them.)

The chat is biased to Dyalog APL, but a lot of the modern additions Dyalog has made to the language make it (in my opinion) worse as a notation, so ideally don't let it turn you off of the concept of array languages entirely if Dyalog doesn't "click" with you.

If you haven't already, you should also check out Notation as a Tool of Thought, a paper so good it won Iverson the Turing Award:

https://www.eecg.utoronto.ca/~jzhu/csc326/readings/iverson.p...

An example is the 40 line JSON::Tiny::Grammar of the Raku module JSON::Tiny. Raku grammars are analytical grammars. This one corresponds to the grammar of JSON defined by "RFC7159, which is a superset of ECMA-404, in that it permits any value as a top-level JSON string, not just arrays and objects".

For example, the JSON::Tiny grammar uses no backtracking, has almost entirely declarative rules, but leans on the default Turing complete powered top down recursive descent invocation of those rules to drive its predictive parsing.

A `rule` is a `token` with `:sigspace` also enabled (whitespace becomes the same as a call to `<.ws>`).

The only one of those that really looks anything like traditional regexes is the `value:sym` token. (Raku replaced non capturing grouping `(?:…)` with `[…]`, and character classes `[eE]` with `<[eE]>`)

This code was copied from https://github.com/moritz/json/blob/master/lib/JSON/Tiny/Gra... but some parts were simplified to be slightly easier to understand. Mainly I removed the Unicode handling capabilities.

It will generate a tree based structure when you use it.

    my $json = Q:to/END/;

For JSON specifically, here's a simple serializer/deserializer (Grammar, Actions).