I think the coolest aspect about Unison, is that they're trying to reify the concept of a codebase (http://unisonweb.org/2016-09-17/editing.html) into something more than just a collection of lines of source code. You can think of it more like a well-defined object that can be transformed in coherent, strongly-typed ways. Unison identifies everything by a hash, so if you "change" a function definition, you're not actually mutating any state in the codebase, you're introducing a new function with a new hash.
> Unison is a new programming language, [...] similar to Haskell, but with a unique ability to describe entire distributed systems with a single program.
Is this not something that could be done in Haskell by defining a new monad type? Perhaps also a tool to deploy such programs to the cluster would be useful. It seems to me that this paradigm doesn't require a whole new programming language, or that it wouldn't be as ergonomic in Haskell.
The nodes being provisioned are all local nodes, running in the same node container. Obviously we’d like to provision nodes running on other computers, or provision from a managed cloud service (like unison.cloud, coming soon) and/or a P2P mesh of nodes.
And further down on the original linked page there's some more info on something it's using for the distributed system description that I don't believe would be possible in Haskell:
This dynamic transfer / deployment of arbitrary computations is possible because definitions in Unison are identified by a cryptographic hash of their content, including the hashes of all dependencies (the hash is also "nameless" as it isn't affected by naming of variables). ...
> If you look at what programmers spend their time doing when programming (other than thinking of course), it’s actually stuff like:
>
> - Adding imports to the code to be able to resolve names
>
It makes me wonder whether the authors have used a modern IDE in the past ten years.
The video in this page is also showing nothing that hasn't existed for years in pretty much all IDE's under the sun.
What the editor is tackling has some overlap with common IDE features, but it’s taking a deeper approach to addressing them.
You listed one item from a big list of tasks, but the more interesting thing is what’s written after the list about how unison addresses the items.
And before demeaning the creators it may be worth it to look into their background a bit and see if it’s more likely to you that they are unaware of modern IDEs or if it’s possible you haven’t fully grasped some of their ideas yet.
I am well aware of their background (I own their book) and this is precisely why I think they haven't used a lot of IDE's. Actually, these past years, I've heard a few times from one of them claiming that with a good language, one doesn't need an IDE.
Distributing arbitrary lambdas and lazy computation of any sort is extremely difficult in GHC Haskell, hence the complexity and limitations of cloud Haskell. Unison makes a number of design choices to support distributed lazy computations.
Hi folks, I’m one of the authors of Unison (Programming Language). Didn’t expect to see this on HN, but happy to try to answer questions about our pre-alpha-release language :)
This looks very promising. I'm curious though, is there any authentication mechanism here? If I have Unison installed does it start a listener and execute whatever code is sent to it?
> This dynamic transfer / deployment of arbitrary computations is possible because definitions in Unison are identified by a cryptographic hash of their content, including the hashes of all dependencies (the hash is also "nameless" as it isn't affected by naming of variables).
> To transfer a computation, we send it to the recipient, and the recipient checks to see if the computation references any unknown hashes. Any unknown hashes are synced to the recipient before the transfer completes and the computation proceeds.
That's fair, but it was written by Ben Pierce of the FP research community. It's nice not to have two projects named the same thing within the same community.
