3 ms·
The problem of D is they made mistakes in the past, they acknowledge it, yet they refuse to fix it, they are afraid of "breaking changes", they act like they ar
by WhereIsTheTruth 3y ago
The problem of D is they made mistakes in the past, they acknowledge it, yet they refuse to fix it, they are afraid of "breaking changes", they act like they are a pillar of the "industry"(?), when they are just a niche, niche languages should be willing to do breaking changes and explore new features
D is perfectly positioned to explore with ownership for example, they tried "@live", yet they don't commit
Take a look at Nim, they explored a ton with memory management, GC, RC, and now orc, they do what D's afraid of doing
All others languages catched up (including both Java and C#..), D lost it's charm, it's a language that is stuck, afraid of trying new things, and afraid of fixing broken things
zig/odin are eating that betterC market share
go/c#/java are eating that high level market share
nim ate that niche market share
and rust ate their better C++ market share
- tyg13 3y agoThis comment feels non sequitur given that the linked thread is complaining about too many breaking changes, leading to them have to constantly have to fix the code after compiler releases.
- WhereIsTheTruth 3y agoIt's not the same issue, versioning is also a problem with D, minor releases shouldn't introduce breaking changes The linked thread specifically complains about that, and the OP request for a LTS version
- p0nce 3y agoSo: D is bad because it needs more breakage! But at the same time D is bad because it needs less breakage. Right.