3 ms·
The crappy documentation is very much in line with many Go libraries, sadly. There doesn't seem to be a great culture of documentation. People often just write
by autarch 12y ago
The crappy documentation is very much in line with many Go libraries, sadly. There doesn't seem to be a great culture of documentation. People often just write bare API docs without explaining why the library is useful or showing a lot of examples.
- yvsong 12y agoIt may be a cultural difference of system programmers (including Go designers and developers) and (consumer) application programmers (e.g., as in the Apple camp). System programmers regard themselves higher, prefer terse symbol names, specs, docs, mathematical expressions, and formal methods, don't seem fans of Objective C or Java style readability and verbosity. But then again, it's open source software -- No one owes anyone anything.
- Dewie 12y ago> formal methods Go and formal methods? Seriously? It's one of those things that I imagine the Go community rejecting as being academic and not about getting stuff done. ^ that's not a value judgement, btw. I have no experience with applying formal methods myself.
- djhworld 12y agoNever experienced this, godoc https://godoc.org/ https://godoc.org/ is a good resource
- autarch 12y agoI was complaining about exactly the docs I've found on godoc.org.