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

[weaselcat via Digitalmars-d]

On Saturday, 14 March 2015 at 08:40:53 UTC, Russel Winder wrote:
> On Fri, 2015-03-13 at 16:13 -0700, Andrei Alexandrescu via 
> Digitalmars-d
> wrote:
>> On 3/13/15 2:22 PM, Russel Winder via Digitalmars-d wrote:
>> > On Fri, 2015-03-13 at 10:31 -0700, Andrei Alexandrescu via 
>> > Digitalmars-d
>> > wrote:
>> > […]
>> >
>> >>
>> >>     File("/tmp/a").byChunk(4096).joiner.startsWith(s)
> […]
>> 
>> How do you mean "conversely"? Maybe you meant "incidentally"? 
>> -- Andrei
>
> In functional languages, each stage in the pipeline returns 
> Option to
> avoid error handling. Go does not give you this facility as it 
> refuses
> to allow activity without proper error checking.
>
> So if byChunk returns a failed read, functional language just 
> carry on,
> Go would force the error check,
>D does…
D throws an exception that you would catch with a try block(or 
scope(failure) )?
I've never seen Go praised for its error handling, it is always 
the opposite.

Go error handling is verbose and ugly. 
http://blog.golang.org/error-handling-and-go