I went down the rabbit hole on a side project and ended up building this: Strange Attractors(<a href="https:&#x2F;&#x2F;blog.shashanktomar.com&#x2F;posts&#x2F;strange-attractors" rel="nofollow">https:&#x2F;&#x2F;blog.shashanktomar.com&#x2F;posts&#x2F;strange-attractors</a>). It’s built with three.js.Working on it reminded me of the little &quot;maths for fun&quot; 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.

Show HN: Strange Attractors

Leaker reveals which Pixels are vulnerable to Cellebrite phone hacking

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&#x27;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] <a href="https:&#x2F;&#x2F;github.com&#x2F;oxidecomputer&#x2F;omicron&#x2F;issues&#x2F;9259" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;oxidecomputer&#x2F;omicron&#x2F;issues&#x2F;9259</a>[1] <a href="https:&#x2F;&#x2F;rfd.shared.oxide.computer&#x2F;rfd&#x2F;397" rel="nofollow">https:&#x2F;&#x2F;rfd.shared.oxide.computer&#x2F;rfd&#x2F;397</a>[2] <a href="https:&#x2F;&#x2F;rfd.shared.oxide.computer&#x2F;rfd&#x2F;400" rel="nofollow">https:&#x2F;&#x2F;rfd.shared.oxide.computer&#x2F;rfd&#x2F;400</a>[3] <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=zrv5Cy1R7r4" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=zrv5Cy1R7r4</a>

Futurelock: A subtle risk in async Rust

You can't refuse to be scanned by ICE's facial recognition app, DHS document say

Updated practice for review articles and position papers in ArXiv CS category

Chat Control proposal fails again after public opposition

Hard Rust requirements from May onward

S.A.R.C.A.S.M: Slightly Annoying Rubik's Cube Automatic Solving Machine

SQLite concurrency and why you should care about it

How I stopped worrying and started loving the Assembly

GHC now runs in the browser

Myths Programmers Believe about CPU Caches (2018)

Visible from space, Sudan's bloodied sands expose a massacre of thousands

CharlotteOS – An Experimental Modern Operating System

Studies increasingly find links between air pollutants and dementia

I built my own CityMapper

Frank Gasking on preserving «lost» games

Data centers contribute to high prices as energy bills electrify local politics

Hi all,I’m a longtime Neovim user who’s been EMacs-curious. The hold up for me has been that I’ve been unable to find a source of truth for what’s top-of-the-line as far as plugins are. With Neovim, it’s a safe bet to look at what folks like Folke are doing, but I have struggled to find a similar figure in the Emacs community who gives insight into what’s-what. I know Doom exists, but I want to fully “own” my config and not over complicate it.Thanks!

Ask HN: Where to Begin with "Modern" Emacs?

Austria: Pylons as sculpture for public acceptance of expanding electrification