On Wed, Mar 09, 2016 at 02:12:42PM -0800, Walter Bright via
> On 3/9/2016 1:55 PM, Jack Stouffer wrote:
> >Hello everyone,
> >I have spent the last two weeks porting the date string parsing
> >functionality from the popular Python library, dateutil, to D. I have
> >written about my experience here:
> >The code and docs can be found here:
> >Let me know what you think about the article and the code.
> >Thanks in advance.
> I haven't read the article yet, but you'll get more interest by
> putting a summary as the first comment on reddit.
I read the article. While I'm no Python expert (do have a little
experience with it mainly through using SCons as a build system for my
personal projects), I can totally sympathize with the annoyances of
using a dynamically-typed language, as well as dodgy iterator designs
like __next__. (I've not had to deal with __next__ in Python so far, but
*have* worked with C/C++ code that basically iterates that way, and it's
Totally agree that if you can convert something to D in about a week's
worth of work, it's totally worth it. D is just a much more comfortable
language to work in (to me, anyway -- this is highly subjective,
obviously), and, provided you don't do anything silly, generally gives
you better performance than many of the alternatives out there. Even
when it doesn't perform the best without hand-tweaking, I'd still prefer
it for general use, because of nice sanity features such as built-in
unittests (now that I've gotten used to them, I sorely miss them in
every other language!), sane template syntax, etc..
He who does not appreciate the beauty of language is not worthy to bemoan its