Package.json dependencies done rightblog This is part one of a three part post on npm Dependency management. Need I say more? Entire developer ecosystems live and die by how dependency management works. Ask a Ruby developer what they would do without RubyGems, or ask (most) Java developers how to get things done without Maven.
Cross-compile node.js on ARM - the WigWag devblog. 3/5/13 –> We don’t have time to post updates right now, but if you need a working script for node 0.8 using an ARM toolchain, see example Gist here Note: the information was current as of node 0.7.0 top of tree, from circa Jan 21, 2012. So modify as necessary. There are three major steps/challenges in getting node.js to compile on ARM We need to get V8 to compile on your target arch.
Benchmarking Node.js - basic performance tests against Apache + PHP Several days ago I have done few very basic performance tests to see how node.js server behaves compared to Apache when serving very simple pages. All tests were executed on dual-core Intel T4200 2 GHZ machine with 4 GB RAM running Ubuntu 10.04 Lucid (with X). For comparison I have used node.js 0.1.103 on one side, and Apache 2.2.14 with prefork MPM and PHP 5.2.10 on the other, hitting them with ApacheBench 2.3 and total of 100,000 request with 1,000 concurrent requests during first test:
Node.js on Android I mainly use node.js since one year ago at work, and I really like it. On my work project, I have to create a system which uses socket.io, but I don't have enough time to re-create a system using Android Java. But I finally figure out how to run node.js on Android. Understanding the node.js event loop So the largest waste with current programming technologies comes from waiting for I/O to complete. There are several ways in which one can deal with the performance impact (from Sam Rushing): The second basis thesis is that thread-per-connection is memory-expensive: [e.g. that graph everyone showns about Apache sucking up memory compared to Nginx] Apache is multithreaded: it spawns a thread per request (or process, it depends on the conf).
How to write your own native Node.js extension - Olivier Lalonde's blog UPDATE: There is now a Node.js addon for loading and calling dynamic libraries using pure JavaScript: node-ffi. Also, node-waf is no longer being used to compile Node.js extensions. TRANSLATIONS: This post was translated to Chinese: Introduction - Chrome V8 Welcome to the developer documentation for V8. V8 is Google's open source, high performance JavaScript engine. It is written in C++ and is used in Google Chrome, Google's open source browser. This documentation is aimed at C++ developers who want to use V8 in their applications, as well as anyone interested in V8's design and performance.
Useful Node.js Tools, Tutorials And Resources Advertisement Created by Ryan Dahl in 2009, Node.js is a relatively new technology which has gained a lot of popularity among Web developers recently. However, not everyone knows what it really is. Node.js is essentially a server-side JavaScript environment that uses an asynchronous event-driven model. What this means is simple: it’s an environment which is intended for writing scalable, high performance network applications.
Understanding node.js Node.js has generally caused two reactions in people I've introduced it to. Basically people either "got it" right away, or they ended up being very confused. If you have been in the second group so far, here is my attempt to explain node: It is a command line tool. You download a tarball, compile and install the source.It let's you run JavaScript programs by typing 'node my_app.js' in your terminal.The JS is executed by the V8 javascript engine (the thing that makes Google Chrome so fast).Node provides a JavaScript API to access the network and file system "But I can do everything I need in: ruby, python, php, java, ... !".