37 karma · joined October 28, 2010
Too bad the site is incredibly slow. Here's a link to the cached "Travel" page: http://webcache.googleusercontent.com/search?q=cache:http://...
I guess then my question is whether "hackers" as an early-adopter group are worthwhile for targeting. Anyone have any anecdotes where a mainstream product started as a hacker niche?
If you include CRAN packages, then this couldn't be further from the truth: http://addictedtor.free.fr/graphiques/
R can be made to produce beautiful visualizations.
Edit: here's a link to the top-voted thumbnails of R visualization: http://addictedtor.free.fr/graphiques/thumbs.php?sort=votes
IMO, since it can be scripted from the command line, it's high time Gnuplot died a graceful death.
(1) Hackers/nerds are early adopters. Thus, they will influence "normal" people to use products that they judge to be superior.
(2) Hackers/nerds are a tiny proportion of the population with no real influence. They might push esoteric but superior technologies, but large-scale adoption will ultimately be driven by how quickly cat pictures can be shared with the largest group of people.
The author of the article clearly believes in (2), but Apple seems to be making money off (1). So which is it? Or is this some sort of false dichotomy to begin with?
I've been thinking about a general purpose experimentation framework for research. Over the last 5 years, I've been re-writing parts of this framework for different projects and wish I had spent some time generalizing and packaging it.
The workflow is:
dataset -> experimental parameters -> code+libraries (this is where the trouble often is) -> result files (plain text, hundreds!) -> analysis (generally in R) -> selectively plotting results
BTW, even with a "uniform" Linux environment, I've been finding so many differences in the behavior of libraries that it's driving me nuts. This will be a nice way to get past, for example, inconsistencies in wxWidgets.
Canvas allows access to individual pixels in an image, and JS is arguably faster than BASIC interpreters of the 80s. Fun things lie ahead in client-side image processing.
EDIT: Incidentally, the code is pretty hairy and has about 3 comments. It's hard to figure out what ML approach he's using from a cursory look.
EDIT: Aah, definitely an image pyramid in there, so some multi-resolution stuff happening.
The bottom line is that with keep-alive connections, the overhead should be less of a problem, since the only expensive part is the initial RSA key generation.