Hacker Newsnew | comments | show | ask | jobs | submit login

1979 calling.

> Documentation was better back when.

When I started programming properly ('84, '85?) it began with being issued the full shelf of IBM 3060 manuals - and when I mean shelf, I mean 3 feet. All my reference material was for the version I was using - relevant, complete, practival. We used to say RTFM and we meant it, you had an M to RTF.

Lots of people hate on the Erlang documentation http://www.erlang.org/doc/ but I love 'em, proper shelf, proper docos.

I am trying to write some HTML5/Javascript sound stuff and help is picking overcooked vegetables out of Google Soup - ech!




This times a million. Microsoft, OpenBSD and Golang are the only things I've found that produce good quality extensive reference documentation these days that I can take offline.

Python documentation, while extensive, is crappy.

I still miss my Sun Ultra enterprise 2. That was documented to bits.

-----


To add to your list I like the PostgreSQL manuals. They always seem detailed and clear.

I find the Rails documentation awful lacking a lot of detail with an expectation that you read the source which in places is fairly hard to follow through several layers and even if you find the relevant part without good documentation you can't tell if it is a bug or intended behaviour in some cases.

-----


Yes I probably should have added postgres. I like the fact that they keep the documentation nicely versioned as well. The quality is fantastic too.

-----


I'd add FreeBSD to that list. Back when I was setting up linux on my macbook, I first went to the FreeBSD manuals to learn how things worked.

-----




Applications are open for YC Winter 2016

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: