substack

10 ms·

121.
by substack 15y ago
Presumably by modifying `require_paths` and therefore changing how `require` behaves.
122.
by substack 15y ago
Native apps in webOS are written in node.js: https://developer.palm.com/content/resources/intro_to_hp_web...
123.
by substack 15y ago
I don't see how it's specious to prefer javascript syntax over python syntax for asynchronous code. It's an aesthetic consideration and so it's less about the fact that you can have the same sorts of functionality and structures in both env
124.
by substack 15y ago
There's a link to heatmap.js in the article.
125.
Heatmaps for node.js and the browser(substack.net)
56 points by substack 15y ago|3 comments
126.
by substack 15y ago
It's handy for whipping out gdb to investigate segfaults at least.
127.
by substack 15y ago
For context, see http://blog.nodejs.org/2011/07/11/evolving-the-node-js-brand...
128.
by substack 15y ago
Oh I forgot to mention in the article, but I'm also using burrito for node-detective ( https://github.com/substack/node-detective ) to find all the require()s in a javascript file. Using detective made browserify ( https://github.com/substa
129.
Javascript AST trickery with burrito(substack.net)
64 points by substack 15y ago|6 comments
130.
by substack 15y ago
> To do that the dependency module IDs must be extracted from the module text via static analysis, but that's fairly easy since module IDs are specified to be string literals. A simple regex is usually good enough, but using one of the
131.
Node.js: batteries not included(github.com)
2 points by substack 15y ago|0 comments
132.
by substack 15y ago
Actually in node at least modules can export functions directly, just assign a function to `module.exports` and when you require() that module you'll get a function back. Plus you can add attributes to that function since functions are also
133.
by substack 15y ago
And the nodeconf slides are at https://gist.github.com/958556
134.
by substack 15y ago
Javascript compressors can intelligently remove blocks that general purpose stream compressors can't, like dead code or comments. Also because they understand the AST they can move code around to a limited extent to make the final output sh
135.
by substack 15y ago
Automatic compression isn't in there yet but you can compress the bundles using the "filter" option, which just takes a function that transforms the bundled source.
136.
Browserify: browser-side require() for your node.js(substack.net)
40 points by substack 15y ago|9 comments
137.
Salvador Dali, spatial frequency, and Lincoln(scottmcd.net)
2 points by substack 16y ago|0 comments
138.
by substack 16y ago
Isn't this what perl6 grammars set out to solve?
139.
by substack 16y ago
I suspect that previous attempts haven't been successful for a number of reasons but especially because they tend to be synchronous. Node is a great platform for asynchronous rpc because the asynchronous character is already designed to mak
140.
by substack 16y ago
Nowjs seems to have a replication system baked in with harmony proxies so when you update data structures these changes get pushed out to the clients. I chose to have dnode just make copies but I do plan on writing a replication middleware
141.
by substack 16y ago
And in the next release of Socket.IO Guillermo has promised us multiple channels, so projects like nowjs should get channels for free!
142.
by substack 16y ago
On that note, (browserify author here) I would love to see projects like nowjs start to abuse the "browserify" field in the package.json for client distribution like dnode v0.6 does (presently in staging until socket.io-node v0.7 lands). Wi
143.
by substack 16y ago
The solution I settled on for dnode is that a deep traversal finds all the functions in your argument list, pulls them out, and wraps them. This part of the protocol is a reusable module if you want to go with it: https://github.com/substa
144.
by substack 16y ago
Rival node.js RPC project (dnode) author chiming in here. This is pretty neat and I like the emphasis on getting stuff going in as few lines as possible but I'm not convinced that return values and implicit result callbacks are the way to g
145.
by substack 16y ago
Ah, your point makes much more sense now. Yes, the author had some overly complex examples, but I'm optimistic about using user-space libraries to handle flow control without having to add new language primitives.
146.
by substack 16y ago
First, why wrap your second example in try {} catch {} but not the first? The second example (final example from the article) seems like it was intentionally made more complicated to prove its point, but it could just be unfamiliarity. Nod
147.
by substack 16y ago
There's also the pushd and popd commands which are part of bash already. And there's a wikipedia entry for this even: http://en.wikipedia.org/wiki/Pushd_and_popd
148.
by substack 16y ago
Referencing objects isn't a problem since dnode doesn't do replication, it just makes copies, but referencing functions when the client disconnects can occasionally be bothersome. You do get a hook when the client disconnects: conn.on
149.
by substack 16y ago
You can pass functions around in your JSON.
150.
by substack 16y ago
I can think of a few, but "linear/nonlinear" doesn't seem like the right way to look at it. From what I've read, productivity has more to do with statistical distributions: http://xw2k.nist.gov/dads/HTML/lotkaslaw.html Very curiously, the

More ›