On Friday, 2 October 2015 at 02:25:21 UTC, Yaser wrote:
Are there any critical frameworks or libraries that are holding
you back in fully investing in D? Obviously I think D is an
awesome language, but some frameworks/libraries hold me back,
wish I could do everything in D.
Nothing major for me, just a plentitude of small problems.
For example: you can't rely on Clock.currTime.toString() (or ISO
string overloads) to provide a reliable fixed-length
representation for logging purposes and the class mysteriously
lacks any kind of .format() function that's available pretty much
everywhere else.
When I decide to write a small tool in D, I pretty ensure that,
next to D's awesome features, I'll be exposed to some ugly warts
of the language or its ecosystem. My experience with DUB packages
(btw, there should be a word for it, like Ruby's gems) is that,
at least on Windows, they are often out of date and require
undocumented build steps to even build -- and that's before you
try to use them and hit the wall of RTFS solutions to
documentation.
TL;DR: instead of focusing on solving my problem, I have to focus
on solving problems unknown in other languages. Saving time by
using fantastic language features and then wasting twice as much
reinventing the wheel is not what I want to do.
