News for hackers. Stuff that matters.
Re:The Case for D by martincmartin on Friday October 30, 2009 @10:42AM (#912075)
> 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.

Re:The Case for D by stevejohnson on Friday October 30, 2009 @02:42PM (#912539)
It'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.
Re:The Case for D by FeepingCreature on Sunday November 01, 2009 @11:26AM (#915184)
I never read The Book, instead learning the language entirely by the spec. It's honestly not that hard.
Re:The Case for D by sketerpot on Friday October 30, 2009 @02:26PM (#912504)
I 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?
Re:The Case for D by WalterBright on Saturday October 31, 2009 @05:15AM (#913404)
I tend to learn languages by writing compilers for them. I'm sure that isn't normal <g>.