These problems are all solvable by other languages/frameworks. I use Python, and we have gevent, which does the same thing as Node, but in a more concise language with a richer standard library.
I agree, in addition javascript is not easy to develop in. Yes, it's fun and fast for little projects. But do I want to stake my future upon a huge javascript codebase? I'd rather not. Navigating through javascript code is beyond cryptic at times.
"III. 2010-??: The Javascript Age" is true only if you build highly interactive web application. When you just need a web site with forms for CRUD content, many PHP CMS systems are just fine, often without coding except when you need a custom theme. The majority of the sites are such ones so LAMP is not near dead.
That's fair enough, but seems to ignore the fact that there is still a tremendous need for efficiently serving static files, even in a javascript era. Images, CSS, Javascript, HTML all still need an efficient method of delivery, and I don't believe that Node.js can fill that role as well as is needed.
I don't see the LAMP stack going away. Parts of it may be substituted as new technologies become popular, but the concept is still sound.
And machine instructions aren't going away, because that's what those C server applications compile down to. But the "web stack," like the other layers before it, is becoming a black box which many developers won't need to know about to do their work.
The principal role of the server is to ship an application to the client (Javascript), along with data (JSON), and let the client weave those into a DOM.
I think that's mixing up technology and content. Just because it has become easier and more efficient to send lots of JSON messages back and forth doesn't mean all documents suddenly become interactive applications.
What I don't understand in the first place is why we want to create persistent sockets on top of a stateless, request-response protocol like HTTP. Sounds like a travesty to me.
We don't, necessarily. Sometimes a persistent socket is the right tool for the job. Sometimes it's not. The whole point of the article was that Node and its ilk serve both needs very well, whereas older mechanisms do not.
[+] [-] codysoyland|15 years ago|reply
These problems are all solvable by other languages/frameworks. I use Python, and we have gevent, which does the same thing as Node, but in a more concise language with a richer standard library.
LAMP is not dead. It's evolving.
[+] [-] Meai|15 years ago|reply
[+] [-] ognyankulev|15 years ago|reply
[+] [-] falcolas|15 years ago|reply
I don't see the LAMP stack going away. Parts of it may be substituted as new technologies become popular, but the concept is still sound.
[+] [-] asolove|15 years ago|reply
[+] [-] baggachipz|15 years ago|reply
[+] [-] splatcollision|15 years ago|reply
The principal role of the server is to ship an application to the client (Javascript), along with data (JSON), and let the client weave those into a DOM.
[+] [-] andreyf|15 years ago|reply
[+] [-] fauigerzigerk|15 years ago|reply
[+] [-] trustfundbaby|15 years ago|reply
word?
[+] [-] ignifero|15 years ago|reply
[+] [-] baggachipz|15 years ago|reply