Started the Sun Eater series. More than a bit inspired by Dune, but the language just drips like honey.
just the overall flow of how the author writes, it's very pleasant.
I'll keep an eye out for specific passages
got a favourite passage to exemplify that honey dripping? I'm intrigued.
Also, I'm nearing the end of my current reading (listening) endeavor …
Morning
morning 🙂
Possibly controversial take: we mostly write libraries where we leave state and resource handling to the user. A function produces a little machine, but unless the user "defs" or otherwise catches the little machine, the user has no means of recovering the little machine, and is possibly forced to restart their beloved REPL. (org.httpkit.server/run-server (constantly {:status 200 :body "okayyy..."}) {:port 4040}) is a quick example, now your port 4040 is lost forever unless you caught the instance!
I really like how in Chrome's js-console, I can right-click a result from a previous evaluation and just mark "Store as a global variable".
As far as I know, Clojure's repl only have *1 ...*3
Would be cool if the repl client had some sort of contract with these kinds of fns. Say that a fn like that had some meta on it that gave the repl a possible var-name to store it under?
Or just some meta telling the repl to keep a handle to it.
Yeah
I'm also thinking from the library development side. If the library can list and close resources it's started, the user doesn't have to care as much.
But 1. Start / Stop logic is boilerplaty 2. And it's generally nicer to have it in the app code — then you can go to the def/defonce and eval the var symbol.
Good fresh water morning