On Tuesday, 5 August 2025 at 12:32:53 UTC, Brother Bill wrote:
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?
"D the good parts", syntax should be learned in a few hours:
https://github.com/crazymonkyyy/dingbats
Id probably delete over half of programming in d's chapters for
beginner introductions. Im confused by the order.
The true depths of template hell, is still unlearned *by anyone*;
there are bugs that provide more capability then what upstream
release is a few years that were undiscovered for 10 years, just
there in how it was implemented.
Or should most developers stick to the "Safe D" subset?
Wrong boundary, its template hell vs c-like d
Safe D will bring in complexity, those dips make problems hard to
solve, "how do I write swap thats @safe from dip 1000 1069 1337?"
well thats an on going research project last I saw was 100 lines
of code with criticisms about 5 edge cases, id just go with the 4
lines of code.
