Mention built-in commands in the Cmd module

[Zaid-Ajaj]

The third chapter 3 hand-waves its way around built-in commands and instead defines its own commands Cmd.fromAsync that is used in the rest of the chapter. The chapter should give a note on why we are building our own commands instead of using built-in ones

• To better understand commands (not just a black box)
• Because built-in commands have "weird" conventions and namings that don't make sense for me

[MangelMaxime]

I didn't read the book yet so I don't know the context either which position you choose to stand on in it.

But, if the book is about learning Elmish etc. I think using the build-in functions/helpers is better. And then, have dedicated sections about making it fits the user needs, vision, etc.

[Zaid-Ajaj]

In the book I had chosen to explain what commands are, then build commands we need from scratch (i.e. From Async<'t> to Cmd<'t> explaining why we are doing it this way. I don't think built-in commands provide much value over those that you could implement yourself easily, except for a couple of them:

• Cmd.none
• Cmd.batch
• Cmd.map