elm-companies VS core

This list is extracted from several sources, such as elm-companies, Stackshare.io, blog posts, videos, talks, atc.

This list shows around 100 companies using elm in production, but that's not all of them. I worked in 2 companies with their entire frontends in Elm and they are not listed here. https://github.com/jah2488/elm-companies

elm is a lovely lang. it would be nice to have modern APIs on it.

here's the project for new eyes:

https://github.com/elm/core

https://elm-lang.org/

In Basics.elm we have:

The package docs for all the functions we learned today

However I notice that the developed of elm/core has died down (last commit was 4 years ago) and I feel that it's fading into obscurity.

https://elmprogramming.com/

There isn't that much good learning material. It is important to get comfortable with the official docs. Especially the standard library that you find here: https://package.elm-lang.org/packages/elm/core/latest/

Looking at the default branch of core, you can already see this in more than just "for the compiler".

For a minimal but useful set of functionality, I would love to see a better set than elm/core. In essence, basic types (Int, Float, String, Bool) and ways to combine these: Tuples, Records, ADT. Since they are also used so frequently, List, Map/Dict, Set and Option/Maybe implementations should also be included. In terms of functions, basic Math and a sensible set of operations for each of the included types. Again, elm/core is a good example.

Once all that handwritten C code was solid, I needed to make sure the C generated from Elm was working properly. I found the source for the core library's unit tests and decided to port them into my project and add some of my own tests. You can run the tests in WebAssembly in your browser too. (Funnily enough, one of the biggest challenges was getting the Elm Test framework itself to run! The framework is more complex than the tests themselves. I still need to come back to the fuzzer tests!)