package.elm-lang.org VS elm-canvas

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!

You don't need native code to be productive in Elm. Elm is perfectly useable without it. Use of native code was not widespread before 0.19 anyway.

I would know. I was working on a large native code project that was killed by 0.19. It sucked for me that my project could not continue, but, I can't say that it has made much of a practical difference when it comes to making software applications. My project was called "elm-canvas" and it was about providing canvas support. Since 0.19, other people have found implementations of the HTML canvas element that do not rely on native code (Like Joakin's great 'elm-canvas' https://github.com/joakin/elm-canvas). For my own HTML canvas based software projects, I have been able to find my own non-native code implementations that work pretty well.

So, I think I faced a disproportionate amount of this problem, and I can't even say it has made much of a difference to my own productivity in Elm (and I have written a lot of Elm).