Node.js is an event driven framework for build web/network apps. It doesn't run in the browser, it is the server fulfilling browser requests. It just happens to use the javascript language.
http://nodejs.org/

Note that Torvalds concedes that the specific code example being complained about does not benefit by the use of goto.

Also not brought up in that discussions is that where to draw the line between goto and nesting depends on the amount of nesting and the length of the code in question, not nesting alone. People using goto in shorter simpler code are making the code less readable.

Now Love's example is a great one because of the falling through from one undo to another. Because the bailout applies to all nesting levels so far not just the current level. That would be awkward in purely structured code. However if the undo were constrained to only the err'ing level, if there had been a goto out after undo C and undo B then structured if/else would have been more readable. But as is with multiple levels of undo it is s very appropriate use of goto.

Unfortunately much use of goto is done when the code is simple and short, unlike Love's example.

A lot of industrial grade engineering, scientific, graphics, etc code is *nix based. These users may be running Linux on PC hardware but they don't really want or care about Linux. They want a convenient working *nix to get their work done. Linux is just a convenient option. These people don't really care about the politics, the gpl, etc. If a BSD provided a more convenient option many would migrate.

Have you attended any Linux conferences in recent years. I'm told that Mac laptops are a pretty common thing. There is no shortage of less than true Scotsman.

The US carriers were withdrawn due to fear of their loss.

At the beginning of the campaign the Marines were landed and the fleet carriers withdrew a couple of days later. The loss of air cover caused support ships to be withdrawn. Marines ashore watched the majority of their supplies and equipment sail away with those ships.

Escort carries would make runs to within range of Guadalcanal to deliver aircraft to Henderson field. I believe Henderson was the major source of US airpower in the area for a while.

A little over two weeks after withdrawing the fleet carriers came up to intercept a Japanese carrier force coming south. This battle took place well to the north east of Guadalcanal. Aircraft from Henderson engaged forces in the vicinity of Guadalcanal.

The Marines were in a bad way. They had less that a weeks food and light on ammunition too. Fortunately they were able to capture some Japanese food.

And yes, to say the surface fleet -- in particular the destroyers and cruisers -- fought valiantly to protect the Marines is an understatement. At times these destroyers and cruisers attacked vastly superior enemy forces on their routine patrols up the slot because they were the only thing between this force and the Marines.

Midway occurred a month earlier and Imperial Japan lost four fleet carriers and more importantly many of their absolutely best air crews. This alone is arguably a valid turning point. At least in a naval sense and the pacific war was essentially a naval war. Now consider how this loss benefited the US at Guadalcanal. The victory at Midway greatly contributed to the victory at Guadalcanal.

Besides the material benefits Midway destroyed the myth of invincibility of the Imperial Japanese Navy and Guadalcanal destroyed the myth of invincibility of the Imperial Japanese Army and Marines. Both played extremely important roles.

I believe that during parts of the Guadalcanal campaign the aircraft carriers were withdrawn from the area to keep them "safe", well safer. They certainly saw action but toe to toe fleet engagements were being avoided. We were a little short on fleet carriers in 1942.

Also some of the capital ships sunk by aircraft had an assist from surface action. In one of those nighttime surface engagements a US destroyer put 3 torpedoes into a Japanese battleship, greatly reducing her speed. She could not keep up with the retreating fleet and was sunk by US aircraft in the morning when the sun came up.

They were used in the 1980s to shell various hostile positions in Lebanon after the Marine barracks was attacked. This included killing a Syrian general in his command post.

They were also used in the 1991 Gulf War to shell various Iraqi positions.

Google it. People who used it back in the day mention it is not supported, relies on a hardware quirk and does not work on all Apple IIs.

And achieving 99.x% is an amazing technical achievement and extremely useful.

Video has worked quite well for quite a long time. Lacking support for a rare undocumented unsupported hack doesn't represent a major bug in the emulator.

What mainframes lack in hardware volume they make up for with users. :-)

An interesting list: http://en.wikipedia.org/wiki/L...

Historian don't make such a call, they preserve everything. A cuneiform clay tablet with a receipt for a shipment of wheat is preserved as if it had the story of Gilgamesh on it.

Decisions of what to preserve are more the domain of invading Vandals and the city residents trying to hide things from them.

Apple II emulators and disk images may have passed that 15 year mark.

The problem is goto is not just used in the "heinous" nesting cases. And "heinous" varies with the length of the conditional blocks. If there are many levels but it fits on a screen or two, perhaps leans toward if. If they are stretching for many screens worth of code maybe lean towards goto.

The problem with goto is that the conditional code is at the same nesting level as the unconditional code so it makes it less apparent what code is conditional. Using goto should be the exception, to substitute a smaller problem for a larger problem, not the rule, substituting a small problem for no existing problem at all (minor nesting for short durations).

I'm with you there.

You are missing the forest of testing and debugging. :-) Its easier if you just have one place to set a breakpoint.