As a matter of fact, everyone who's written AJAX code and has used a library like jQuery (which these days covers a high percentage of serious JS developers), is already used to the event model of programming. The language's simple built-in way of creating anonymous functions is very helpful in this aspect. It's only fair to note that in this area of event-based programming, Javascript actually has an advantage. Node.js, on the other hand, comes with its own standard library that was designed from the ground-up to be 100% non-blocking. However, when you code with Twisted you have to be careful to use only very specific Python modules - use one that is blocking and you've ruined the whole model. Twisted is a venerable and powerful event I/O library for Python, for example. Asynchronous non-blocking I/O seems to be all the rage recently, as it was found to be greatly enhancing the performance of servers, allowing to handle huge loads of concurrent connections within a single process, without using threads. What's really cool about Node.js is that it's completely event-based, designed and tuned for asynchronous non-blocking I/O. It's a Javascript interpreter built on top of V8. There's a lot of excitement around this issue lately - excitement that brings talented developers in, places them in the zone for productive hacking, and overall provides a fresh perspective on things.įor example, one of the most exciting tools in this scene is Node.js. Just as the rise in popularity of JS in the browser brought us faster engines that make the internet experience more pleasant, I think that examining new approaches is generally healthy. Many people started feeling that this is a useless split of attention, and using a single language both for the client and the server is a good idea. These days a web-developer has to constantly switch between two programming languages - Javascript for the client, and his server-side language of choice for the server. The first reason, in particular, is very important. A real arms race between Google's V8, Mozilla's TraceMonkey and WebKit's Squirrelfish boosted the performance of Javascript engines considerably in the past couple of years. A zoo of new and powerful implementations has appeared recently.This increases the amount of programmers interested in it, as well as the total amount of Javascript code out there in the wild. Javascript is growing in popularity as more and more powerful applications get written in it to run in the browser.So what has happened recently to stir the balance? Since then, powerful dynamic languages like PHP, Python and Ruby along with Java and ASP have taken over the server-side development scene. The idea certainly isn't new - Netscape had offered JS on the server-side sometime in the 1990s. In the past few months a new meme seems to be very vibrant in the world of web-development: server-side Javascript.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |