The error message for when the command reactor from the elm compiler is used could be more human friendly and newcomers' friendly (writers, non-devs, ...).
SSCCE
elm reactor
Go to http://localhost:8000 to see your project dashboard.
elm: Network.Socket.bind: resource busy (Address in use)
Elm: 0.19.1
Browser: N/A
Operating System: Arch Linux
Additional Details
The error message, while sufficient for devs, might be intimidating since it refers to socket which can be confused with websockets and lead the user to the wrong guess (am I using a websocket? What is a websocket? How can I disable this in my operating system?).
The error could maybe look like
elm reactor
Oops! Looks like another application is using the port 8000. A port is a way
to open communication between two interfaces, a server (elm reactor) and a
client (your browser). But I can't open the port 8000 since there is already
another application (another server) listening for requests for this port! Try
to search & stop the application that is responsible for listening to this port?
Or you can also use a different port by using this syntax.
elm reactor --port 8001
Try using
elm reactor --help
For more information.
Of course the error message could be shorter but it's nice to have this educational error messages sometimes.
Quick Summary:
The error message for when the command
reactor
from theelm
compiler is used could be more human friendly and newcomers' friendly (writers, non-devs, ...).SSCCE
Additional Details
The error message, while sufficient for devs, might be intimidating since it refers to socket which can be confused with websockets and lead the user to the wrong guess (am I using a websocket? What is a websocket? How can I disable this in my operating system?).
The error could maybe look like
Of course the error message could be shorter but it's nice to have this educational error messages sometimes.