thundersnap v0.01: an undo button for everything
18 points by jbauer
18 points by jbauer
Absolutely love the idea here. I'm not going to have the bandwidth to play with it anytime just soon, but will certainly check back in as it matures.
I feel the same! In fact, it feels like for some time now, we've had what i assume might be building blocks that could serve as conceptual dependencies for this "undo button" concept...in foundational systems like ZFS, BTRFS snapshots, NixOS, containers, etc. I'm not going to state that i am an expert in any of those techs...but it does feel like maybe now or soon, it will be prime time for such a system-wide "undo button". I'll come back to this as it matures, and look forward to playing with it then.
As NixOS rollbacks teach us, the hard part is:
Excellent point! I hadn't learned that through NixOS, but you're so right!
Well you mentioned NixOS and BtrFS… I am not sure I have ever learned this as a point separate from «managing persistent data is often complicated», but immutable-data-structure-style systems are quite good at taking away all excuses for not looking directly at the question of data migrations. No, it is not the downgrade of libc that will go wrong, downgradfe of libc works perfectly with just one reboot!
Seems to be slop: https://github.com/tailscale/thundersnap/blob/fbeaf1fd0c1a1ab35379749f5d6e5f929941622e/CLAUDE.md
That is pretty basic, though. This concept of calling a project slop because it has a CLAUDE.md is weird to me. You can definitely use AI to supercharge yourself on projects and it not be slop.
That said, having AI make commits for me seems icky as well, so it having info about git/jj is interesting.