Skip to content

Out-of-the-box experience. #879

@agirorn

Description

@agirorn

First of all, I´d like to apologize since This is probably not the place for this but I did not know where to place this.

I have to say the out-of-the-box experience of ELM is far from optimal. I´m not saying this offends anyone, but as someone who is trying to lean elm and tinker with it, I find that nothing really works out of the box.

I install elm and run mkdir elm-test && cd elm-test && elm init && elm make, then I get treated with a message telling me to go to the guides copy the first code I get, and save it into src/Main.elm and run elm make src/Main.elm this, of course, fails with

I need the module name to be declared at the top of this file, like this:

    module Main exposing (..)

I think the elm init could do more to make OTP process smoother like

  1. Include a basic app in src/Main.elm since that obviously is the next step in making an elm app.
  2. Print out the very basic next command to run

Also if you wish this to be tool developers pick ELM as there first choice as a development tool, then they have to be able to run init and start working, in my opinion.

Svelet does this will with SeletKit also Rust withe cargo new

Any how encountering a bunch of errors when trying to start it is very deterring and makes me kinda want to stop learning ELM.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions