Clojurians Log v2

@martinklepsch has joined the channel

there's some prior art towards "live repl" kind of thing in a Lambda: • https://clojutre.org/2016/#distributed-transducers, had the idea or parallel fold, something like this would be neat, to use the parallel nature or lambda, used https://github.com/mhjort/serializable-fn to decorate function definitions to ship new code (as text/forms) for lambdas to execute • me and Chrisophe's hacking on deploying functions: https://clojutre.org/2017/#livecoding-the-cloud, maybe the thing here was no upfront stack, but a lib to lift a function easily to Lambda+API Gateway route, used in-depth bytecode analysis to ship the generated JVM level bytecode + all dependencies, the kind of stuff that Graal does, and hit slight walls there possibly :)

currently thinking something like a "sub repl", like cljs piggieback / shadow-cljs (e.g. (shadow/repl :app)), where you jump into executing forms in Lambda. Haven't though about result accumulation/printing too much yet though 🙂 Limiting concurrency to single Lambda invocation would allow kind of serial experimentation, more concurrency would need a bit more thinking, might be neat to eval code that does a kind of modulo over process identity / concurrency, to do work splitting. Might need a new kind of way of thinking about execution / state persistence. Maybe during process liftime, write context into an atom, and before timeout, serialize it and load on new process boot. Hazy ideas, I hope you don't mind thinking on this out loud, don't want to hijack this channel 😄

on what holy-lambda lacks now, maybe ClojureScript/node would be a good addition, I guess that's on a todo list even 🙂