skysight-inc/HackerNews huggingface dataset:
Ask HN: How to feel the internet?
I've recently become fascinated by Brain Machine Brain Interfaces or (BMBIs) and similar technologies such as haptic feedback. Do any of you know any good resources for diving deeper into this subject? I love the idea of being able to feel the internet.
I am a physician in Australia.
Being a doctor sucks here too.

I encouraged my son to avoid medicine.
He followed my advice and is enjoying himself in private equity.

Anyone bright enough to do medicine would do far better in another profession.
Nicki minaj- anaconda (reaction video)
Frequentists and Bayesians care about two different likelihood functions:

* Frequentists care about p(evidence | parameters), and interpret probability as a measure over subsets of the counterfactual set of repeated trials (usually independently identically distributed) produced by their model.

* Bayesians care about p(parameters | evidence), and interpret probability as "belief" or "propensity to bet". This is, of course, philosophically ridiculous, since they proceed to ground rational belief in Bayesian statistics. What they are really doing is exactly what their likelihood function says: taking a measure over subsets of the counterfactual set of possible worlds which could have produced their evidence.

The frequentists have the advantage of their methods being more computationally tractable. The Bayesians have the advantages of intuitiveness and of yielding more accurate inferences from the same limited data-sets. Pick the tool you need and remember what you're taking a measure over!
Create Better Advertising Projects Through Video Marketing
Nice game. the mechanics are unique. I think the animations are slightly laggy (tested with my iphone 4s).
Also, the game crashed on me, but I couldn't reproduce the steps.
Subset of high-order functions are more fundamental than operations defined for a whole set?)

Clojure's are more fundamental than other languages?
It's cheaper if you heavily subsidise it and remove all future (unknown) decommissioning and waste storage costs and let the state pick those up...
Note that we haven't yet reached the end of the line as far as improvements to the manufacturing process of solar cells is conscerned, in particular http://www.nature.com/nature/journal/vaop/ncurrent/abs/natur... . Cheaper solar energy might not be far off.
writer of the article here:

I simply cannot follow the argument about "added complexity"

The use case defines the minimum amount of links you have to make, in this case 4.

Now you have two options: You just roll with it (we used to do that), or you try to abstract away a few steps (we do this now with the dispatcher).

The dispatcher here is roughly 100 lines of fairly simple, unittestable code, so I really cannot see where the elusive bugs come from. 100 lines that you will easily save if your app is complex enough by the way.

With the dispatcher, you can abstract away a couple of steps consistenly over your app. Now I fully agree that you need a certain threshold of complexity to make it worthwile.

But you cannot avoid the original complexity of your usercase.

There is no alternative to decent abstraction if you reach a certain level of complexity, because it is given externally.

Other concepts like two-way databinding do exactly the same.
AMAZING. That $2000 bottle of Margaux takes over 600 times as much energy to produce as Three Buck Chuck. I knew it tasted better for a reason.

edit: and fine, be a pain. Let's make it apples to apples and make it an ROI comparison. So $500 you can keep the panel, but I keep the retail power cost of $.15/kWh and will also increase retail prices by 4% over a 25 year period. I'm going to use 10mWh again. So 400kWh/yr, or $60 in year 1. In year 1 dollars, that is $1500 over the life of the system. However, using a handy compounding interest calculater, the 4% annual increases in power cost increase the lifetime cost of non-solar power by a factor of 2.5, so that's $3750. So we have a 600% financial ROI. That's unrealistic for solar and I'm ignoring the NPV, but I'm just working with the numbers you handed me.
+1 for Linode. Used Rackspace Cloud before, v glad if I never go back.

Also Bytemark's BigV when I want better support.
While nuclear pays for site safety, it is the tax payer that covers the decommissioning and future waste storage / processing. As the costs for this is just so obscenely high that no private company would be involved if they had to pay for it from the meager profits they'd made from the electricity they'd produced. So once again it is the tax payer that covers the damage.
It is worse as ram corruption can cause a loss of the entire zfs pool. there are no zfs recovery tools available, so data recovery can be next to impossible or very expensive.
"one thing that's surprising to many is that the floppy drive contains a CPU identical to the one in the main unit."

I don't know of other applications but there has been a Mandelbrot program that used the processor in the floppy
as a co-processor.

The C64 has a 6510 processor and the 1541 floppy has a 6502. As far as I remember the only difference are 4 additional IO ports that the 6510 has and that the C64 uses for (memory) bank switching. So for computational purposes the processors are identical.
That is the fault of the EU, they banned sales of incandesent lightbulbs in order to be green. Meanwhile the retards move back and fourth between two cities every 6 months and fly all over Europe.
Criminal investigations in the USA have obviously no legal standing in the EU. What the US would have to do in that case would be to contact European law enforcement and ask them to help them.

Which they wouldn't do, because what they would ask would be against the law.
My comparison is here: http://noelwelsh.com/programming/2014/08/17/angularjs-vs-rea...

It isn't a 100% fit for what you're looking for -- there is no case study -- but it might be useful to you.
> A piece about 1cm square costs $200 or more. Solar panels need square meters of the stuff.

Excuse me, but what planet are you posting from? Your claim above suggests that a monocrystalline silicon solar panel that's of average size (120 by 54 cm), 6480 sq. cm., should cost $200 per square centimeter, or 1.3 million dollars. In fact, such a panel costs $168.50:

http://www.aliexpress.com/item/200W-100W-X-2PCS-monocrystall...

> People in fact don't buy them - except when they get subsidies that artificially reduce the price.

All your claims have been falsified using readily available evidence.
Did you rule out Kafka? If so, on what basis?
I think "of" meant to stand for "often".

Which is still a very strong position, but not entirely out of the park - it's quite common (not only in statistics, of course) to encounter situations where not every prerequisite of a certain methodology is met, and yet the obtained results are usable in a practical environment.
Show HN: Wine, Beer or Spirits? An interactive datavis
How? Everything about this seems incredibly straightforward
It's a client-side framework. You'll generally run the JSX preprocessor as part of your website's build process (i.e. before uploading it to a server).
From the article:

Rudenko therefore resorted to including rebars in the bottom and top walls. 'They
are needed during the pouring of a variety of cementitious filling materials inside
the printed walls.' The cement used, however, is just a regular cement mix with a
few additives. 'It is possible to use a special quick-setting concrete to speed
up the process, but it will affect the cost, and I don't see much reason to build
a house extremely fast at the expense of higher cost and lower quality.'
"I don't know of any city where the local cable co offers anything like that"

Any internet provider in Moscow. It's actually even cheaper.. US internet and phone service prices are ridiculously high.
"A piece about 1cm square costs $200 or more. Solar panels need square meters of the stuff."

And that would be a real problem if solar panels producers had to have microprocessors etched into panels, had to pay the scientists to design the processors, and had to build the plants to scale that process to industrial levels, like Intel.

Happily, they just have to buy an ingot of the stuff and cut it with a saw into a 250 micrometer by 1 meter squared (or so) piece. I will leave it as an exercise to you to verify the spot price of solar grade silicon is less than $30/kg.

So lets say a panel takes 250 micrometers * 1 meter * 1 meter * 2g/cm^3 (density of silicon) * $30 / kg (assuming spot prices and not long term contracts or internal sourcing). That's 250 cm^3 * 2g/cm^3 * $30/1000g, or $15 for a whole panel of the stuff.
The Dutch secret service is at least as bad as the NSA. They just lack the scale, the budget and the opportunity.
Examples of similar products that meet your requirements?
Microarchitecture doesn't change the fact that the instructions in your program - the ones that you can work with - still have the same programmer-visible behaviour (except perhaps being a little faster.)
Since current energy storage solutions are more resource intensive (and polluting) to make than energy generation, we need on-demand energy generation.

Solar (and wind) of x MW average power means at least 2x of max power, and thus needs at least 2x of 'reserve' non-solar power to cover the gaps when it's not being produced due to daytime or weather.

This means that solar, even if it'd be completely free and perfect, can't fill a majority of global energy needs - I'd guess that a third would be an absolute maximum unless/until we get radical breakthroughs in energy storage technology.

Those types of unpredictable energy don't replace other power plants, as those nonrenewable power plants are needed anyway - they only save fuel for those plants by allowing them to reduce load at random times.
To be fair, using natural gas has an unknown future cost (global warming) which is not (properly and generally) reflected in either the cost of the gs fired power stations or the gas fuel itself.
I don't dispute that. I'm saying the model that you learn from learning assembly is very different to what the hardware is doing.

Concretely, learning assembly, you might assume each core has a set of physical registers that correspond to the registers you see and that isn't the case.
I have a technique when trying to judge actions of companies I don't really like.

If a company I liked did this would I think it's a good thing?If so, it's probably a good thing.
the word analog does not mean "not on a computer". It is also not the opposite of digital.
which is also a fantastic author anyway :)
at what point in your conception of the world do unjust laws get struck down?
Don't think that's quite what the author was getting at. A "frequentist" who makes a decision based on a p-value or confidence interval, and a "Bayesian" who makes a decision based on a posterior or predictive probability distribution, can both be viewed as making a decision according to a procedure that minimizes some statistic of a loss function.

Both of these broad families of methods are diverse, but to generalize broadly, decisions informed by "frequentist" tools are often concerned with the worst-case value of the loss function within some universe, and decisions based on "Bayesian" methods can be viewed as caring about the expected value of the loss function given some prior.

Both of those families (and many others) are "the ground truth," in that they both make statements that can be proved as theorems of mathematics. A "frequentist" confidence interval will always achieve its guaranteed coverage no matter what, if the likelihood function is true. A "Bayesian" credibility interval will include the true value of the parameters at exactly the advertised rate, when averaged over each possible value of the parameters weighted according to the prior, and assuming the likelihood function is true.

The author says, and I agree, that the thing worth arguing over is the "norm we use to choose our optimal procedure" and the nature of the loss function. Whether you care about controlling the worst case or the expected value or something else depends on what matters. (The author points out that in an adversarial situation where your strategy is known to your opponent, minimizing the worst case may be advisable...)

Some days, we care about the worst-case performance of QuickSort, and some days we care about its average-case performance (given an assumption that all input orderings are uniformly likely). It's ok to care about different things depending on the application; we don't have to split into warring tribes over it.

More here: http://blog.keithw.org/2013/02/q-what-is-difference-between-...

http://jsteinhardt.wordpress.com/2014/02/10/a-fervent-defens...

http://cs.stanford.edu/~jsteinhardt/stats-essay.pdf
A reply to ars - a 1cm piece costs 200 dollars? Because I've got a solar pocket calculator here that I'm sure I picked up for £2 and I am pretty sure wasn't subsidised. Been doing its job for a very long time too...
Are reset CSS stylesheets useful
The book mentioned in the discussion looks interesting but super expensive:

http://www.amazon.com/Introduction-Statistical-Inference-Spr...

Has anyone read it?
That is a great point, and I do think that large scale transmission (closer to a global grid) and energy storage advancements are possible, but so far have suffered from a chick/egg problems. But even so I think there's a legit place for spot generation from whatever origin (probably methane powered turbines) in a balanced energy roadmap.
Yes, I would also love us to stop using coal, and believe we should asap.

But this doesn't mean that we should be subsidising nuclear, we should be able to see and pay for the true costs of all our power sources. But instead we have crazy incentives where for residential and commercial energy contracts, the more you use the lower your unit cost. So a highly energy efficient house pays more per unit than an inefficient one.
I implemented what you describe using the BSR (BitScanReverse) instruction as base of an indirect addressing of an exponentially growing data size.

Essentially, instead of a direct addressing like V[i], you can do VV[log2(i)][i]. Where log2() is implemented with a single BSR instruction.

The addressing table for the first level is very small in size, and it can be assumed always in cache.

Here the .h/.c source:
https://github.com/amadvance/tommyds/blob/master/tommyds/tom...

https://github.com/amadvance/tommyds/blob/master/tommyds/tom...

Did you used something different ?
>Now we have to build-up renewable decentralized energy during the next decades. That's the common goal here in Germany.

Great. But Germany is also building new brown coal power plants, what's more Germany is backing a brown coal power plant just across the border with Poland. So it seems that there is a need for ongoing base load power generation... and effectively Germany is going for brown coal over nuclear.

Brown coal is, I believe, the most polluting way to generate electricity. So... why not nuclear instead?
It is the EU notbIreland that sets the framework for the legislation. Ireland has little choice.
Doesn't matter. They tow and store cars. They don't investigate the story behind each car. They don't change their policies based on how unfortunate and upsetting your story is. They tow and store cars.
I do not have much experience with Angular, however, I feel the arguments over different frameworks depend a lot on the specific nature of your app.

two-way databinding is perfectly fine and really helpful for a lot of apps. However, it will screw you for certain use cases.

In my opinion, it really boils down to how much global interaction you have in your app. If you simply render a lot of models that can only be changed trough the view, then I don't really see a reason for a Flux like architecture. Two-way databinding is perfectly fine there. (React vs whatever then boils down to performance vs toolset)

If you do a lot of graphical stuff that allows for heavy interaction, filtering and other kinds of stuff, I believe that two-way databinding will be your downfall. You need to clearly and explicitly map out on how data flows through your app. That is the time where an architecture like Flux shines.

So ask yourself this question:

"How often can a user do something in your app, and a lot of Views need to rerender?"

If the answer is "often", then you should consider something like Flux. If not, Angluar might be a better fit, especially if you already know it.
Thank you.

That step had me really confused.
Total agree, we should also be charging the coal/gas fired energy producers for the actual clean up costs, then it would be interesting to see which people want to invest in.
What about “Seacode”?
In 2005 Sea Code tried to create a "micronation" (anchoring a cruise ship right outside of US territorial waters) and use it for "nearsourcing" sw development.
Does anyone know what happened? Are they still operating? Anyone else tried the same idea somewhere else?
The site still exist: http://www.sea-code.com/ but looks like it hasn't been updated for a long time
“First they ignore you, then they ridicule you, then they fight you, and then you win.”

I guess this means we're moving into the 'ridicule' phase.
I always thought of chess as pattern recognition. But I guess that's kind of a subset of memorization.
The real question is whether Google's self-driving car is better (it doesn't have to be perfect) than humans in heavy rain (humans also have difficulties in heavy rain).
HabitRPG – A free habit-building app that treats your life like a game
That's the fault of the French. Insert Monty Python joke here.
It seems all you've done is inverted and hidden the sequence dependency in a series of waitFor chains instead of event chains, which in some ways is worse; compare

A:
update;
notify B;
B:
update;
notify C;
C:
update;
notify D;
D:
update;

with

D:
wait for C;
update;
C:
wait for B;
update;
B:
wait for A;
update;
A:
update;

The former is a clear sequential path, the latter builds up and then unwinds in a stack-like fashion. It's like the difference been non-tail and tail-calls.

It's only a technical nuisance that one model needs to wait for the other to update.

I would certainly not view a sequence dependency that's critical to correct operation as a "technical nuisance" to be hidden away; it's an important fact.
I've read this 3 times and I still can't see what the advantage of this dispatcher is.

In the event model, Events that deal with model A also have to be dealt with in models B,C, and D. Wouldn't this lead to exponential explosion?

The fact that B has to explicitly wait for A in the code also seems prone for errors. If A changes to no longer deal with that event, will B block forever?

And this still builds an event chain, because B is blocking on A. I don't see how this is different from an event chain, execpt that the dependency is non-obvious (whereas a callback chain/future chain will at least show what data is being passed into B from A)

This is maybe OT as well, but this article could really do for some concrete examples in the explanations. "Model A" and "Model B" are not examples.
mmm...that's not what I read/heard. Germany had a surplus sometimes during the year but on the average it's a consumer more than a producer.

edit : what I just wrote is untrue, Germany is a net exporter (since 2012) but suffer from the important irregularity of solar/wind production (overproduction and underproduction happen regularly and may damage the network).

And, 46% of the electricity is coming from coal...
pardon my ignorance, but what would be the difference between the two? Don't rewrite rules happen in GCH anyway?
Do Bayesian methods imply a choice of loss function? I think it's a framework for observational statistics, not for policy making or decision theory. You can use it as a tool during policy or decision making, where you should indeed have a debate about picking a loss function that corresponds to your goals.
Is there a VM image for a system running guix? I am having trouble finding one.
Intuit:

https://developer.intuit.com/docs/0020_customeraccountdata/0...
two-way databinding does not always do the same thing. Angular's digest cycle is frame-based, where everything is recalculated until you hit a fix-point. This is more analogous to the event dispatcher (A is updated, then on refresh B will) than your dispatcher example.
Kuto, לשוחח עם לקוחות ולמכור קלים כמו מגע פשוט
Exactly what i was thinking. The article seemed to me as needless bashing, thr priduct isnt on the market, its still in developement. How scared of google is the author?
<a href="www.starthacking.net/sql-injection">Nice post here is mine on SQL injection</a>
http://www.starthacking.net/sql-injection
SQL injection tutorial
What is hacker http://www.starthacking.net/what-is-hacker
The best part of the site is his piano rendition of the Martin Galway soundtrack of a c64 videogame called "parallax" -- check it out.
Would it be possible for someone to just address the complaints in the article?

"While Google's fleet has safely driven more than 700,000 miles, the autonomous model relies so heavily on maps and detailed data that it can't yet drive itself in 99 percent of the country, according to an MIT Technology Review report."
Show HN: Sofa, an Object Data Model Persistance Framework for Couchbase
It took me a while to come round to it but this kind of madness is something that Ember's event/render loop and implicit property dependency graph makes really, really easy to solve.

People knock Ember for its complexity but in reality it's simply a complete/coherent solution for the kind of problems people like this are iterating towards - and watching their code get more complex as they do.
Are there really people other than philosophers who are actually "Bayesians" or "Frequentists"?

Frequentist statistics are just a special case of Bayesian statistics with certain implicit, built-in priors - if you pick these priors using Bayesian statistics you'll get the same answers.

The frequentest toolbox is just a collection of these useful special cases of Bayesian statistics with priors that usually make sense in practice. The advantage is this greatly simplifies the statistical analysis for many problems. Sometimes these methods fail though, when the priors they rely on implicitly are far off from the actual, and so a Bayesian analysis is needed.

Of course, sometimes it's difficult or impossible to use Bayesian methods.

It's analogous to classical vs. quantum/relativistic physics. For many cases, you can get the right answer to a problem using classical physics. But under certain conditions, classical physics breaks down, and you must apply quantum or relativistic physics to get a meaningful answer. On the other hand, for many problems it would be silly or impossible to use quantum or relativistic physics because classical is perfectly good.

So you might get into argument about whether a specific case can be adequately handled by frequentest statistical methods, or whether a bayesian analysis can/must be applied.

The philosophical debate about the different approaches to the nature of probability is just that - a philosophical one, and one that has no real bearing on the usefulness and correctness of bayesian or frequentist statistics in practice.
No, the real question is can it drive in heavy rain. I've seen humans do it.
Datomic-junk: Datomic odds and ends
As others have pointed out, the prospect of fines is not the only factor motivating Microsoft. There is also the dwindling trust of potential customers in Europe. If they roll over to the US government on this one, it's another strong argument for anyone in Europe to avoid the MS cloud.
New Apple iwatch to come soon
If you are restricting your tools on the grounds of philosophy you subscribe to, you are doing it wrong. Ditch the philosophy, stick to math, try everything and go with what results in models of predictive utility. That's what actual scientists do.