As users go increasingly mobile, applications need to increasingly cater to mobile needs. And one of them is the need to communicate asynchronously: it makes no sense for your phone to continuously check your email account to see if you have a new message. That wastes your precious data usage quota, drains your battery, and is rather pointless if your email account could just send a message to your phone once to say that you have new mail instead. Of course, we're talking about much more than just email here – but that's the idea behind asynchronous frameworks. It may seem like a small change, but it is a rather large one in terms of how it would affect application design underlying all the mobile applications you use today.
Note to self: Stop reading G+, it's time to get busy!
Vert.x: Why the JVM May Put Node.js on the Ropes
It’s Time for Change. We’re beginning to see a turning point in asynchronous frameworks, specifically with regard to Node.js. My contention is that a dynamic language paired with a hybrid conc…