5 ms·
I think OP thinks about documentation of framework/language like an explanation of why/how/what for and not exactly API references. I agree with both of you, go
by wrestlerman 8y ago
I think OP thinks about documentation of framework/language like an explanation of why/how/what for and not exactly API references. I agree with both of you, good API docs is mandatory, but also reading about advantages/disadvantages on the official website of given technology should be very easy to do.
- jasode 8y ago>, but also reading about advantages/disadvantages on the official website of given technology should be very easy to do. Yes, it's technically easy but not socially easy. If I go to the Elixir landing page at "elixir-lang.org", it doesn't list the disadvantages and warts. Obviously to us, they didn't avoid writing negative things because they ran out of disk space to store the text or didn't have the network bandwidth. The reason is that it's human nature not to do that. We have to find that alternative viewpoint from people like you (since you're interested in explicitly writing about some of Elixir's issues).
- tessiegarcia 8y agoAgree with you!