Hacker News new | past | comments | ask | show | jobs | submit login

Go isn't my first choice but “like, for anything” reeks of dogma. Can you explain your rationale?



That was just a harmless (I hope) hyperbole. I've actually used Go a couple of times for image processing workers and such. And that's when I developed my distaste for this language.

I mean, I get it, it's easy to pick up and use. Coroutines and channels are useful, and make easy to write async stuff.

But god damn, it's so dull and boring, there's no joy in it. We're programmers, we're supposed to extract abstractions and express them in the code we write. And IMO your language should definitely try to help with that.

Instead, Go wants you to do err, value = ..., if err == nil { ... } on almost every single line. You can't adequately compose stuff. Well, you can try, but you quickly run into its ugly, verbose syntax for anonymous functions or lack of generics.

Maybe I'm not getting something, maybe it's just not for me, I dunno. But next time I need high performance compiled language, I'll use Swift or maybe even Rust. Also I think Scala Native is somewhat stable already, gotta look into that.


I pull my joy from the task being accomplished rather than the syntactic swirls I sketch out while accomplishing it.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: