Here we return a thunk that uses the IO and Exception abilities
which in turn returns Unit indicated by the 2 parens (). This specific signature is the signature of a runnable Unison function. 6/7

Abilities is a unique feature of Unison. It's how we model effectful code. Read more here: www.unison-lang.org/docs/fundame... 5/7

Lambda arguments work with type variables too 4/7

Signatures can have type variables (generics). Here's a breakdown of the `Map.insert` function, which simply adds a new element to a map. 3/7

Functions can of course accept lambda arguments. Here's `Text.map`, which allows consumers to map over each character in a `Text`. 2/7

A challenge we often hear from new Unison devs is around reading function signatures. Our syntax is common to ml-style languages (Haskell, Elm), but it can look intimidating when new to those langs. In this 🧵 I break down the syntax. First up, a function that is used to create an html div. 1/7

Also earlier when playing around with the particle effects and doing some debugging I got quite a fun effect by accident:

Here's my latest view transition experiement on hojberg.xyz

Just finished adding light-mode to the UCM Desktop pre-release. Get it here: github.com/unisonweb/uc...

cc @unison-lang.org

Finally got around to adding support for light mode and switching between themes in UCM Desktop /cc @unison-lang.org — this is not yet in the pre-release, but will be very soon (still tweaking the styling).

@chriskrycho.com Here's a Figma mock of where we're planning on ending up, good vertical alignment and all :)