On Tuesday, 5 August 2025 at 12:32:53 UTC, Brother Bill wrote:
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.
This is both one of the strong and weak points of D: It gives you a ton of flexibility and lets you model code in a fairly free-form way, unlike languages like Go where variety between codebases is very minimalised.
It would be good to have a "style" document that showed the "best practices" and "Do's and Don'ts" of good D programming.
There's things like The D Style guide (https://dlang.org/dstyle.html) which is used for Phobos, and there's the slightly crusty D Idioms list (https://p0nce.github.io/d-idioms/) going over a bunch of misc stuff.
I initially had more to say, but monkyyy's answer kind of eludes to it - there's many different ways to use D (half baked or not) to the point nothing can truly work together in exact harmony.
