Event JSON
{
"id": "18a95248fb0fbe5135333e39d4d5a3603438113eb9303b442dcdacf10284fc03",
"pubkey": "681d02ade973883f419f143e7c5b8a3f1f13dd585acd936353d8b39df86b1a9a",
"created_at": 1770905574,
"kind": 1,
"tags": [
[
"t",
"haskell"
],
[
"t",
"clojure"
],
[
"t",
"wisp"
],
[
"proxy",
"https://merveilles.town/@aartaka/116058067698811628",
"web"
],
[
"t",
"commonlisp"
],
[
"proxy",
"https://merveilles.town/users/aartaka/statuses/116058067698811628",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://merveilles.town/users/aartaka/statuses/116058067698811628",
"pink.momostr"
],
[
"-"
]
],
"content": "I’m uneasy about chaining / threading operators, be it #Haskell’s $, #Wisp colon, #Clojure arrows, or my own #CommonLisp #/ operator from \u003chttps://codeberg/aartaka/lin-edi-table\u003e.\n\nThese seem to restrict the code in what it can do. With dirty imperative or functional code, you can insert new forms literally everywhere. But with these operators you have to come up with strategies to compose things properly.\n\nWhich is not a problem with Clojure, because at least built-ins are designed with threading in mind. But it’s much harder in brown field langs like CL.\n\nThis post was brought to you by refactoring a complex seven-stage threading in Clojure.",
"sig": "b0583af155dbe90f117e5376e79ec19327521834f5b985d220668219ca64f905bd4ae730fb972b0e4c72aa03c942b4eeb85921dc312a1293cf58414814f50620"
}