hoon

This Hoon code is very pretty but the English content of the names is extremely low.

What is the benefit of reinventing computer science from the ground up with nock and hoon?

Or to put it more briefly: a well-designed Nock implementation is not in any way coupled to the Hoon or Arvo layers.

For instance, maybe you rolled your own decrement, so the interpreter can't match it with the jet it uses for stock Hoon decrement.

The actual name syntax is roughly Lisp's - for instance, (my-long-function arg1 arg2) does the same thing (roughly) in Hoon as in Lisp.

I have never heard of it either, but I know some hoon and it makes intuitive sense to me.

A given Nock implementation is intimately coupled to a matched Hoon compiler.

I think Hoon is wonderful [1] because it has both power and predictability.

Here in Australia we have something called 'Anti-hoon laws' which states after three major traffic infringements, your car can be seized (and destroyed/crushed in some cases).

Searching around the repo to try to find out wth `marl` is I found this: The fundamental hoon structure used to generate XML is a manx.

But if you want to come to chat on ~doznec, there are about half a dozen people who can translate hoon and probably can explain in plain English what the fix looks like.

:( This is a bug we had in the hoon chat client on Urbit that has seen various iterations of fixed, not that this is at all helpful, because it is written in hoon it will probably seem like line noise even if I could bisect and show you the commits that fixed it for urbit...

In the "lapidary" Hoon in which most of the kernel is written, facets (variable names, roughly) are meaningless TLV strings, usually CVC (consonant-variable-consonant).

Do you have any examples of what "non-lapidary" Hoon might look like?

As a coder of "various ability and background", I found that Hoon source code was a relaxing joy to read and write after a few weeks of dedicated study.

> I guess the Hoon interpreter is a C program that uses readline "or even readline - this is not readline, it's internal to Arvo"

Hoon's power is in the zoology of runes (Digraphs) and it's predictability is rooted in its homoiconicity.

All of that is written in Hoon, which compiles into Nock.

I find that the programming model you've attached to it --- the Nock/Hoon stuff --- makes it easy to dismiss the work.