4 ms·
D is well-designed and has many wonderful features, but its documentation is so bad as to make it unusable for serious work. This article is the best reference
by stevejohnson 17y ago
D is well-designed and has many wonderful features, but its documentation is so bad as to make it unusable for serious work. This article is the best reference work on D2 that I have yet seen, which should not be the case.
Also, this guy has been working on the book for over two years now. Even when it's done, it's going to be just like Grails is now: you can read the online docs, but you don't really get it until you read a certain book.
- dkersten 17y agoThe Phobos vs Tango thing put me off too.
- martincmartin 17y ago> you can read the online docs, but you don't really get it until you read a certain book. Isn't that expected and normal for anything that involves thinking about things a different way? D has language features that most programmers aren't familiar with, so to use the effectively involves a shift of thinking. Same with Grails.
- sketerpot 17y agoI learned Python by reading the official tutorial and hacking away until it made sense. I did the same for O'Caml, and later for Haskell (although that one took longer). Isn't that normal?
- WalterBright 17y agoI tend to learn languages by writing compilers for them. I'm sure that isn't normal <g>.
- stevejohnson 17y agoIt's not that books are bad, it's that there is only one book. If it's not in The Book, you essentially can't find it anywhere, unless your mailing list spelunking skills are particularly good.
- FeepingCreature 17y agoI never read The Book, instead learning the language entirely by the spec. It's honestly not that hard.