A few notes on choosing between Go and D for a quick project

[Andrei Alexandrescu via Digitalmars-d]

On 3/20/15 10:26 AM, Tobias Pankrath wrote:
>> You may want to answer there, not here. I've also posted a response.
>>
>> Andrei
>
> Nitpick: Your solutions that use readText validate their input and the
> python version probably doesn't. You could mention that (I cannot
> comment on SO).

Yah, nitpicks should go there too. We need to have an understanding that 
statistically everybody is on SO and nobody here :o).

> Interestingly readText is faster than byChunck.joiner regardless.

I'm not if it does the checking.

> Nitpick 2: http://www.unicode.org/versions/Unicode7.0.0/ch05.pdf
> (chapter 5.8) splitLines is still incomplete, missing to break on
> U+0085, U+000B, U+000C. Would a PR for this be accepted?

Prolly. Walter?

> I'd say the coolest answer to this question would have been: D has not
> only one of the fastest, but the only correct solution to this that
> works with UTF8, UTF16 and UTF32 at the same time.

Well then write that answer.


Andrei