elm-architecture-tutorial VS package.elm-lang.org

I'm learning Haskell right now, pure functional language, but if anyone is interested, Elm is based on Haskell and much easier to learn. Elm is a web development language that compiles to JS. https://guide.elm-lang.org/

Elm is a different approach that compiles into JavaScript. In the extreme case, you have Emscripten which will compile many language into JavaScript but will feel really clumsy compared to using JavaScript in a lot of cases.

And if you want to stay in the UI realm, Elm is a good introduction into functional programming.

If you want to get better at data structures you should strongly consider learning a functional language. A huge part of functional programming is manipulating data structures. The language Elm is a great place to start for you since it's frontend specific. For example, check out the doc page for the Dict data type and see if that kind of stuff is what you're looking for.

https://guide.elm-lang.org/ for a high level guide, and an unstyled button example https://elm-lang.org/examples/buttons.

I hope this tiny guide was helpful, and that you learned something new today. If you want to learn more about Elm, you should check out the official guide or say hello in the Elm Slack #beginners channel

https://guide.elm-lang.org/ is always a solid example for me

After going through the whole Introductory Guide to the Elm Language and reading the Elm in Action book, I already felt quite comfortable developing webapps in this paradigm. I liked Elm so much that I started a project to teach programming to beginners using this language and made the first classes available on the website elm.dev.br (in Brazilian Portuguese).

Also the fact that their package manager is strongly coupled against https://package.elm-lang.org/. There is no way to override it. This means that if that package site ever goes down, you will be left with an unbuildable project. Seems pretty risky to me.

Imagine, for example, you have a component library that you don't want to publish to the public package.elm-lang.org. How do you make that available just within your company?

Not to be silly but I was getting ready to do my port & all but clicking on "source" from with package.elm-lang.org takes me to elm-charts, not elm-plot.

Elm has packages prefaced with the repo owner, so its mdgriffith/elm-ui and not just "elm-ui".

If you're dealing with some kind of currency it's better to use a Decimal type which has few packages on the ecosystem.

If you are looking for a complete API documentation you should be browsing https://package.elm-lang.org/ ; I still find it lacking compared to other programming languages, but it's definitely more complete that the starting guide.

There are two ways of structuring state. Record with each page's state in its own field OR a custom type with the variants containing the state for the page (this is what you see in elm-spa-example or package.elm-lang.org). The tabs you describe behave like the first approach.

Elm is a strongly typed functional language, compiler, package manager, and framework. You write in the Elm language, and it compiles to JavaScript for use in the browser. The Elm compiler has 2 basic modes of development, and production. It optionally has a REPL if you want to test some basic code. The package manager uses it’s own website and structure using elm.json, instead of package.json. The framework is what Elm is most known for, and was the inspiration for Redux.

I was considering doing just that, using nginx server. I was using Evan's git repo for Elm packages (website: https://package.elm-lang.org/) (git: https://github.com/elm/package.elm-lang.org ) where he does uses that. So I think I will try this first and then consider deploying the binary if I can. Thanks for the advice!