Earlier quoted context omitted.
Wow, now I'm curious about the language. Looks like made-up gibberish at first sight: ++ lax :: lax:as:go |_ [her=ship dur=dore] :: per client ++ cluy :: cluy:lax:as:go ^- [p=life q=gens r=acru] :: client crypto ?~ lew.wod.dur !! ?. =(fak.ton r.i.lew.wod.dur) ~|([%client-wrong-fake her] !!) :+ p.p.q.i.lew.wod.dur q.q.i.lew.wod.dur (haul r.q.i.lew.wod.dur) ::
Suppose we wrote this with keywords. I can't stomach a naked keyword so I'll put a colon on the front. We might write: :function lax { :object :tuple{her: ship dur: dore} { :function cluy { :produce :tuple{p: life q: gens r: acru} :ifno lew.wod.dur :error :unless (equals fak.ton r.i.lew.wod.dur) { :record :tuple{%client-wrong-fake her} :error } :then { :tuple { p.p.q.i.lew.wod.dur q.q.i.lew.wod.dur (haul r.q.i.lew.wo…
For what criteria of 'better'?
I can't really present an argument either way since I'm not familiar enough with the language, but it does seem like it requires a fairly high amount of cognitive overhead for... I'm not sure exactly. Keystrokes?
There is something to be said about the efficiency of glyph-based writing systems like kanji, so APL might've been on to something, but overloading common ascii characters and creating meaningless words? That seems like a lot of noise for brains without extraordinary working memory to filter out on a regular basis.
I'm sure thinking and writing in it are fine (even brainfuck isn't difficult to write), but for something intending to be the backbone of the internet, I would've assumed maintainability to have been the most important design goal.