Show HN: Strange Attractors
338 by shashanktomar | 40 comments on Hacker News.
I went down the rabbit hole on a side project and ended up building this: Strange Attractors( https://ift.tt/CRM9zNT ). It’s built with three.js. Working on it reminded me of the little "maths for fun" exercises I used to do while learning programming in early days. Just trying things out, getting fascinated and geeky, and being surprised by the results. I spent way too much time on this, but it was extreme fun. My favorite part: someone pointed me to the Simone Attractor on Threads. It is a 2D attractor and I asked GPT to extrapolate it to 3D, not sure if it’s mathematically correct, but it’s the coolest by far. I have left all the params configurable, so give it a try. I called it Simone (Maybe). If you like math-art experiments, check it out. Would love feedback, especially from folks who know more about the math side.
Saturday, November 1, 2025
Futurelock: A subtle risk in async Rust
Futurelock: A subtle risk in async Rust
283 by bcantrill | 126 comments on Hacker News.
This RFD describes our distillation of a really gnarly issue that we hit in the Oxide control plane.[0] Not unlike our discovery of the async cancellation issue[1][2][3], this is larger than the issue itself -- and worse, the program that hits futurelock is correct from the programmer's point of view. Fortunately, the surface area here is smaller than that of async cancellation and the conditions required to hit it can be relatively easily mitigated. Still, this is a pretty deep issue -- and something that took some very seasoned Rust hands quite a while to find. [0] https://ift.tt/tWHKCFY [1] https://ift.tt/dtZcqjp [2] https://ift.tt/OaX9UHj [3] https://www.youtube.com/watch?v=zrv5Cy1R7r4
283 by bcantrill | 126 comments on Hacker News.
This RFD describes our distillation of a really gnarly issue that we hit in the Oxide control plane.[0] Not unlike our discovery of the async cancellation issue[1][2][3], this is larger than the issue itself -- and worse, the program that hits futurelock is correct from the programmer's point of view. Fortunately, the surface area here is smaller than that of async cancellation and the conditions required to hit it can be relatively easily mitigated. Still, this is a pretty deep issue -- and something that took some very seasoned Rust hands quite a while to find. [0] https://ift.tt/tWHKCFY [1] https://ift.tt/dtZcqjp [2] https://ift.tt/OaX9UHj [3] https://www.youtube.com/watch?v=zrv5Cy1R7r4
Subscribe to:
Comments (Atom)