@ProgrammerDude
Account based inGermany
About this account
- Account based in
- Germany
- Connected via
- Germany App Store
Account-level information from X, not a live location or the device used for a specific post.
I perform @nixos_org witchcraft at @mercury
Joined January 2010
- Tweets19.2K
- Following2K
- Followers5.5K
- Likes13.3K
I just checked and pointy end is indeed up and flamey end is indeed down! I can’t believe how close we were able to get!!
It would be very funny if I end up meeting @dhh at Starbase the coming days
This is why DHH is so freaking annoying.. not only does he not read what his bot writes . He also doesn’t read how his bot writes or asks the bot how it got to the solution. No interest in intellect or engagement . Bot would’ve told him asm is not load-bearing.
Why shows to me that he’s just a bad prompter. A good AI user uses AI to learn so that next time you can prompt even better. Sure you don’t have to read the code. But you must absolutely read and write the prompts. And extract the context and understanding how things work
Peoples thoughts on restate.dev ?
This was built in collaboration with us at @mercury after me complaining over and over again that outages due to space leaks in Haskell are a PITA to the respond to. No more!
Well-Typed are happy to announce Eventlog Live, which streams real-time telemetry from any Haskell application to any observability platform that supports the OpenTelemetry protocol! well-typed.com/blog/2026/09/…
90% of AWS’ products are just there to mask and fix issues of other products.
Does anybody in that company talk to each other or no?
Pragmatic way to solve this:
Have stdenv.mkDerivation throw if you actively pull in an unfree dependency whilst you claim your derivation is free.
But if you are evaluating an unfree package directly you probably know that already and no reason for us to block that
buck2 recently added cgroup awareness to their scheduler which freezes or kills build Actions when under memory pressure. It works extremely well at making my agent not choke my laptop with concurrent builds
one of the problems with rust dev that mr-boxington fixes (or at least mitigates) is a bunch of agents running and hitting OOM while also permitting cargo builds to run in parallel (even in the same worktree). it has a scheduler that hands out permits to keep cpu/memory under control.
it's not perfect and you can definitely still hit OOM issues. one reason for this is it monitors cargo processes but your agents may be running tests or doing other work that is outside of its scheduler.
in the next release I'm adding optional support for `cargo test` executions to run within the scheduler. it does this by running rusage and recording how much cpu/memory the tests take.
anyhow, if you use mr-boxington, definitely send some ideas on how we could continue to improve this.
