Where Unison is headed by @Paul Chiusano

This is a long post with a lot of details of what we're thinking for the future, so here's a summary:

1. Keep keep improving the core language, runtime, and tooling. Examples: adding an FFI to Unison, improving JIT compiler performance, more semantic merge capabilities, and a more graphical UCM experience.

2. Make Unison Share an even nicer place to host your projects. Examples: "find usages", site-wide code search, multi-collaborator projects, and more.

3. Major new Unison Cloud features: scheduled jobs, distributed event processing, resilient workflows, and high-performance native execution via our JIT compiler.

I really love where unison is going. Love the ideas behind it. My one hold up on diving into it, is that it’s unclear how much of its super powers are tied up to the cloud offering. I can’t find a simple example where I spin up two unison programs and have them pass arbitrary unison values across a socket. I get you will want more than this for a production system. But just that example alone would make me more likely to dive in and start building some stuff in unison.