substack

8 ms·

91.
by substack 15y ago
I discussed this with isaacs in one of the nodeup episodes and we concluded that a pagerank implementation for authors and projects that reads in the npm stars and dependency graph might work. It would also be useful to consider the github
92.
by substack 15y ago
Perhaps you could just be more narrow in your searches with `npm search`? Perhaps instead of searching for "asset management" you could just search for a tool that does browser javascript bundling and then search for another tool that does
93.
by substack 15y ago
Knowing how semver works is pretty useful if you're doing node development and writing down package dependencies in package.json. semver is also for negotiating protocol version ranges between network services.
94.
by substack 15y ago
Nor should it. semver is just about versions. npm does know about tests with scripts.test in package.json and there are some projects in the works to run tests automatically from npm like CPANTS but it's still early.
95.
by substack 15y ago
Node is catching up pretty fast, although its modules might not be as mature yet: 102257 perl http://www.cpan.org/ 33270 java http://search.maven.org/#stats 31921 ruby https://rubygems.org/ 18068 python ht
96.
by substack 15y ago
I could just as easily make up a story about how males are intrinsically attracted to pink and red, the color of animal flesh from a recent hunt and how females are attracted to blue waters since in many pre-agrarian societies women had to
97.
by substack 15y ago
I really love how this project copies how the node require resolution works. That is by far my favorite thing about node and it lets programmers do version management and reusability really well.
98.
by substack 15y ago
> Let's go ahead and compare with Twisted, shall we? Oh goodness, yes. How about an echo server. This one is from the twisted home page, so I am not knocking down a strawman. from twisted.internet import protocol, reactor
99.
by substack 15y ago
The asynchronous aspects were a very small piece of the article for a reason. Node is doing a lot of very interesting, important, and novel things that aren't related to asynchronous events at all. Twisted in particular suffers from too muc
100.
by substack 15y ago
> But still, having dealt with library version issues sometimes, I think "concurrent library versioning" and "sophisticated package management" sound awfully nightmarishly black-magic to me. I guess I would be more on the "let's underst
101.
The node.js aesthetic(substack.net)
136 points by substack 15y ago|76 comments
102.
by substack 15y ago
Doing probability backwards like this is not useful and leads to fallacious conclusions and magical thinking. How is this any different from people running around misapplying quantum terminology for feel-good conclusions?
103.
by substack 15y ago
The plan is to support other test styles like jasmine and qunit through npm modules: http://testling.com/docs/#using-npm
104.
by substack 15y ago
Support for conflicting dependencies in npm is an amazingly great feature because once a piece of software works you can update little pieces of your application without worrying about whether upgrading a dependency will break some sub-depe
105.
by substack 15y ago
Hey thanks! The business of making the web a little less terrible and a little more reliable is a great space to be in.
106.
by substack 15y ago
Testling is our newest product here at browserling, so we definitely know how to make tunnels work. We just wanted to get testling launched quickly is all; tunnels are coming soon.
107.
by substack 15y ago
Right now, you do need a public IP for t.createWindow(). We have ssh tunnels in browserling already but they don't work with testling just yet. Stay tuned. I think one of the biggest benefits of testling right now is that you don't have to
108.
by substack 15y ago
We pretty much have what you're describing already, except we use node.js-style require()s with browserify instead of AMD. You can write really simple unit tests and just execute them with a curl one-liner or you can write more integration-
109.
by substack 15y ago
Yep you can use it both ways. To drive an existing page around you can use t.createWindow() and t.submitForm(), which give you a new window object and a jquery handle bound to that window object. http://testling.com/docs/#an-example-test
110.
by substack 15y ago
I suspect that people who don't "get" pointers (#4 in the article) actually have a much harder time with the pointer declaration and manipulation syntax in C than actually understanding how pointers work and what they let you do. For instan
111.
by substack 15y ago
You have to roll this yourself right now with a connection pool of stream objects. I'll probably build this out as a separate module.
112.
by substack 15y ago
It's handy if you want to map ports or host:port combos to subdomains so they all can share the same port on the same server.
113.
by substack 15y ago
I guess what I was saying there isn't the whole story, since bouncy uses node's http parser directly to handle splitting up keep-alive requests. What I meant was more that bouncy sends data over a tcp stream instead of simply passing the re
114.
by substack 15y ago
This software fills the same niche that something like HAProxy or apache virtual hosts fills right now. Bouncy is great for when you have services on your internal network or on different ports and you want to map them to subdomains.
115.
Bounce your http requests around with bouncy(substack.net)
44 points by substack 15y ago|18 comments
116.
by substack 15y ago
As I just mentioned elsewhere this thread already, browserling is rolling out exactly this service really soon! Here's a sneak peak: http://browserling.com:9088/
117.
by substack 15y ago
We at browserling will be releasing something perfect for that in a week or so! Sneak peak: http://browserling.com:9088/
118.
by substack 15y ago
Haskell is great for pure algorithms like that. As for jumping in too quickly? I was a pretty heavy haskell user for about 3 years.
119.
by substack 15y ago
I gave haskell a shot as some of my earlier github repos indicate: https://github.com/substack . I even wrote my blog in haskell with happstack, since snap hadn't gotten popular yet. Haskell is very hard, but even after 3 years of pretty i
120.
by substack 15y ago
Reading the section on ruby reminds me of the things that I take for granted in node.js right now owing to the long history of package management and module systems that it builds upon. It's super nice having the dependencies specified by s

More ›