JavaScript Multi-Threading – How to Implement Multi-Threading in JavaScript

This is true:

Rush to client-side in web development

But it is not confined to client-side, it is a full stack movement.

I know this may be surprising. Please, hear me out.

Why is that so? How could the new and "diffuse" client-side developing in HTML5/JS possibly be superior to big and well thought server-side solutions?

First of all, both are well thought out.

Secondly, Because it is better.

Good question.

But "better" is subjective, so the answer to your question is, what specifically is better?

Re-visit the question:

How could "diffuse" client-side developing in HTML5/JS possibly be superior to big server-side solutions?

Because small is nimble.
And big is clunky.

It is flexibility.

Doesn't seem like a big deal. Does it? Flexibility.

However, flexibility underlies everything. One improvement in flexibility - improves everything.

Maintainability. Extensibility. Scalability. Modularity. Usability. UX.

And it is faster to implement. This is the reality. Faster and Better.

This is why Windows 8 made JS a first-class citizen.

HTML5 - JS, is not a fad and it will not go away. We are only seeing the seeds of a technology that will grow to provide computing content and interaction behavior to tablets. Tablets.

Smart phones were the fastest mass-media adoption since the TV in the 1950's. Now, not only do we have smartphones - we have Tablets.

Already in development at Mozilla and Windows the OS that will run on future devices in their markets -> HTML/JS.

Many solutions and innovations remain.

A full stack of JS is emerging, based on flexibility.

I hope that helps.

There are several advantages to this approach:-

• Responsiveness, because the business logic is in the fat client you do not need to wait for a round trip over the network for every interaction.
• Sophistication - having all the control and higher level logic in the client enables rich user interfaces (e.g. this site, or gmail) which would simply not be possible if every interaction required a round trip to the server.
• Scalability, all this processing is taking place on your device, using your electricity. if you have a large number of users the saving in server side processing is significant.

There are a few downsides though.

• Lack of control over the client environment. You do not know which browser on which OS or what screen size and processing power your client will have. You application may not work on every client.
• Uneven response. Large client libraries need to be downloaded and upgraded every now and then which will be relatively slow, once downloaded the response is lightning fast, users, generally prefer a consistent response time even if it is a little slower.
• Javascript -- love it or hate it you are stuck with it as your main development language. Your code becomes public which some companies hate (perhaps they are embarrassed by their code quality?).
• Security -- your server side code is now largely just database services whose APIs are open to anyone studying your Javascript therefore you need to take extra care in securing these services.