barathr

Sounds good.

Happy to discuss further if it's of interest.

This is really clever and elegant. Thanks for building it.

This is a neat idea, and one that I frequently find a need for. (I was curious how it'd work, so I copied and pasted the description and screenshot of the UI into Claude and in two prompts it built a working React app prototype.)

Any chance that Threlte makes it easy to do view-independent rendering / ray tracing? Basically if you have many surfaces in your scene and you want to not just visualize the scene but find out how much light is arriving at any surface (even ones the camera currently can't see), is that something Threlte enables?

I'm interested in computing light that trees receive and want to be able to visualize it but also have even leaves that aren't in view to continue to receive light during the simulation.

Amazing how prescient her talk is on so many levels -- things that in 1982 there were likely few folks really thinking about deeply and holistically.

What we're hoping for (and is the theme of the piece) is that we are and can and should be both and more -- taxable citizens, members of illegible communities, and many more things. It's a both-and perspective -- life is and should be composed of many overlapping systems.

It's a general-audience essay, not one targeted towards the HN community. So unfortunately there's little opportunity to delve any deeper into what specific data structures are involved in holding the data and the difference that might make. There are data structures underneath in the excerpt you pulled out and they're so common in code that we don't even notice it. (Even something as simple as this: certain data structures are better for finding recent / first items and others are better for finding "top" / largest items. That has implications that ripple upward and can skew what users are shown.) It would be nice to consider the differences in how different data structures store data and their broader implications.