Talk:Bck2BrwsrFlow
From APIDesign
Comments on Bck2BrwsrFlow <comments />
codeslinger at compsalot.com said ...
Well, I am and I am not kidding. Of course, I don't want anyone to write code with 268 nested loops manually.
However JavaScript is just another assembly language - people should not write it manually. We have higher level languages that should be used by humans and then translated into JavaScript. Such translators (like Bck2Brwsr) then need to deal with efficient representation of flow and may be in need to deal with goto. Having an effective way to emulate goto -- which Bck2BrwsrFlow is trying to find then becomes essential...
Thanks for your comment and btw. chapter 13 of TheAPIBook is called Extreme Advice Considered Harmful - in honour of Goto Considered Harmful.
--JaroslavTulach 12:32, 14 March 2013 (UTC)
Follow
Your kidding right??
I mean come on, you are a very smart guy, so why would you want to design such an abomination?
JavaScript is NOT Line Numbered BASIC, so why do you want to write programs as if it were?
Every computer language has it's own way doing doing things, it's own style... You need to learn how to think in that language, not coerce some ugly mess onto it.
Remember how we all got a kick out of those laughable Japanese English Instruction Manuals... "Some Paper is Stacking Needed in honerable feeder is collector"... stuff like that... that is what you are doing the equivlent of here.
Nobody can debug and or maintain 268 nested loops... and I'd fire anybody who wrote it.
Go find yourself a copy of Dijkstra's paper Goto Considered Harmful
--codeslinger at compsalot.com 00:53, 14 March 2013 (CET)