This is rather out of date and we've all moved past it. Me and Issac are cool now.
(function($){ | |
/** | |
* Register ajax transports for blob send/recieve and array buffer send/receive via XMLHttpRequest Level 2 | |
* within the comfortable framework of the jquery ajax request, with full support for promises. | |
* | |
* Notice the +* in the dataType string? The + indicates we want this transport to be prepended to the list | |
* of potential transports (so it gets first dibs if the request passes the conditions within to provide the | |
* ajax transport, preventing the standard transport from hogging the request), and the * indicates that | |
* potentially any request with any dataType might want to use the transports provided herein. | |
* |
// Start `node d3-server.js` | |
// Then visit http://localhost:1337/ | |
// | |
var d3 = require('d3'), | |
http = require('http') | |
http.createServer(function (req, res) { | |
// Chrome automatically sends a requests for favicons | |
// Looks like https://code.google.com/p/chromium/issues/detail?id=39402 isn't | |
// fixed or this is a regression. |
Let's have some command-line fun with curl, [jq][1], and the [new GitHub Search API][2].
Today we're looking for:
$ curl http://registry.npmjs.org/-/by-user/testuser | |
{"testuser":["npm-test-blerg","npm-test-publish"]} | |
$ curl http://registry.npmjs.org/-/by-user/testuser2 | |
{} | |
$ npmswitch testuser testuser2 | |
+ npm cache clean npm-test-blerg | |
+ npm owner add testuser2 npm-test-blerg | |
npm http GET https://registry.npmjs.org/-/user/org.couchdb.user:testuser2 |
Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.
Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.
In Response to http://qfox.nl/weblog/282
Peter van der Zee published this post on his personal blog and it was featured in this week's edition of JavaScript Weekly. The following sections each contain a piece of code copied directly from his post, followed by an irrefutable explanation of why it is either wrong or misleading.
EDIT, April 1, 2013: I've removed any harsh language, but the content and corrections remain the same.
From: Sam Stephenson <[email protected]> | |
Subject: Re: ruby-build hint | |
Date: Sun, 10 Feb 2013 12:25:56 -0600 | |
To: Michał Papis <[email protected]> | |
Hi Michał, | |
Thanks for the email. | |
You're right that `[[` is not POSIX sh-compliant. Nor are the following |
Sent this to the [CouchDB users list][email] just now; duplicated here for others to see or comment
Hi, all. Sorry to be distant from the community recently. No excuse.
I thought I might share December stats from one of Apache CouchDB's most well-known deployments and killer apps: the Node.js npm registry.
- Zero downtime