Roc Lang – Elm but for everywhere [video]

I admire the consideration Richard and the rest of the Roc community put into the language, but I&#x27;m curious whether the absence of macros will unavoidably lead to code like <a href="https:&#x2F;&#x2F;github.com&#x2F;agu-z&#x2F;roc-pg?tab=readme-ov-file#examples">https:&#x2F;&#x2F;github.com&#x2F;agu-z&#x2F;roc-pg?tab=readme-ov-file#examples</a> . It&#x27;s not obvious to me that the benefits of that constraint (teachability, language tooling) outweigh the costs of writing code that probably should be automated.<p>That said, I may just be showing my lisp bias, and tools like Squirrel in Gleam are sufficient <a href="https:&#x2F;&#x2F;hexdocs.pm&#x2F;squirrel&#x2F;" rel="nofollow">https:&#x2F;&#x2F;hexdocs.pm&#x2F;squirrel&#x2F;</a>

roc is the language most rust nerds really want but don’t realise yet. functional, modern tooling, fast enough for almost everything (~ go &#x2F; swift), and without the insane complexity and cognitive overhead of the borrow checker.<p>So excited to see it continue to thrive and grow.

Interchangeable &quot;platforms&quot; seems like a fantastic idea! Unfortunately there is ZERO documentation on how to develop your own. For me, personally, this is the last barrier for adaptation! Please asap! Love this project!

Does anyone know if roc fell down the blessed packages issue elm did? That was a major turn off to any interest I had in elm

Can someone explain where Roc sits in terms of monads vs effects?

Does Roc lang actually do web frontend, like Elm?