GOTOs are not harmful.
They're just the BASIC equivalent of jumps in assembler. GOSUBS are just calls. If they're really so bad, why are their assembler equivalents used in almost every program in every architecture?
What's your most controversial programming opinion?
51–53 of 53 posts
Re: What's your most controversial programming opinion?
#52Mine is very simple and very contentious:
It is completely unprofessional to implement a solution you've been asked for, if that solution is bad practice.
That is to say, if you're asked to make a hack that will cause pain and misery, has a security risk attached, won't be performant or other clear, obvious risks, it is unprofessional to not object and in some cases, refuse.
Re: What's your most controversial programming opinion?
#53Editing one big file is easier than editing many small files. Hence, have a tool to break your "one big file" into small "section" files if needed but stick with one big file as long as your editor can stand the size.
This is so "controversial" that some nice fellow here on HN both called it "crazy" and up voted it because of that.
My current "one big file" is 16555 lines of code long (javascript/nodejs). GVim handles it perfectly.