Elm - General Discussion, Blog Posts, Wiki

[OvermindDL1]

@cjen07

If you ever build a project using Elm and Phoenix in real world, you may try to put all elm files in a src folder and export them to a Main.elm and then compile the Main.elm. That is not a wise way to organize all elm files, because you will not put all views in one single index.html.eex. If you think that’s how elm should work in a single project, I think you are wrong.

Except I had to do that as it was a single monolithic app, thus yes all the views were together. The way Elm’s type resolver works is the more types you have then the exponentially slower it gets to compile.

@cjen07

All js files are concatenated into one app.js: “info: compiled 4 files and 8 cached into app.js in 284 ms”. And the html only needs app.js, which is a monolithic file.

If you check you’ll see the elm standard lib duplicated a lot, though google closure can help with that at times.

@cjen07

I am not arguing that elm compiles any faster than bucklescript. If you just aim for absolute compile time, bucklescript is obviously better. I am suggesting that If one builds a project with elm as the frontend language, there is a much better way to organize all elm files: not to import all views into one View.elm, not to import all models into one Model.elm, not handle all msgs (even indirectly) in one Update.elm. If you follow my suggestions, you will not have to wait too long for a change in one elm file.

Okay, so how would you split up a single monolithic notification/messaging app for a teacher tracking system? How could you not import all the parts of the view into a singular location?

@cjen07

I think I am still new to elm, not writing any effect managers, not reading enough source code, but someone in elm community once told me they have over 100k LoC and incremental recompiles are about 1s:

rtfeldman’s thing minimizes the types used and they have multiple pages, not a single page that drives everything. They came from a javascript centered world so types were not at their forefront. A ~28k line project here takes about 48s to compile even after it had already been compiled once, though this was in 0.17, 0.18 brought some improvements in some areas but nothing substantial.

EDIT: Also Elm has nothing to do with ocaml, moved to where it belongs.