Hacker News Reader

>I don’t think any technique is inherently bad: imperative, global variables, and even “goto” can be used wisely to solve problems.

The word "wisely" does the heavy lifting here. Put it this way: would you rather work on a legacy code base that has goto statements all over the place, or on one where strict standards were applied?

I find this is the relevant question when it comes to programming styles.

View on HN

I’d rather work on a codebase where strict standards were applied.

Banning “goto” is one of such, but also allowing to be utilized under certain conditions to write state machines for example.

I think we will miss innovations if we are dogmatic about features.

“Learn the rules like a pro, so you can break them like an artist.” - Pablo Picasso

Reply on news.ycombinator.com