1,059 karma · joined June 4, 2012
[ my public key: https://keybase.io/fzakaria; my proof: https://keybase.io/fzakaria/sigs/KyeYEObQNSlKKt-hy6DszIs2uGt7gRou7CzeSZoR6Q8 ]
Vendoring deps is the only true real sane way for large repos
I remember Target funded some earlier Nix work like lorri.
Interestingly, I found operating at this level to have been a necessity if I wanted to fix or write a derivation. Otherwise I would face random errors and be left clueless as to what the problem was.
Writing a derivation builder (nix pill) was illuminating.
If you're also interested I (Farid) also had a follow up where I follow up on how the hashes are calculated. (Using the error to get the hashes also bugged me)
I use it to also create vanity hashes :)
I just wrote about my experience here on a project https://fzakaria.com/2025/01/28/bazel-build-event-protocol-v...
Unnecessary abstraction
Right now I am really liking my kinesis advantage 2 Love the form factor.
I don't understand how absorb works in your example. Why would the commit "z" be affiliated with some random documentation changes you come across and fix in the wip commit.
All that I see is it makes it easier to make small refinements to preciously altered lines ?
Super excited for jj.... Almost want to find a work opportunity to promote it. Been a refreshing tool I've adopted in 2024 I'm happy about.
There were also some nice integrations to pull in commits, doc edits , etc..
I'm kind of intrigued by Mill but I've fallen into the same trap I've observed in others. I'm over indexed in mental capacity in having wasted learning Bazel and it's equivalent systems.
The lift to another system has to be enough to surpass that loss.
"Committing" something as a public trading company has little weight behind it. At the end of the day, they have a fiduciary responsibility to their shareholders and can do any changes in service to that.
I remember there were docs how to onboard a repo to that list.
Is this functionality effectively in-kernel now ?