And with all that, Archive is also now able to read .topolets zips and load them into the pages. Making them work with the rest of Archive's look is something I have no idea how to achieve. (1/1)
I modified the algorithm to have background color and hue change on the colors. Same HSL Hue means beautiful coherence. (1/1)
Topolets Processor now has a tool to erase from the pictures. This made sure I could get rid of the dates and scan errors. Now they look flawless. (1/1)
It is a freeing thing to not have to do any setup in advance of just running your program which can describe whole distributed systems. Rather than having to do a bunch of work "out of band" to ensure your compute resources are ready to run the code they need (like building containers, uploading a container image or jarfile somewhere, or whatever else), in the Unison model of distributed computing, you just run the code and whatever dependencies are missing can be sync'd on the fly.
Dependency conflicts are, fundamentally, due to different definitions "competing" for the same names. But why do we care if two different definitions use the same name? We shouldn't. The limitation only arises because definitions are referenced by name. In Unison, definitions are referenced by hash (and the names are just separately stored metadata), so dependency conflicts and the diamond dependency problem are just not a thing.
Moreover, the idea of everything in the language having serialization on their own makes it possible for a storage layer to be typed, not with a separate type system that your program doesn't know about (as in SQL), but as part of your Unison program. That is, values persisted by your program give you back typed references to the storage layer, and you're assured by Unison's type system that when loading that reference you'll get back a value of the expected type.