> Scrapscript solves the software sharability problem.<p>> it’s JSON with types and functions and hashed references<p>> it’s tiny Haskell with extreme syntactic consistency<p>Content-addressability is one of the main features of Unison [1]. How do the languages compare? Why did you feel the need to create a new language (especially since both have a strong Haskell flavor).<p>I'm guessing lots of people will have these questions so it could be good to mention Unison somewhere in your materials. The language seems to have big goals, so it doesn't seem that you are working on it "just for fun" :-).<p>Are there other "content-addressable" languages out there other than these two?<p>--<p>1: <a href="https://www.unison-lang.org/" rel="nofollow">https://www.unison-lang.org/</a>
The web site appears to claim that this solves interoperability between systems. I don't understand how. What enables one system to understand content coming out of another? For example, let's say you have two medical devices sharing patient data. Will scrapscript make it possible for them to create a mapping between the information models of the two systems?
So, (and this is five minutes playing here no deep dive), content-addressable is taken Seriously here.<p>Each expression is a hash of (its ancestors - not too sure) but the implication is sort of the git dag is built into the language. Looks like that has deepmimplications for releases, deployments, inspecting code chnages<p>There is an implication that my-labcorp is using scrapscript. Which is interesting as it seems to be a health based platform - tracking and dealing with test results, X-ray images etc etc<p>So I love committing to one of the most basic CS concepts (cryptographic hashes)<p>And I love the implications for code management. What I am not sure is why that helps with things like labcorp platform - I also love those implications (encrypt and store and just shuffle that data) because cannot any language use the concepts ?
I am interested in this as a replacement for bash scripts<p>The killer feature would be pulling in other scripts as libraries (they may be published anywhere) but I can lock down the hash of these dependencies inside of my script file.<p>Is this possible?
As the author of another language with uses content addressable code for all source code (also to aid in shareable code - <a href="https://yazz.com/app/homepage.html" rel="nofollow">https://yazz.com/app/homepage.html</a>) I feel that it is really good to see that projects such as ScrapScript use this technique. Well done guys!
Lots of amazing ideas here! One more that would be great is 'sandboxing' if a program can use network/filesystem/etc, then I would feel safe to run any random scrap if I knew I would get some sort of oauth-looking screen that said what it wanted to access.