wolfadex

Just a reminder that Svelte, in Rich Harris's own words, is a language and not a framework. It technically isn't JavaScript, just an incredibly similar syntax.

While I primarily use Elm for all my front end side projects, I do think it's worthwhile to try both.

I'm currently writing a blog about trying as many front end frameworks/languages as I can. I'm going with this approach because I want to see what I can learn from each of them. For example, I've learned from Elm that compilers can be much friendlier. I've learned from Svelte that people are more willing to accept what appears to be familiar.

You may learn something completely different.

By "regular" programming do you mean JavaScript?

What's wrong with being verbose?

We're in the process of a rewrite into Elm at the moment and have been loving every moment of it. Even the devs who are seeing Elm for the first time are enjoying it.

This year I've been super productive with Elm and built a few things for the community:

Elm Resources (https://wolfadex.github.io/elm-resources) - opinionated list of tutorials and tools for Elm

elm-license-finder (https://github.com/wolfadex/elm-license-finder) - tool for listing elm dependencies

elm-text-adventure (https://package.elm-lang.org/packages/wolfadex/elm-text-adve...) - package for building text adventures in Elm

Grove (https://github.com/wolfadex/grove) - WIP GUI tool for management of Elm projects

Slime Buddy (https://slime-buddy.netlify.com) - A little slime pal that you can take care of (re-wrote it from JS to Elm)

And I have 2 other projects that aren't quite ready to show. Maybe I'll have something for 1 of them before the 1st?