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.

>>14

It breaks your "ability to reason about a program" BECAUSE YOU'RE A FUCKING RETARD.

it's not because my a fucking retard, it's because it changes you ability to reason about the program from static to dynamic. Flow chart approach isn't tenable for statically analyzing a program, yes even an idiot can follow a flow chart around but that's because it's operational. Grasping for operational understanding of code instead of a declarative one is what lower beings like goto users require.

Dijkstra was complaining about the idiots who used goto excessively

he actually wasn't and this isn't why I'm against goto. you're absolutely right that people will make a huge mess out of anything.