ljharb

it, _, result, and $ are all valid identifiers already; the only choices would have to be syntax errors currently.

npm doesn’t offer these things, so it’s not a useful comparison.

substack isn't a startup, it's a human being. Regardless of something being pg's "take", that doesn't make what you've done here ethical, or good for the ecosystem, or good for your company. (Separately, if you don't have the .com OR the twitter handle, change your name)

Change your name, how about?

default exports are precisely as tree-shakeable/dead-code-eliminate-able as named exports; this topic just isn't remotely relevant to the discussion.

A default export is what a module is; a named export is what a module has.

Both tools are useful; both are necessary; most modules should have a single default export.

1) you should be consistent, it's not your place to force users of your code what to name things 2) `import { foo as myBetterName } from 'path'`; your argument (about consistent names) is invalid :-p

nvm maintainer here: this is true - but please use `node`, since the concept of "stable" and "unstable" has died with the advent of node v4.0 using semver.

All node versions are now stable, and version numbers now communicate breakage, not stability. As it should be.

nvm maintainer here: you do not need the `v`, it will always be automatically added if you've provided a version number that doesn't already match to an existing alias.

nvm maintainer here: the only thing that's done over HTTP is the initial redirect on http://nvm.sh, which will soon be HTTPS. This URL is only used if you type it in (because it's easy to remember).

Everything else is done over Github's super-secure HTTPS - so there's really nothing to be paranoid about.

"The solution to worrying about JS lib/framework size: include one less .jpg on your site." - https://twitter.com/paul_irish/status/227203681462927361

also, https://twitter.com/trek/status/227082154109186049 and http://fourkitchens.com/blog/2013/04/24/one-less-jpg/

I use Panic's Coda for PHP, CSS, JS, and very lightly for Ruby on Rails. It needs code folding and git integration, but otherwise is quite pleasant to use and doesn't take up very many system resources.

Recurly.com

I'm about to implement Recurly http://www.recurly.com/ on my own site, on top of PayPal Website Payments Pro.

Recurly abstracts my gateway's API stuff and stores payment details so I'm not tied to my gateway - much like I wouldn't use a Comcast email address to have the freedom to change TV providers.

Worth a try. Note: I'm a potential customer of theirs and have no other affiliation.

I like it - but ABSOLUTELY turn off autoplay. Autoplay is the devil.

Don't force choices on users by playing audio for them - and if someone doesn't know how to push "play" then they don't deserve to hear music.

You should make an Amazon EC2 image and offer an already set-up service (with maintennance and whatnot) for 110% the cost of EC2. That gives me a low barrier to trying it out (it should cost me like 20 bucks for a low usage trial or less) before making the time commitment to install it.