forgo VS Papercups

ForgoJS: a 4KB React alternative that gets rid of framework specific DOM access techniques and state management. For example: let people use closures for managing component state rather than something new like hooks.

Here's a preview: https://github.com/forgojs/forgo

I'll do a Show HN once it's ready.

The best language for the task at hand, when presented with time constraints, is the one that you already know well. OP said in the article that they authored Papercups [1]. Adopting Elixir for a websocket-push service makes a lot of sense, then. However, why don't you learn Elixir, some OTP, and then reconsider that question? You could be missing out.

[1] https://github.com/papercups-io/papercups

https://github.com/papercups-io/papercups - 5.2k stars, uses Phoenix 1.6

Papercups

Shameless plug here if anyone is interested in an open source live chat tool check out https://github.com/papercups-io/papercups

Phoneix - Elixir

We're a live message tool and it is basically what Elixir is built for https://github.com/papercups-io/papercups.

The Elixir community has been great and incredibly friendly. I originally was worried about the size of the community but that hasn't been an issue the community has been super helpful. I also think the annual stackoverflow usage surveys are very misleading because most of the community's questions get asked in ElixirForum and not on Stackoverflow.

Phoneix is the web framework of Elixir which is very similar to Rails but minus a lot of the magic has been very helpful for our productivity as well.

If I had to built another service that is websocket heavy I would definitely use Elixir. Even if it was a standard crud app I would still most likely choose Elixir.