> From what I understand, Unison has very little in common with Scrapscript.
I think you should read up on Unison a bit more, I see a lot of overlap.
Both identify code with hashes, and implement code sharing through hash based syncing.
Builtin serialization is also present in both, and both are very Haskell inspired.
One difference I see is the sharing mechanism, where Unison has a local sqlite repository and tooling for uploading, while Scrapscript seems to be built more around IPFS. But that seems like an implementation detail rather than a fundemantal difference.
Unison supports algebraic effects, aka abilities with handlers, which is a much more powerful and general concept than the platforms in Roc.
I think ergonomics and practicality could use more consideration when discussing new languages. A language exists in an ecosystem.
At a glance to me, Scrapscript looks very traditional and easy to grok from a regular programmers perspective, there are build steps, you can use an IDE or editor etc.
Unison feels more like "Smalltalk Squeak" and Scrapscript feels more like "GNU Smalltalk". Come live in our new world, or integrate new stuff into your existing world kind of vibe.
I think you should read up on Unison a bit more, I see a lot of overlap.
Both identify code with hashes, and implement code sharing through hash based syncing. Builtin serialization is also present in both, and both are very Haskell inspired.
One difference I see is the sharing mechanism, where Unison has a local sqlite repository and tooling for uploading, while Scrapscript seems to be built more around IPFS. But that seems like an implementation detail rather than a fundemantal difference.
Unison supports algebraic effects, aka abilities with handlers, which is a much more powerful and general concept than the platforms in Roc.