Rich two-way binding based on libraries like Handlebars is the norm these days.Frameworks like Meteor are also on their way to the developer toolbox to solve concurrency & scalability issues and let the developer only be concerned about developing what they want in a high level way.

Not to mention the beast that is the Html5 as it holds a lot of promise for the future. W3C Web Workers is coming onto the scene as a form of “threading” and supported in the ECMAScriptEdition 5.

There are number of up and coming libraries for doing tasks in JavaScript which up until now was considered only a “server job”. Pdf.js is one such HTML5 technology experiment that explores building a faithful and efficient Portable Document Format (PDF) renderer without native code assistance. Zip.js is another JavaScript library to zip and unzip files on the client-end. JS-Crypto is a collection of JavaScript crypto functions to call from the front-end.

Is this how the future would shape up to for the Web 3.0? Is JavaScript in every layer in an N-Tier Architecture i.e. Presentation Layer, Business Layer, Data Access Layer a viable solution? I would love to get your view regarding today’s JavaScript in “every sphere” based development paradigm.