3 ms·
> Goto's create unreadable code and are unnecessary. They're there to encourage the writing of bad code. Goto's are seldom used by bad programmers anyway - mos
by laumars 12y ago
> Goto's create unreadable code and are unnecessary. They're there to encourage the writing of bad code.
Goto's are seldom used by bad programmers anyway - most of them wouldn't even be aware of them. They generally exist in languages as a niche feature used be experienced developers for those rare situations where a goto results in cleaner code. You definitely don't see Go developers sprawling goto's everywhere just because it exists.
> You can pass a pointer over a goroutine channel. That's my main issue with them, beside the fact that we should be past this needless complication of our code. Again, they're unnecessary and encourage bad code.
Erm, sorry. You've lost me now. I'll grant you that pointers require a little extra mental overhead, but they're most definitely necessary when you're writing code that either needs to be sensitive to memory usage, or performance.
As for pointers "encouraging bad code", I'm not even going to dignify that remark with a proper response.
- fweespeech 12y ago> Goto's are seldom used by bad programmers anyway - most of them wouldn't even be aware of them. .....yeah. I've seen too many internal codebases where "goto" was used so horrifically I want that feature to die in a fire just to prevent such malignancy in the future. Golang only hasn't reached that stage because its young enough there isn't heavy maintenance work over a 10+ year period yet.