team VS Elm

It's just as true today, though. When the Rust mod team resigned en masse in 2021, it was announced by a programmer (the author of ripgrep) [0], and the conflict was with the core team (also programmers). A supermajority of their contributors to open source projects are programmers, so most famous meltdowns are going to be conflicts between programmers, not between programmers and the tiny minority of non-technical contributors.

I'm still waiting for anyone to give an example of an open source project meltdown that was triggered by non-technical contributors.

[0] https://github.com/rust-lang/team/pull/671

the mods publicly outlined the governance issue, while keeping the moderation issue private (https://github.com/rust-lang/team/pull/671)

Here's another list: https://github.com/rust-lang/team//blob/d4c071b86c33683845919cf27eabf33e15fb6784/teams/interim-leadership-chat.toml

they linked their (user)names:

https://github.com/rust-lang/team/blob/2cea9916903fffafbfae6...

You can also check rust-lang/team repo, where shows more than 400+ people have worked on the Rust Project as official members. And on thanks.rust-lang.org, it shows that 300+ people have been involved in each recent release. I believe the number of active contributors may be more than 100+.

Right, but this type of drama isn't new in the community. A while back the whole mod team resigned because they were not able to hold the core team accountable. In fact I remember it being said that the Core Team placing themselves unaccountable to anyone but themselves. So I don't think I'm being dramatic at all here.

If that's too onerous, you can also look at the list of directors and observe that there are people titled "Project Director" who you can look up on https://github.com/rust-lang/team and observe that they have in fact been selected from the project teams.

You're more than welcome to set the narrative straight. The infighting among Rust maintainers is based partially on your resignation note where you said the Core Team was "unaccountable" https://github.com/rust-lang/team/pull/671 and implied that they were untrustworthy. The same people that once went around starting language wars, like calling Zig a "massive step backward" for the industry https://news.ycombinator.com/item?id=32783244.

I'm just an outsider observer, who's been watching the sparks fly. It's been interesting as well to watch how quickly memories changes when positions are dangled. If there's ever an investigative report on the tribulations of Rust, they can also dig into the allegations of nepotism around one maintainer and his girlfriend on the project, vis-a-vis Amazon. https://news.ycombinator.com/item?id=28633113.

Elm [1] is based on a similar idea. Build your app from pure functions that return HTML tags.

[1] https://elm-lang.org/

You also wouldn't really be creating your own new programing language. You would be creating something that can run JavaScript by following JavaScript standards and syntax. You might be able to add some non-standard features of your own on top of those standards, or include your own standard library of helpers or utilities, but you can't completely make a new or alternative language and then load it in the browser (or at least not by reimplementing ECMAScript standards... you actually can make your own language that runs within any Javascript enviroment, if you provide an interpreter or compiler that transforms it into valid JS. Some people have done something like this, eg Elm: https://elm-lang.org/).

You should at least have a look at https://elm-lang.org/ it is a pure functional language like Haskell (although with fewer fancy syntax/type classes) but it has some lovely libraries for visualisation and even with plain elm (+ elm-ui) doing string transformations can be easily done.

I get it. However, the whole point of using Unions to narrow your types, ensure only a set of possible scenarios can occur, and only access data of a particular union when it’s safe to do so. That’s some of what pattern matching can provide, and 100% of what using switch statements in TypeScript with their Discriminated Unions can provide. Yes, it’s not 100% exhaustive, but TypeScript is not soundly typed, and even Elm which is still has the same issue TypeScript does: You’re running in JavaScript where anything is possible. So it’s good enough to build with and much better than what you had.

The beauty of a language like Elm (and other lambda-calculus / functional programming inspired languages) is that there's very little transformation involved in going from an idea to code. And that seems to have a big impact on getting things done.

I think the most fun and approachable way for beginners to build games with functional programming is with Elm [1].

See a few (small, demo) games built by the community in [2] .

Notice Elm has abandoned the FRP approach in favor of Model-View-Update [3].

[1] https://elm-lang.org/