Do you think the same way about the code written by the guys who wrote your compiler?

I thought app stores existed because of security.
Let's do away with them altogether then.

It is much easier to make a handful of bytecode-instructions secure than it is to make the wealth of what is JS today secure.

If you start a kickstarter campaign, I would back it.

Just as we had a little hope of losing some of that "geeky" image that goes with coding... Dr. WHO starts teaching to code.
Sigh.

Will this appeal to, e.g., girls?

While you evaporate, there's a moment when you're surrounded by your own gas molecules, which can be used to push you forward, I suppose.

(I forgot to add "return x;" inside the function, but I guess that's clear)

The language is single threaded, doesn't mean it can't support "threads" in a message-passing way. The fact that my old Apple ][ can support threads by hooking 2 of them up through a serial interface doesn't make them "multithreaded". But if you want to look at it that way, then I apparently can't stop you :)

Ok, so if a "for" loop is transformed so easily into an equivalent asynchronous structure, please enlighten me and show me how.
For example, take these simple nested loops, and I'm curious what code it transforms into.

function f(x)
{
    for(var i = 0; i < N; ++i)
        for(var j = 0; j < N; ++j)
            for(var k = 0; k < N; ++k)
                x = g(x, i, j, k);
}

where g is some constant-time function.

I know this is Slashdot, but you must be talking about Google here.

If they can tell legal from non-legal, why do they even show the illegal stuff?

In related news, most people earning over $1M through the development of an iOS app have the profession: software developer.

A man is sitting in this ship, and throws a massive Korean-made LED TV-screen overboard into the water.
As a result, will the water level rise, or drop?

Please don't forget that the whole point of my comment was that threads are broken in JS.

The problem with event-driven/asynchronous programming is that it requires a lot of work, and makes your code look awkward. For example, a simple "for" loop turns into a monster of functions calling eachother, in order to break the inside of the for-loop into small chunks that can't lock the UI. Now imagine a doubly-nested for-loop. You'd need special compilers to keep your code clean.

Remember that Windows 3.1 was replaced by true multitasking for a reason.

Also, asynchronous code can only make use of 1 core of your CPU, which is also a waste.

A customer just called. He pressed "Ctrl+End" to go to the end of the document, while it was counting words. He complains that the user interface is frozen.

Yes. But because of this problem of the (fictituous) customer, I now have to rewrite my 30.000 lines of code from web-worker style to single-threaded asynchronous style. Unless you have a better idea :S

The problem is that "threads" are supposed to be a solution to dividing work.
If you don't have threads, how will you divide work without ruining the nice hierarchical structure of your code?
You'll need a special compiler that does this for you. And the result will be *slow* (albeit perhaps more responsive).