After spending hours and hours in a breadth-first scan to learn me a D, I agree completely with the suggestions in this thread and I'm happy to help implement them.

Caveats: I'm just now coming up to speed on D and I'm an engineer, not a tech writer.

I think the biggest needs are:

(1) Improve the home page "Why pick D?" info. The current text doesn't quite answer. Why switch from your creaky old language? And if you're switching, why D vs. Rust?

Mention the game-changing plans for optional GC, memory safety, and calling C++. Then D becomes a clear win in real-time, safety-critical, and security-critical systems.

(2) Add an introduction for experienced C++/Java programmers. Get them up to speed quickly and excited about how D is easier, faster, more fun, more reliable, and un-fsck'd up.

(3) [Easy] Add comparative info to the links to available books, including the D reference: Aim? Audience? Up to date? Coverage?

Ali's ebook is very nice but for beginning programmers, not me. (Ali, you might want to say so up front.) Andrei's book is 4.6 years old. How much has D changed? Honestly I'm a slow reader and will eventually read the spec, so I started reading that. Is that a rough way to start? Too many forward references? Too abstract? What'll I miss by not reading a book first (besides Andrei's humor)?

*If y'all shed light on the books, I'll update the wiki* http://wiki.dlang.org/Books

Note: This page doesn't jive with http://digitalmars.com/d/dlinks.html

(4) [Easy] Add more info on the available IDEs: Up to date? Graphical debugger? Features? Maintained? Recommended?

I'm currently using Sublime text but need my graphical debugger so I'll try Eclipse + DDT soon. I could try Visual D but I'm expecting to move off Windows. A good IntelliJ plug-in would be ideal.

*Tell me about the IDEs and I'll update the wiki* http://wiki.dlang.org/IDEs


On Saturday, 24 January 2015 at 04:35:27 UTC, weaselcat wrote:
you mean like this?
https://qznc.github.io/d-tut/index.html

Sort of, but it's old and says little about the language itself.

Reply via email to