Why go sucks

* goto
* bad exception handling
* no generics; they latter added a hack for this this as a macro
* reminder that go programs just download whatever the fuck off github and call it good and run it. and cant even remember specific versions of them so you are ultrafucked if they ever change

Go is like the Tea Party of programming: everyone knows their ideas are shit but they're REALLY REALLY OPINIONATED about them so it's not even worth arguing.

>>19
"Goto considered harmful" is literally a meme. That's not even what Djikstra wanted to call the article. And yes, on typical architectures, pretty much all control flow structures are implemented as the equivalent of goto. It only became problematic when languages like BASIC made it easy for idiots to program, and goto based code is easy for an idiot to screw up, since all it takes is a typo to send your program to the wrong line (and in some cases the problem might not be immediately noticeable). Structured programming protects the programmer from this - it's nearly impossible to jump into the middle of the wrong subroutine by accident, usually the program will just fail to compile.