lab notes
I'm a little indisposed this week, but I did find some time here and there to do research into effects. I spent the time reading and watching a talk about effects by Oleg Kiselyov. The short version is that side-effects can be formulated as a communication protocol between
lab notes
I'm back, after a little hiatus from writing the notes. Last time, I discovered that I should have been looking more deeply into other reactive models before I embarked on a functional component (React-like) model to model data pipelines. The impedance mismatch should have been indicative that something
lab notes
Last week, I started looking at Signals. When I stepped back and looked at the entire front-end ecosystem, it seemed like many of them outside of React (Solid, Vue, Svelte, Preact), converged on some variation of Signals. There is even a Javascript proposal to include Signals in the language. Given
lab notes
One of my main goals is to make non-CRUD backend pipelines more visible. I didn't think nodes and wires programming was the way to go, but unconsciously, I envisioned just showing the results of a cell next to the cell, like regular computational notebooks. But my underlying assumption
lab notes
I've been a bit anxious about the pace of progress these last three weeks. I wanted to strike a balance between making practical progress and having a sound basis. This last week, I struggled with breaking from structured programming. * What do algebraic effects buy you? * What is the
lab notes
This past week, I worked through more confusion on my part. * Consolidated the representation of an algebraic effect with the React-like components (Fibers) * Worked out a solution for resuming fibers after getting a result back from from the algebraic effect. (Then block) * Use a data description of all cells (Epx)
lab notes
Last week, I merged the runtime worker into the kernel worker. Originally, I wanted that to run multiple kernels at once, so users can run languages in a mix of cells, or they can run more than one cell in parallel. It was too hard to trace execution over a
lab notes
I fell short this week in that I didn't do what I said I was going to do. Instead, of writing code, I went down the incremental rabbit hole. It was innocuous at first, but ended up being a full deep dive, mostly into the work of Steven
lab notes
For a while now, I've been circling the drain on the Tools for Thought space and all the topics related to it. One large topic is reactivity, and not too far behind is incremental computation. They're two sides to a coin, so it's hard
lab notes
I spent most of the week getting a basic algebraic effects runtime working. The initial version is single-threaded, synchronous, no typing, with a single yield from handlers. For now, it's good enough for building the proverbial skateboard. Only during implementation did I run into design questions I wouldn&
lab notes
My progress on Crafting Interpreters halted when I was researching how Algebraic Effects were implemented, once I realized that I might not need all the gory details. The part I wanted to get to was understanding how closures were implemented, especially if they were relevant to getting Algebraic Effects to
lab notes
The notebook that I want to build and use has pure functional cells. Functional cells are where the output only depends on the input. * No need to figure out the correct execution order for the notebook cells to get it in a working state. * For any change, only dependent cells