Since there’s currently “no ecosystem or api design for serverside stuff” to speak of, I think it might be quite equalising for elm to start her backend journey from constrained environment like aws lambda or even cloudflare workers [than starting in more general server environments]
I’m experimenting with elm on “server side” and I’m liking how elm can make “http routes” handling much better than standard url/middleware approaches; looking forward to more discoveries in this space.
The lack of parallel Task execution does mean an elm version of the canonical “google search” be slow, albeit concurrent.