Working on some code and came across the Gem:
-
GOTOs are absolutely ok. Like many things, you have to use them carefully and that's all. (RANT) At every corner there is someone who wants to forbid some particular stuff he did not quite get. Sorry guys, but if you can't figure out how to live with GOTOs, memory management, pointers, object orientation or whatever else, then stop making 'rules' for those who can live with those things. Flip some burgers instead (EOR (End Of Rant))
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a fucking golf cart.
"I don't know, extraterrestrial?" "You mean like from space?" "No, from Canada." If software development were a circus, we would all be the clowns.If it is part of the language, you probably will hit a wall sooner or later that can not be broken without it... You only have to prioritize... (Not to mention, that at the end half of your nice code will translate to jumps of various types at machine level)
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
GOTOs are absolutely ok. Like many things, you have to use them carefully and that's all. (RANT) At every corner there is someone who wants to forbid some particular stuff he did not quite get. Sorry guys, but if you can't figure out how to live with GOTOs, memory management, pointers, object orientation or whatever else, then stop making 'rules' for those who can live with those things. Flip some burgers instead (EOR (End Of Rant))
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a fucking golf cart.
"I don't know, extraterrestrial?" "You mean like from space?" "No, from Canada." If software development were a circus, we would all be the clowns.Sorry RANTs are only allowed on Thursdays! :)
New version: WinHeist Version 2.2.2 Beta
I told my psychiatrist that I was hearing voices in my head. He said you don't have a psychiatrist! -
If it is part of the language, you probably will hit a wall sooner or later that can not be broken without it... You only have to prioritize... (Not to mention, that at the end half of your nice code will translate to jumps of various types at machine level)
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
I spent most of the weekend digging out almost 40 year old machine code and assembly. Crisp short routines that apparently were coded with the single responsibility principle in mind. Absolutely not the spaghetti code one might expect and the sparingly used branching instructions don't do any harm at all.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a fucking golf cart.
"I don't know, extraterrestrial?" "You mean like from space?" "No, from Canada." If software development were a circus, we would all be the clowns. -
Sorry RANTs are only allowed on Thursdays! :)
New version: WinHeist Version 2.2.2 Beta
I told my psychiatrist that I was hearing voices in my head. He said you don't have a psychiatrist!Mondays are annoying enough as it is?
-
Hi All, Picking through some code that isn't working and found the following in the comments
// // It may be necessary to get back here to process more characters. // Goto's aren't pretty, but effective. I feel extremely dirty for // using not one but two of the beasts. //Well thats good then! :wtf:
In college, one of the COBOL instructors told his students, "If you use a GOTO, I will fail you"; good in principle. Then... we worked on some code (I forget the details) and the instructor said, "For this type of application, you must use a GOTO in COBOL". I looked at it and replied, "No, and I'll explain after class." My solution to NOT use GOTO's was valid, but it resulted in 3 times the code.. and this is COBOL.. not exactly a desirable outcome, but my point was: you don't HAVE to use a GOTO, but in this instance it is preferable.
-
In college, one of the COBOL instructors told his students, "If you use a GOTO, I will fail you"; good in principle. Then... we worked on some code (I forget the details) and the instructor said, "For this type of application, you must use a GOTO in COBOL". I looked at it and replied, "No, and I'll explain after class." My solution to NOT use GOTO's was valid, but it resulted in 3 times the code.. and this is COBOL.. not exactly a desirable outcome, but my point was: you don't HAVE to use a GOTO, but in this instance it is preferable.
And then I avoided the problem entirely by using recursion, ending up with a crying CodeNazi at my desk. He insisted that nobody understands recursion. Ok, stop crying, then. And let me have a word with this Nobody.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a fucking golf cart.
"I don't know, extraterrestrial?" "You mean like from space?" "No, from Canada." If software development were a circus, we would all be the clowns. -
I spent most of the weekend digging out almost 40 year old machine code and assembly. Crisp short routines that apparently were coded with the single responsibility principle in mind. Absolutely not the spaghetti code one might expect and the sparingly used branching instructions don't do any harm at all.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a fucking golf cart.
"I don't know, extraterrestrial?" "You mean like from space?" "No, from Canada." If software development were a circus, we would all be the clowns.Very true. Back in the days of MS Basic there was barely any flow control:
.. GOTO
.. IF THEN [ELSE ]
.. FOR = TO [STEP +/- val] ... NEXTThat was it. (even the If is a conditional goto). Surprisingly code hasn't changed much these days - just got more verbose, now we have while, do, switch, break, continue ... - and if you think about it all of those "new" things are just a slightly better controlled version of IF THEN [ELSE ] We HAD to use goto, but in reality our "spaghetti code" was doing the exact same thing as people do today with "structured" code. It's not that the new programming languages fixed anything at all - just hid the truth behind new verbs. Summary: yes we loved our GOTOs, not just because we had no choice, but because we had the balls to use them, and use them really really well. Yes - balls: ladies included - although those days weren't many females into being a 'computer nerd' (- and we never really noticed that - we had our line printer Marilyn Monroe style pin-ups, and bak then that was enough.)
Sin tack ear lol Pressing the "Any" key may be continuate
-
In college, one of the COBOL instructors told his students, "If you use a GOTO, I will fail you"; good in principle. Then... we worked on some code (I forget the details) and the instructor said, "For this type of application, you must use a GOTO in COBOL". I looked at it and replied, "No, and I'll explain after class." My solution to NOT use GOTO's was valid, but it resulted in 3 times the code.. and this is COBOL.. not exactly a desirable outcome, but my point was: you don't HAVE to use a GOTO, but in this instance it is preferable.
Tim Carmichael wrote:
it resulted in 3 times the code.
If it was COBOL, how could you tell?
Software Zen:
delete this; -
Tim Carmichael wrote:
it resulted in 3 times the code.
If it was COBOL, how could you tell?
Software Zen:
delete this;When you have to type it in, you can tell. And that IS the point: 3 times the volume of NORMAL COBOL!
-
When you have to type it in, you can tell. And that IS the point: 3 times the volume of NORMAL COBOL!
In a long and fairly mundane career, I have two minor claims to fame. One, I've never had to write an Engineering Change Order (ECO) at my employer of 26 years. Two, I've never had to learn or use COBOL. My impression has always been that the language was painfully verbose.
Software Zen:
delete this;
