It's so comfy

erlang is easy to learn. i wrote a gsm protocol implementation on both languages. although erlang is more concise, the golang version is more performant and easier to deploy since its just a static binary that you scp to the target. erlang needs a runtime so for cli apps i tend to use golang.

>
>>gopath bullshit forced upon developers is straight up hostile
go modules gets rid of this
>>dependency management is commiting some master github branch to your repo
go modules + project athens looks good
>>lol no generics
>>built because they don't trust their developers
true but if youre working with networking/telco protocols like me, you can get away with interfaces, still hoping for generics in go2 though

>>if err != nil
>>fucking nil
>>compiler doesn't even enforce mandatory error handling
yeah again hoping for a better alternative in go2
>fuck you

Only brainlets use go

Attached: blackjack.png (1032x1858, 414K)

I am going in dry

The proposal I've seen is retarded.

> hoping for a better alternative
Monads already exist. We've known how to use them practically for 20 years or more.

Attached: 1526375458960.jpg (1438x788, 124K)

Go having static binaties is slightly a lie. It has some OS requirements for timezone files (afaik this has issues on Windows as they are not present without installed compiler), links libc on network code and cgo, and has no builtin option to include file as either blob or string on compiletime (handy for templates)

wew

inst that an unrolled loop?
besides overwriting the same position i don't see anything wrong in your image

this post is slightly a lie, iirc go static doesn't automatically static link system c library but it CAN explicitly do this but cgo is excluded.

well some people have known how to use them for 20 years or more. go doesn't even know how to use tuples outside stdlib

Gopher a cute