He found that the more HTTP client requests he did, the more memory his Node process would consume, but it was really slow.

[...] Then I ran Node with UMEM_DEBUG set to record various important information about the memory allocations

[...] Every hour, it grabbed the output of pmap -x and a core file and stored those in Joyent Manta

[...] In MDB there's a particularly helpful command ::findleaks that will show you the memory addresses and the stack traces for leaked memory, not unlike using valgrind, but without all the performance penalty.

[...] At this point we knew that we were looking for something in v0.10 that called MakeCallback but that didn't first have a HandleScope on the stack. I then worked up this simple DTrace script.

In any UNIX shell, the following will always work out of the box:

browserify src/main/lib/js/*.js > out-bundle.js

But of course, not under Windows.

And browserify does not accept directory names as primary parameter, nor wildcard globbing patterns. There is a pending issue & pull request aiming to …

I'm not really crazy about Yeoman's grunt-usemin : I find painful the way it enforces a unique pipeline, with its preliminary useminPrepare task and :generated targets.

But on the project I'm working on, we made the choice to use it early on, and we're sticking with it for now. And this …

Inspired by this tweeter post by Marcus Lagergren and the JS1K competition, here is a valid Javascript code snippet for you obfuscated code lovers:

ｰ=!+[]+!+[]+!+[]+!+[],ߺ=ｰ+ｰ,ǀ=ߺ+ߺ,ꓹ=!+[]+[],ǃ=!+[]+!+[]+!+[],ᚐ=ꓹ[+[]],ꓹ=ᚐ+ꓹ[ǃ]+(![]+[])[ǃ]+ᚐ,ᚐ=/,/[ꓹ]+[],ꓹ=ǀ+ߺ+!+[]+!+[],ꓹ=ᚐ[ǃ]+ᚐ …