<story><title>Gleam Is Pragmatic</title><url>https://blog.drewolson.org/gleam-is-pragmatic/</url></story><parent_chain></parent_chain><comment><author>jazzypants</author><text>&amp;gt; I won’t fall into the trap of trying to define Monads in this post. Instead, let’s talk about monadic-style APIs – that is, APIs that allow you to do a bunch of things one after another, with the ability to use the result of a previous computation in the next computation, and also allows some logic to happen between steps.&lt;p&gt;Am I crazy, or did he just give a really good definition of monads in programming? I think that it benefits by not letting itself get bogged down in Category Theory nomenclature which doesn&amp;#x27;t actually matter when programming.</text></comment>
<story><title>Gleam Is Pragmatic</title><url>https://blog.drewolson.org/gleam-is-pragmatic/</url></story><parent_chain></parent_chain><comment><author>atemerev</author><text>The greatest power of BEAM-based languages is the fully preemptive actor model. Nobody else supports it. This is a superpower, the solution of most problems with concurrent programming.&lt;p&gt;In Erland and Elixir, actors and actor-based concurrency hold the central place in the corresponding ecosystems, well supported by extensive documentation.&lt;p&gt;In Gleam, actors and OTP are an afterthought. They are there somewhere, but underdocumented and abandoned.</text></comment>