> I hadn't anticipated so many comments about the web site...
Well, first, I think you need to accept the fact that you made a truly stand-out website, with a useful innovation (the Q&A format with code examples) that people are going to copy (and to good effec).
But second, the comments about the web 'preview' is the GCD of HN - Haskell, .Net, and Python programmers might still take a peak at a JavaScript library web page, even if they won't use it immediately.
Third, and this is most important, it would be significantly better if you published Papa Parse to the NPM registry, because then "real" javascript programmers can add it to their existing project with a simple "npm install papaparse --save". Publishing is trivial (install npm, run 'npm init', set values, then 'npm publish').
Thank you! And you're right about the audience and their interests. That makes sense.
I'd love to package this thing up for NPM. But I'm not a Node.js developer, so I haven't tried running this in Node. I'll see what I can do though to make that happen.
Interestingly, a lot of people are putting up non-node.js libraries on NPM (front-end stuff), which Bower, Browserify, and others take advantage of. So don't be shy, just document that it's for front end (though I have a feeling it'll probably do just fine in node anyway, the lack of dependencies makes it easy)
I meant GCD. The LCD between people on HN is arguably their personhood - but that's not useful, since it's true for every online community. The GCD of HN, on the other hand, has to do with a shared love of problem solving, particularly in fair contests. The website of a library, as opposed to the library itself, is an expression of "a solution", which we can all enjoy (and comment on), even if we don't use it in our work. Therefore website exposition speaks to the GCD of HN members.
Well, first, I think you need to accept the fact that you made a truly stand-out website, with a useful innovation (the Q&A format with code examples) that people are going to copy (and to good effec).
But second, the comments about the web 'preview' is the GCD of HN - Haskell, .Net, and Python programmers might still take a peak at a JavaScript library web page, even if they won't use it immediately.
Third, and this is most important, it would be significantly better if you published Papa Parse to the NPM registry, because then "real" javascript programmers can add it to their existing project with a simple "npm install papaparse --save". Publishing is trivial (install npm, run 'npm init', set values, then 'npm publish').