I'm trying to wrap my head around the "magic compression" bit. So literally every namespace lives in a repo somewhere? And even files referenced are just automatically committed to that repository? What am I missing?
Also how does this not create either an enormous tangle of circular references or a huge pile of unused... scrap?
It’s content addressed, so circular references can’t naturally arise. You kind of need to create an ID of some sort and reference that and create some way of looking that up. I didn’t check if they allow for recursive function calls, etc.
The repository/scrap pile of content could be stored in lots of ways that you could choose. I imagine if everyone pushed directly to a global “scrap pile” like IPFS it would end up as a huge pile of unused scrap. Like unison, they’d need to provide some kind of default development environment, but anyone could build additional tooling (kind of like anyone could write a git clone).
Also how does this not create either an enormous tangle of circular references or a huge pile of unused... scrap?