As it already has been mentioned - Future's poor performance is mostly due redundant context switches on pretty much any operation. If you do `future.map((i: Int) => i + 1)` it can be executed on a different thread,…
There's a blooming ecosystem of pure functional programming libraries. Or even two ecosystems: Typelevel and ZIO. My company uses Scala a lot with with these ecosystems (my team is on Typelevel, another one is on ZIO)…
Wondering if Unison was designed as (or ever planned to become) a general-purpose language or it something more domain-specific, e.g. distributed computations.
As it already has been mentioned - Future's poor performance is mostly due redundant context switches on pretty much any operation. If you do `future.map((i: Int) => i + 1)` it can be executed on a different thread,…
There's a blooming ecosystem of pure functional programming libraries. Or even two ecosystems: Typelevel and ZIO. My company uses Scala a lot with with these ecosystems (my team is on Typelevel, another one is on ZIO)…
Wondering if Unison was designed as (or ever planned to become) a general-purpose language or it something more domain-specific, e.g. distributed computations.