>>4node.js ``apps'' are the problem, or rather [m]node.js[/m] is. Just when you think web development got back to its senses and started to move away from Javashit, this thing comes and sets the world back with completely ridiculous claims of performance that everybody and their grandmother gobbles up immediately, no matter how obviously bullshit they are:
node.js scales linearly with the number of cores.
— Ryan Dahl
What people don't mention in the advertisement is that you have to write your program in callback-style Javashit, which has got to be the worst way to do concurrency ever conceived. I'd say only raw mutexes are worse, but I'm not even sure about that one because at least I'd have a language choice there. You can't really use anything else either because
node.js doesn't play well with saner concepts like promises and most modules, another purported strong point of
node.js, rely on callbacks.
So what this project essentially does is package a bad platform based on a bad language and a bad idea together with a rendering engine that infests the web with its ad-hoc, IE6-like pseudo-standards, thus create a lovecraftian software stack and call it
``a new way of writing applications with all Web technologies''.
This project seems completely and utterly pointless to me from a development perspective. Web technologies are for the web, and they
suck in their current state, even for their original purpose. Why anyone would try to port them and shit up the desktop world with repurposed tools unsuited to the job at hand is beyond my comprehension. This seems all too much like this
node.js solves everything mindset that appears to run rampant in its community right now and happens every other year when the new overhyped framework hits its peak in popularity.
Sorry, Intel, your new way to write applications sucks.