I'm not sure, but I'd guess closing over it in the callback would work, as long as the TCP timeout is longer than the database response (even then, you could probably touch the stream every so often while you wait, perhaps via nextTick or something).
I guess it's time for me to try Plan 9 in a virtual machine again soon. Last time I tried it, I wasn't able to get it up to the point that I could use the Web browser. That's kind of necessary these days, if one wants to stick with an OS.
I have a severe (self-diagnosed :P ) case of Not Invented Here. It prevents me from hacking on Somebody Else's Code. It's why I use Ubuntu instead of Plan9 or HURD or Movitz. I really want to move toward one of those, but I just can't make myself make the time to get used to them to the point where I can add enough to them to feel comfortable that I'll be able to do anything I need to. Is there a tutorial for people like me to learn how to get involved with such a big undertaking as contributing to a partially-completed OS written by someone else?
My naming convention is naming conventions.
My server is named slogan, my tablet is named color, my netbook is named protagonist, my car (a Nissan Quest) is named Tribe, my ad-hoc wireless network's ssid is synonym, my external drive is named planet, and my server's replacement will be named category.
I'd like that a little better if it had one or two past elements for each zoom level (eg., the first column is fine, the second column needs a "yesterday" and probably a "today" for grounding, the third column needs last week, and the last column needs to be 12 months starting 1 or 2 or 3 months ago)
Ideally, whoever grants the telcos monopoly power (Is it the FCC that does that? I don't know.) should be able to enforce net neutrality. If that's the FCC, they should be able to enforce it; if it's someone else, they should.
They could just be being glib. Clipping and LOD aren't the same thing as one another. Consider the 2-D case of sampling a line (uncountably many points) for a raster display. Reimagining our favorite line drawing algorithms as search problems requires a lot of work to figure out how to best search the space. I hope these guys are doing something like that.
"searching" a "point cloud" sounds like a winner, reminds me of Seadragon's claims about bandwidth/screen resolution, but in 3D (and complicated with a search problem with probably lots and lots of parameters)
Don't think of it as substitution. Think of it as telling the computer (and thus the world). It also provides a log, so the next time you're happy or mad at them, the computer can remind you of a good thing they did.
Why doesn't the dad give his daughter points when he's proud of her? When society has a bunch of different points systems like that, social points from each individual ought to be one kind of points system. It could help make trust networks, too.
Note that this doesn't get you the applicative-order version we want, but it does satisfy the definition of Y
My = (lambda x . x x) (lambda x f . f (x x f))
= (lambda x f . f (x x f)) (lambda x f . f (x x f))
= (lambda f . f ((lambda a g . g (a a g)) (lambda a g . g (a a g)) f))
It would have taken me a lot longer to become familiar and comfortable with this culture if not for esr's help. A hard rule like "no esr" would throw the baby out with the bathwater. HN's shower has a drain.
For someone who studied Scripture in its original language, you've still managed to hit my pet peeve of pluralizing the title of the scroll of Disclosure.
The article is about the problem caused by not being explicit with our privacy intentions and expecting software to figure it out.
If we keep catering to the expectation that software will solve this problem, we'll miss out on lots of opportunities, including the opportunity to develop a privacy-aware society. People are able to learn these things. They will, if you let them.
Human nature is not a fixed value in this problem. It will grow around the best tools.