No more writing encoders and decoders at every network
boundary. Say where you want computations to run and it happens
🔮 — Dependencies are deployed on the fly.
Your codebase is always live and typechecks, even in the
middle of a refactoring. Unison has structured refactoring
sessions, not a big misleading list of type errors.
No more writing translation code between your values and the
storage layer. Directly store values and unpersist them later
without fear of dependency conflicts or version mismatches.
Other tools try to recover structure from text; Unison stores
code in a database. This eliminates builds, provides for instant
nonbreaking renames, type-based search, and lots more.
Many dependency conflicts arise from definitions competing for
the same names. Since Unison references code by hash instead of
by name, an entire class of conflicts can be eliminated.