4 ms·

This article surprised me. Is the state of node.js actually not really that far along? It seems like the examples in the article (and even in this thread) are

This article surprised me. Is the state of node.js actually not really that far along? It seems like the examples in the article (and even in this thread) are all basically proxies or chatbots. Are there better examples of successful applications of node.js?

owyn 15y ago
My co-workers ran in to the same problem once they started using node.js for a project (it's a chat server!) All the examples out there are very "hello world". Even the chat server library that we attempted to use as a foundation for the chat server had never been used in a production environment. But they got it all working and it runs fine.
fletchowns 15y ago
I'd say it's pretty far along: https://github.com/joyent/node/wiki/modules https://github.com/joyent/node/wiki/modules
templaedhel 15y ago
https://www.learnboost.com/ https://www.learnboost.com/ uses node for their whole backend. They also have authored and maintain several useful modules such as mongoose.
reid 15y ago
When you visit search.yahoo.com, some lazy-loaded JavaScript resources are served from a Node.js server. That server uses YUI server-side to calculate JS module dependencies for that page's autocomplete feature. Since the response is very cacheable, and resolving dependencies doesn't happen on the client anymore, this technique improves loading time for that feature by 40%. It also delivers less code for modern browsers. Feature tests from the browser are sent in the request, which server-side YUI considers for eliminating code only needed by older browsers.
- socratic 15y ago
  This sounds like a really interesting application. Any idea what the break down is like on the loading time savings? In other words, what portion of the loading time savings is attributable to download time vs parsing time vs execution time vs other things?
  - reid 15y ago
    This technique changes: - Downloading and parsing metadata about modules YUI can load (eliminated) - Calculating what files to download based on the metadata (moved to the server) These tasks are usually started by the script loader inside of YUI's seed file, which is a small script that provides the loading API in the browser. Instead of doing these two steps, the seed simply asks the server for what's needed and gets it back, near-instantly: it's likely in your browser cache, or a Yahoo! CDN edge cache primed from another visitor. Most savings come from a combination of less code downloaded and cachability of the result. Slower browsers (old IE, mobile phones) also benefit from less execution time, because they are particularly slow at doing the loading themselves -- IE 6 users enjoy 60% faster feature startup after the switch to server-side loading.
vier 15y ago
see http://joyeur.com/2011/08/11/node-js-meetup-distributed-web-architectures/ http://joyeur.com/2011/08/11/node-js-meetup-distributed-web-...

owyn 15y ago

My co-workers ran in to the same problem once they started using node.js for a project (it's a chat server!) All the examples out there are very "hello world". Even the chat server library that we attempted to use as a foundation for the chat server had never been used in a production environment. But they got it all working and it runs fine.

fletchowns 15y ago

I'd say it's pretty far along: https://github.com/joyent/node/wiki/modules https://github.com/joyent/node/wiki/modules

templaedhel 15y ago

https://www.learnboost.com/ https://www.learnboost.com/ uses node for their whole backend. They also have authored and maintain several useful modules such as mongoose.

reid 15y ago

When you visit search.yahoo.com, some lazy-loaded JavaScript resources are served from a Node.js server. That server uses YUI server-side to calculate JS module dependencies for that page's autocomplete feature. Since the response is very cacheable, and resolving dependencies doesn't happen on the client anymore, this technique improves loading time for that feature by 40%. It also delivers less code for modern browsers. Feature tests from the browser are sent in the request, which server-side YUI considers for eliminating code only needed by older browsers.

socratic 15y ago
This sounds like a really interesting application. Any idea what the break down is like on the loading time savings? In other words, what portion of the loading time savings is attributable to download time vs parsing time vs execution time vs other things?
- reid 15y ago
  This technique changes: - Downloading and parsing metadata about modules YUI can load (eliminated) - Calculating what files to download based on the metadata (moved to the server) These tasks are usually started by the script loader inside of YUI's seed file, which is a small script that provides the loading API in the browser. Instead of doing these two steps, the seed simply asks the server for what's needed and gets it back, near-instantly: it's likely in your browser cache, or a Yahoo! CDN edge cache primed from another visitor. Most savings come from a combination of less code downloaded and cachability of the result. Slower browsers (old IE, mobile phones) also benefit from less execution time, because they are particularly slow at doing the loading themselves -- IE 6 users enjoy 60% faster feature startup after the switch to server-side loading.

vier 15y ago

see http://joyeur.com/2011/08/11/node-js-meetup-distributed-web-architectures/ http://joyeur.com/2011/08/11/node-js-meetup-distributed-web-...