roc VS purescript

See also: https://github.com/roc-lang/roc/blob/main/www/content/faq.md...

Zig is not entirely unsafe. It provides quite a few compile time checks and primitives to catch memory leaks or prevent them altogether.

For those following along https://github.com/roc-lang/roc

https://github.com/multikitty/New-Programming-Languages-Show...

I don't see how to make Single Page Apps, or really anything client side in Roc. I'm quite frustrated by https://github.com/roc-lang/roc/blob/main/roc-for-elm-progra... which doesn't answer this which is the first question imo.

Their FAQ is an eminently reasonable breakdown of their choices:

https://github.com/roc-lang/roc/blob/main/FAQ.md

I don't fully agree with all of the reasoning, but it's a reasonable position to stake.

If you forget what parametrisation and functions are, then Roc's modules look like they actually do that.

Reminds me of: https://github.com/roc-lang/roc/blob/main/FAQ.md#why-doesnt-...

> How would a user interface written in a functional language look?

Maybe you're not aware of Elm?

https://elm-lang.org

Elm is really functional, unlike the likes of React that are just partially, kind of functional.

There's an attempt at bringing Elm to the desktop, the Roc language... here's an UI example written in Roc:

https://github.com/roc-lang/roc/blob/main/examples/gui/hello...

What are your thoughts on the direct descendant, Roc? [0] I know it's pre v0.1 so maybe you don't have any, but as a fellow Elm lover it seems pretty compelling on the surface albeit less directly frontend-dev focused.

[0] https://github.com/roc-lang/roc

I might be misunderstanding something, but, for example, look at this "host"/platform: https://github.com/roc-lang/roc/blob/main/examples/cli/tui-platform/host.zig

When I see this it makes me want to run for ReasonML/ReScript/Elm/PureScript.

Sum types (without payloads on the instances they are effectively enums) should not require a evening filling ceremonial dance event to define.

https://reasonml.github.io/

https://rescript-lang.org/

https://elm-lang.org/

https://www.purescript.org/

(any I forgot?)

It's nice that TS is a strict super set of JS... But that's about the only reason TS is nice. Apart from that the "being a strict super set" hampers TS is a million and one ways.

To my JS is too broken to fix with a strict super set.

A web application makes use of these same ingredients, i.e. HTML, CSS, and JavaScript, but it uses significantly more JavaScript. As the JavaScript powering your web application grows in size it can bring with it a variety of problems that a few languages, like TypeScript, ReScript, PureScript, and Elm, have attempted to solve. Each of the aforementioned compile to JavaScript languages have their pros and cons but it is beyond the scope of this article to get into those details. Suffice it to say, my preference is Elm. It is also not the goal of this article to convince you to use Elm but only to show you how Elm fits into the flow of creating a web application and hosting it on GitHub Pages. So let's continue by adding Elm to our project.

Naturally I’d recommend using a better language such as ReScript or Elm or PureScript or F#‘s Fable + Elmish, but “React” is the king right now and people perceive TypeScript as “less risky” for jobs/hiring, so here we are.

Unless you want to switch to https://www.purescript.org/.

PureScript[1][2] seems pretty alive these days. From my relatively small, self-contained experiments, it's a lot more flexible and expressive than Elm at the expense of (maybe?) being a bit harder to learn up-front.

[1]: https://www.purescript.org/

[2]:https://github.com/purescript/purescript