yeah, i definitely feel like we're currently in a very time-sparse model for review, when a lot of changes can be condensed locally. it'd reduce a lot of friction and also save a lot of compute costs if we were able to left-shift a lot of our current review work
Looks cool! Chapters is definitely something I've been angling towards as well. Any plans on going in the other direction (directly incorporating rich feedback/review into the agent loop through Stage)?
I can’t speak for the Go bindings, but using the Rust crate has been pretty clean. Haven’t really felt the need to dip into deserializing raw .scip file in the time that I’ve been working with SCIP.
In your experience, what’s the best way to increase signal? I feel as though a lot of devs struggle with the initial process of getting past screening, drawing attention to projects, etc.
Woah, I had this exact idea, down to the tunneling and local machine! I basically just coded up a Tailscale + caffeinate harness for my agents and it's been working super well. Your UI looks great though, glad to see more players in this space!
I’m new to CRDTs, but could we clean up tombstones if all replicas acknowledge? Not too sure, but could we persist snapshots of state at certain “compaction” points?
Huh, the checkpoint primitive is something that I've been thinking about for a while, excited to see how it's implemented in the CLI. Git-compatible structures seem to be a pretty big pull whenever they're talking about context management.
This is hilarious lol, it’ll be any day now before we get a full JS kernel. Garbage collection could be an obstacle, but I know there have been some kernels written in Go/Java before
Makes sense, it feels like this just codifies a lot of implicit standards wrt OSS contribution which is great to see. I do wonder if we'll ever see a tangible "reputation" metric used for contribs, or if it'd even be useful at all. Seems like the core tension now is just the ease of pumping out slop vs the responsibility of ownership of code/consideration for project maintainers.
Wow, the shelf UI is a real throwback to the old iBooks shelf design! Looks great. +1 on the bounding box issue, it takes me out of the flow when accidentally triggering a book below the current shelf.
Highly recommend writing a BitTorrent client. The spec is easy to grok, it has a bunch of fun subproblems that you can go as deep or as shallow as you want into, and it's super rewarding being able to download something like the Debian kernel after all of your hard work. Magnet links and seeding are two fun things to tackle post basic implementation. It also got me really interested in peer to peer systems and DHTs like Chord!
I think for me, the difference really comes down to how much ownership I want to take in regards to the project. If it’s something like a custom kernel that I’m building, the real fun is in reading through docs, learning about systems, and trying to craft the perfect abstractions; but if it’s wiring up a simple pipeline that sends me a text whenever my bus arrives, I’m happy to let an LLM crank that out for me.
I’ve realized that a lot of my coding is on this personal satisfaction vs utility matrix and llms let me focus a lot more energy onto high satisfaction projects
Wow, looks really nice, and the README’s super comprehensive. I don’t know if I missed it or not, but do you support inter-note link navigation (like Obsidian WikiLinks)? I know markdown-oxide did this with LSP actions, but I’d love to know more about your plans for navigation/lsp-like features, if any
OCaml’s REPL is lovely, but I found myself having some friction with initial startup. The build/package system was pretty convoluted, and I ended up choosing JS’s Core stdlib for my needs (a simple compiler). With the new multicore release it’d be cool to see OCaml in some more practical projects!
I love this book! I worked through a bunch of it during my winter break last year and found the incremental teaching style extremely rewarding. For readers of the book, Sandler’s reference OCaml implementation is super useful for getting your bearings. I was kind of thrown off by the use of TACKY as an IR, but it was nice to have a solid reference as I worked through the book. For those more experienced with compilers: what are some good resources for stuff like SSA and optimisation? I’ve looked at some of the resources here https://bernsteinbear.com/pl-resources/ but are there other canonical resources?