I am in my learning curve for D as an experienced developer. What has attracted me to D is the combination of features: Design by Contract, Functional Programming, OOP, and more.
But I have been exploring the "weeds" and am curious if D is only for rocket scientists or for regular programmers, including as a first programming language.
It would be good to have a "style" document that showed the "best practices" and "Do's and Don'ts" of good D programming.
Every language has its "nits", even Eiffel. The concern is whether that is a straight forward approach to get things done, avoid the "dragons", and work with existing libraries without needing a "wizard" to cast some spells.
Should D be considered a language that should be learned in its entirety?
Or should most developers stick to the "Safe D" subset?
