Профиль

spr turns local amends + rebases into remote new commits + merges, fwiw. it's the only way I can retain my sanity working on github

they were looking for feedback on hacker news and I couldn't help it

yessss scoped panic hooks would be really great

it is such a fun book to read though. the nesting doll structure is perfect

I should re-read Cloud Atlas

If many other people do something and it works, it is worth understanding how it came to be before doing your own thing. Sometimes you realize your way is better (for example, Oxide racks, unlike even hyperscalers, have network cabling in the back), but it's important to understand what's going on

Reminder that Chesterton's fence is basically the one good conservative idea

yeah

AI slop

my favourite Michael Kalecki quote: “I have found out what economics is; it is the science of confusing stocks with flows”.

great choice by rust to rename "object safety" to the much more intuitive "dyn compatibility (previously known as object safety)"

Also, forcing people to name every branch is unpleasant at best

if you were designing a stacked workflow from first principles, you would focus on atomic/bisectable commits as the unit of work, with interdiffs between versions to guide you. Basically what Gerrit, Phab and numerous other tools do. The lack of engagement with prior art continues to be frustrating

spent some time looking at this last week and was very unimpressed. stacked diffs/patch series don't make nearly as much sense with a new commit + merge workflow as they do with an amend + rebase workflow. jj compat is alao dubious. going to stick with spr

fascinating that the rust standard library also happened to run into soundness issues with allocators unwinding. (This is something I mentioned in my iddqd blog post as an entirely unexpected source of soundness issues that GPT flagged — it is now carefully handled by iddqd)

Guarantee `handle_alloc_error` never unwinds · Issue #834 · rust-lang/libs-teamProposal Problem statement Currently, handle_alloc_error cannot unwind on stable. However, the unstable set_alloc_error_hook API would allow that to change, potentially allowing an unwind to happen...github.com

JESUS H. CHRIST

(I don't actually agree that jj is like being in an interactive rebase... for example, you can't nest git interactive rebases but you can easily do the equivalent with jj)

I didn't say or imply that interactive rebase was good!

interactive rebase is one of the best parts of git ;)

to take a small example, I just glanced through the reports and it flagged a place where an example had a TOCTOU race, and that someone copying this code would repro the TOCTOU. which I mean, sure, it's worth fixing, but also ¯⁠\⁠_⁠(⁠ツ⁠)⁠_⁠/⁠¯