stream: proposal to improve err msg when ._write is not implemented

[italoacasas]

Right now when someone try to use writable.write we don't give too much feedback in the error msg. I think we can do better on that area.

Example:

const ws = require('stream').Writable();
ws.write('example')

Output:

Proposal:

[cjihrig]

This seems like too much. The existing error is not really helpful. What about something simpler like _write() must be implemented or _write() is not implemented. If you are creating your own writable stream, you should already be familiar with the docs.

[italoacasas]

I understand, but I think we have a lot of places that we can improve the error msg, maybe the format that I'm proposing, in this case, is not the best one but we should try to improve this kind of errors msg.

We cannot assume that all the developer are seniors, and in most cases, people don't read all the documentation, they read some random article in google. I don't think that giving more information like a link pointing to the specific documentation, a more readable error, etc... is not going to affect in a negative way on comprehension.

For newcomers is going to be something nice to have too, I would love to give this a shot, maybe I can make a proposal with different Ideas of how we can improve in my opinion this kind of errs msg where we have more information that we can show.

[cjihrig]

Sorry, but I'm -1 to elaborate error messages, and very -1 to including URLs in error messages.

[italoacasas]

Yeah, on second thought I do not think a URL is a good idea. But I cannot see the downside in elaborate more the msg when we have more information that we can show.

[italoacasas]

80% of the time when a person get this kind of error Error: not implemented they are going to use google to find the response, we can kill that step if we elaborate more the error msg.