HN user
hello: { email: "echo cuw@rrpf.orexryrl.rqh | tr a-z n-za-m", topcolor: "ffffff" }
A hearty second for mechanize. It basically wraps urllib2 which is neat. Although, I've encountered situations where language support for distributed systems would have really saved some frustration. There's a version of mechanize for Erlang [1], which I intend on trying out whenever I get around to learning Erlang :)
Here's the original Nanex source in question:
To me, the most interesting thing about PNaCl is that it'll be the first real test of LLVM as a portable assembly bitcode, rather than just a compiler IR. There are arguments for why LLVM may not be such a good idea, but given the momentum it's been making, I can only see good things happening for LLVM if more people use it.
It would be unethical to maintain a harmful allele of a gene, assuming that the particular allele is unequivocally harmful.
But that is not always the case. The textbook example is sickle cell anemia: although it is very harmful in homozygous individuals, it confers resistance to malaria without negative side effects in heterozygous individuals, which is beneficial.
There's the possibility that a harmful gene today becomes beneficial in the indeterminate future, for a reason that we cannot predict. That is the logic behind genetic diversity in a species, which allows it to cope with new and unpredictable environments by essentially allowing alleles to compete in the "natural marketplace."
If we're going to take control of our genomes and select for ourselves which alleles are harmful or beneficial, we must at least be prepared to preserve genetic diversity, if not in living individuals, then in gene banks or genomic databases.
A search on Wikipedia turned up this 1976 paper [1] (unfortunately, behind a paywall), which derived a memristor circuit emulating Hodgkin-Huxley dynamics, a good biophysical model of the membrane potential of a neuron. In particular, it can show the generation of action potentials.
The relevant part is on p. 210: "In particular, the potassium channel of the Hodgkin-Huxley model should be identified as a first-order time-invariant voltage-controlled memristive one-port and the sodium channel should be identified as a second-order time-invariant voltage-controlled memristive one-port."
[1] http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=1454361...
There's a really cool experimental history behind understanding the cochlea, especially concerning George Zweig, once a particle physicist. A lot of this work was done in the 70s and is, IMHO, some of the best examples of biophysics you can find.
One of the relevant papers you can find on google is: http://symposium.cshlp.org/content/40/619.full.pdf
To nitpick at the math: "No free lunch" results are asymptotic in the sense that they necessarily hold over the _entire_ domain of whatever problem you're trying to solve. Obviously, algorithms will and do perform differently over the relatively few inputs (compared to infinity...) that they actually encounter. It's similar to undecidability: just because a problem is generally undecidable doesn't mean you can't compute it for certain subsets of input, and compute it reasonably well (for some definition of reasonable).
I'm not a condensed matter researcher, but from what I know these particular majorana fermions are quasiparticles, so it's a little misleading to directly compare this to the Higgs boson which is an elementary particle. Still, this is cool because it means topological quantum computing might be possible:
A more extreme example along the same lines as Watchmen is the anime series Neon Genesis Evangelion. NGE totally rips apart mecha anime and gives its characters psychological issues to tragic effect, mirroring the creator Hideaki Anno's own struggle with depression.
Looks a lot like TeX, which is a good thing. In fact this might even be better. I'm tired so I might be missing an obvious weakness but to take the analogy a bit further here are some comparisons between this suggestion and a more TeX-like version.
The author's suggestion:
{b {i This is in italics and bold.}}
{Henny+Penny We can use google fonts anywhere if we just import them first with the google-font code}
{macro foobar {u {b %s}}}
{\b {\i This is in italics and bold.}}
{\font {Henny+Penny} We can use google fonts anywhere if we just import them first with the google-font code}
{\macro {foobar} {\u {\b #1}}}
http://www.nature.com/nature/journal/vaop/ncurrent/pdf/natur...
Dunno if there's a preprint somewhere.
Hmm, so gaussian distributions are easy to use and ubiquitous and all (they're the basis functions used in SVM), except that I don't see any reason for them to be priors here. But since 2012 > 2008 I feel like I'm obligated (and I'm semi-trolling) to point out the obvious about lazy assumptions based on "flexibility and tractability", which is that they can implode hilariously in your face. C.f. the financial crisis.
[1] http://econometricsense.blogspot.com/2011/03/copula-function...
Betteridge's law of headlines: http://news.ycombinator.com/item?id=4092880
From the whitepaper [1]:
After an appropriate transport period, the brain is
perfused, sectioned, suitably stained, and each section
digitally imaged. These 2-D images are co-registered into a
3-D computer stack that is subsequently registered to a
common reference atlas. The resulting 3-D brain image is
largely unlabeled (i.e., contains no signal of interest),
except for the connections between the injected region and
its target regions. Thus the labeled connections are
clearly identifiable. A given region is injected in
multiple animals to account for individual variability.
[1] http://brainarchitecture.org/mouse/documentation/project-whi...
While it could be reverse psychology to troll HNers to linking their site, it's also bad publicity among hackers, and the argument breaks Occam's razor.
You didn't include an email.
I've been having success with Go for backend work, and easy C integration in this kind of database like this would be useful for what I do. I'm not sure if R integration should be a priority though, since most R users I know are ambivalent about it (whatever, small sample size), and because Julia development continues to improve.
Have you tried just replacing redis' Lua dependency with LuaJIT yourself? LuaJIT 2.0 should be a drop-in replacement for Lua 5.1, it has the same headers and even builds the same way.
It's probably best to post this when people are headed to work in GMT or US timezones, or in the afternoon before they leave.
This whole divide-by-zero rhetoric is a little silly. A quick google search yielded the following explanation:
http://en.wikipedia.org/wiki/Kangbashi_New_Area
Ordos City itself apparently has close to 2 million people, but there's a fully developed urban housing district designed for 300,000 which has only reached 10% occupancy since 2010.
From the Kaspersky article, Flame ships with a Lua VM, sqlite3, zlib, libbz2, and an SSL library (probably OpenSSL?), and these and more apparently result in its unusually large size (almost 20 MB).
Sounds almost like "lean malware" written by a relatively small team using easily available tools and libraries.
[0] Ben Horowitz's blog: http://bhorowitz.com/
[1] patio11: http://www.kalzumeus.com/
This looks like a frontal assault on MATLAB Simulink. Knowing Stephen Wolfram's past works, I think this will turn out well.
I'm not sure economics is the right angle. This is an (re)election year, and these newspapers are all in "Virginia, North Carolina, South Carolina, Alabama and Florida." Think what you want from that.
Clarification: this is the official backend Nvidia pledged to open source a few months ago. Exciting times.
It's happened before, at least once very early on:
Google had taken ill.
The problem was the index storing the contents of the web
in Google's servers. For a couple of months in early 2000,
it wasn't updating at all. Millions of documents created
during that period weren't being being collected. As far as
the Google search engine was concerned, they didn't exist.
luajit2 in interpreter mode is also very fast, originally written in x86 (Mike Pall has probably finished the arm port by now). But I've never heard of any benchmarks between the luajit2 interpreter v. havokVM, that would be interesting to see.
Funny, on my first query I found an obscure HN scraper:
http://tazod.com/At least for me, the pinwheel is accessible and gives the website a baseline of "being fun."
A lot of people do claim it's worthless to learn math or, at an extreme, writing correctly. That's part of the problem.
Thanks, I think it's fixed. Unless I introduced another bug.