Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
![](/static/devrant/img/pipeless-devrant-banner-white.png)
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
@Jilano first: the multiple return values. It's just a bliss to just return errors with the value. This way my actual return value is completely type safe. That brings me to the second thing: there are no union types (or whatever you call it, when a var can be a number or a string). Somehow this is a big deal which makes things pretty simple, no matter the size of the application.
goroutines. Didn't use them myself yet but boy what is that a fine way to do multitasking without producing a callback mess?
It creates a fucking binary. The thing coming out of there is fast, and you deploy one single file and you are ready to go. It's size is a bit crazy (got a good 14M with just some docker whiz and gizmo in my application) but I think that's no big deal, drive space is cheap these days isn't it. :D
It just feels good writing go code. When learning new languages, it often feels weird to actually write it after learning it. Not with go, it just feels really right somehow. -
Maartz22934yThe ecosystem is also mature!
Love alice, Negroni etc for making micro service.
It’s a real breeze.
We’ve got to write a garbage collector for dead ws connections. With go routines it was easy as fuck ! Love it.
Related Rants
God i fucking love golang
random
go
golang
language
that error handling tho