skysight-inc/HackerNews huggingface dataset:
This is cool in terms of self-expression and making the ticket more personal, and props for trying something new and building this in the first place, but does it actually solve a problem? I agree that the hassle / un-naturalness of scanning everyone in for smaller, more casual events is a problem, but I'm not sure if this solves that problem.

Unless an organizer makes this mandatory for all attendees, it's more than likely that only a minority of attendees will actually take a selfie of themselves for their ticket. And if say, 20% of attendees took a selfie and 80% did not, how does this solve the "scanning problem" for organizers?
You absolutely do not have to write your Android apps in Java. You DO need a thin bootstrap layer of Java, but with the amount of Android resources out there you don't have to write this yourself. You could make the next popular Android app and never have to touch a line of Java.

The NDK allows you to write apps in C/C++. And most other popular languages have a way to interface with C, you can use them as well. I've seen Android apps written in Python, Lua, and C#.

Also with things like Phonegap you can use Javascript if you so desire.
Cheating at Caltech
E for archive has been there since the beginning of 2008.

And, by the way, it is E because Y just removes the label, inbox label if you're reading the mail in the Inbox or the label where you're reading the mail from if you're in a label.
Not to discredit the very capable developers discussing this, but in the interest for giving credit where credit is due, didn't Peter Todd suggest this back in his Bitcoin 2013 presentation on off-chain transactions? I seem to remember him explaining something similar on a rooftop patio in Toronto last spring after a Bitcoin Toronto meetup.

EDIT: http://www.youtube.com/watch?v=4d3LA8KpdMQ#t=6m45s
CRS-3 Falcon 9 first stage to sport legs and attempt soft splashdown
My thoughts:

- Ugly, yet simple syntax
- Ugly OTP, yet powerful
- emacs
- Grumpy community, just like freebsd-dudes.
- Isn't general purpose
- Breaking meta on ever step: no loops, no variables, no strings, actors, recursions, no namespaces (i mean like in any popular language)
- Nobody writes tutorials.
- Poor library selection. Look at RoR, having 40 dependencies is okay there.
- Situations like you do everything like in Basho's getting started for webmachine, and nothing is working
- A lot of libraries that do the same thing, which is funny because it lacks of other libraries. Don't you dare ask community which webserver to use.
- If you ask about IDE on erlang@c.j.r - almost instant ban, because, you know, trolling.
This. It's amazing and powerful if you need 1m+ client connections per server. Outside of the epic scale engineering problems of facebook, twitter, google, amazon, whatsapp... It's very difficult to get anything done with Erlang.

If you have fewer than a million people using your application at a time, you're probably better off writing it in a more normal language.
The GP's claim was that:

> The rich are simply not smart enough to intelligently allocate their capital. [...] You don't see big investments in new technology, science, infrastructure, or other complex and difficult areas because by and large the financiers do not understand these things.

To me, this is saying: tech, science, and infrastructure and undercapitalized relative to their expected returns. It is very difficult for me to construct a model in which a) capital is foolishly providing too little capital to certain sectors relative to the returns it should get, and b) those sectors don't provide outsized returns to the capital they do get.

Of course, such a model is possible! It's possible that returns are random but allocations are still irrational. But what does such a model look like?

One possibility is that returns are totally unrelated to the underlying performance of an asset. For example: new technology is a more rational allocation of capital, and would provide greater return, but it doesn't, because return is totally disconnected from the performance of the technology.

To me, that possibility seems quite unlikely. Yes, the anti-EMH position holds that prices frequently depart from their underlying value--but the idea that there is zero connection, as would be required by such a model, is not tenable. It's absolutely clear that real-world events have effects on asset prices. If, say, Oculus Rift becomes extremely popular with consumers, the capital that invested in it will receive large returns.

Another possibility is that there are network effects that make it impossible to make the excess returns from these sectors unless the rest of the financial sector decides to invest in these sectors as well. But it's very difficult to see what those network effects might be, and it's even more difficult to imagine that they are present for all productive investments in these sectors.

Unpredictability of asset returns is the primary testable prediction of the EMH. On the other hand, it is difficult to construct a reasonable anti-EMH position that incorporates the observed unpredictability of asset returns.

Finally, if the claim that the market is ignoring great opportunities because of stupidity or irrationality does not imply that there are excess returns available on investments in those great opportunities, it's frankly difficult to see what the claim means. If I say "you should invest in my startup, because it's a more intelligent allocation of your capital than real estate--but no, I do not expect that you'll earn higher returns from my startup than you would from another investment," it's pretty difficult to understand what I actually mean by "more intelligent allocation."
I think Tombone5 meant Saturation and not Hue.
There are only 4 colors in that chart, the Saturation represent the density of population.

It's true that if you don't pay attention to the caption, you might think that the lighter areas within a country represent the richest people in that country, but no, it's only the population density.
I'm looking forward to see how reign turns out!
10 Skills a Developer Must Invest In
Using Tunlr's DNS servers also provides access from the rest of the world. They are still free for non-netflix/hulu sites.
... seriously?

First, my response wasn't meant as argument, it was meant as inquiry. With his "citation needed" rayiner questioned the notion that privacy against foreign governments was a right, someone pointed at UDHR, rayiner gave some grounds UDHR shouldn't be used for that. My question was accepting that premise (here); it was not intended as a statement that we have to use UDHR if he failed to come up with something better.

Second, you should be entirely aware that not every participant on this site is obligated to hold the views of the majority.

The question about Article 27 is interesting. It's poor to focus only on the second part of it, though. The entirety reads:

(1) Everyone has the right freely to participate in the
cultural life of the community, to enjoy the arts and
to share in scientific advancement and its benefits.

(2) Everyone has the right to the protection of the
moral and material interests resulting from any
scientific, literary or artistic production of which he
is the author.

I would say I agree with it, but point out that nothing in the UDHR specifies mechanism, and I think that our systems which purport to be implementation of part (2) overreach in ways that interfere with (1) (and/or just generally suck). As it happens, I don't think piracy is a great way of dealing with that overreach, but what we're seeing in that debate is the tension between people wanting to protect a particular (possibly aggressive) interpretation of one right and those wishing to reclaim a particular (possibly aggressive) interpretation of another.
I'm seriously thinking about Erlang now. What raised my eyebrows was "2-3 million concurrent connections on a single FreeBSD box"[this is what WhatsApp achieved]. Async network IO can be done with library support in Python, natively in nodeJS, etc. I wonder if one can push those stacks to this level.
Come on. Not exactly a good faith effort, is it? Why type in a rant like this, when you could have found a wonderful tutorial on Google in one tenth of the time it took you to write this?
Thanks. Yeah, the pain points I remember from learning x86 asm have to do with screwing up dealing with both 16-bit and 32-bit ints and pointers in the same program. Those were probably pretty contrived assignments, and you're right, most of the x86 bizarreness is there even if you're just doing 8086 stuff.

I just don't know if it's wrong to jump in the deep end with x86. Obviously the argument can be made either way, and x86 is ugly, but I'm pretty prejudiced toward learning something that will potentially be useful right off the bat. That would make me lean towards x86 or ARM for teaching or for self study, I think, and I have no idea what the ARM tools look like right now.

One of my more masochistic long-term goals is to make a compiler (I've made an assembler of sorts) so I might be revisiting this question at some point. Joy.
Although you have a point, it does lie within the mix of others. There are horny men in every sector/industry but yes it is much noticeable in the IT and gaming sector. However this has a lot to do with the social settings, stereotypes and minority/majority issue. I remember once setting up an Xbox account for my gf and making her play a round of some game (she is not into gaming). I was amazed at how many friend request and messages she received in such a short period of time.

There are three types of people who funded this project:

1) People who were really interested in the book.

2) People who saw a woman and thought funding it would be right thing to encourage and lessen the gender divide.

3) People who saw a pretty girl and wanted to please.

I honestly don't believe the third type of people were responsible for the majority of funding. Why? Simple, most of them would have tried to get in touch with her by now and since its not a pleasant experience getting creepy messages from strangers, had it happened, it would have been mentioned on her blogpost.

The reasons why I din't fund?

I was turned off by the marketing video. She was being unnecessarily flirtatious/kiddish with the camera. Not even once did they show an actual kid in the whole video, let alone trying to get them to learn from it.

I din't have a need for the product, or it wasn't appealing enough to have it for my nephew and niece.
What is up with the obsession to get women coding? Why does it matter? You don't see anything like this in female-dominated professions.
Don't be an idiot: a straight forward interviewing strategy that works
You can recover a substantial portion, but there's a few things you can't quite get back. Since Go is a mutable-state language, and also a shared-state language (isolation is by convention, not by language design), you have to live with the consequences of that. In my supervisor tree implementation, the restart of a monitored goroutine is just to fire off a new goroutine on the exact same object again; if you still have bad state lying around and immediately crash again, well, too bad, the supervisor can't do anything about that. (Except not thrash the processor with endless restarts.) In contrast, when an Erlang supervisor restarts a process, it is guaranteed to be a fresh process with no shared state from the one that just crashed. It's much more likely to not immediately crash.

(I fiddled with having the user specify a closure that is supposed to "create" a new object for the restart, but then simplified that away when I realized that the closure itself could well have mutable state too. Better just to stick with the simpler interface and document the consequences of failing to clean out state at the beginning of your monitored code. On the plus side, so far the interface for the supervised-things is "Serve()" and "Stop()", and nothing else; hard to argue with that level of simplicity!)

You also won't ever be able to recover live code restarts; you can try to transfer all state to a new process, including file handles, but that's a lot of implementation work. (I'm stuck right now on the fact that my connections are encrypted, and the encryption code won't let me even get to the state, let alone transfer and reconstitute it somewhere else. Someone's got some code for moving file handles around on GitHub but I can't seem to Google it up.) Most people already live in a world where live restarts are difficult or impossible, though, so they won't miss that. Getting a REPL into a live Go server is impossible, at least with Go itself, and will also probably never be as clean as Erlang. (Go "2.0" could fix that with an official Go interpreter, which is the missing bit. I can handle the sockets, I can bind readline and give you a nicer REPL, but interpreting Go is a challenge. Progress is being made, I believe as part of the new compiler implementation, but I'm not sure anyone has this as an explicit goal.) Again, most people live in a world where they already don't have a REPL into their running code, and therefore won't miss this.

There's also some more subtle semantic differences, but I'm saving that for a blog post. (It gets long, especially if I first have to explain Erlang, which is what the blog post does.)
>It amazes me how often ‘how to be happy’ pieces do well on Hacker News. I think delving into the notion that the more time we spend behind our computers, the less fulfilled we might feel in life overall [is a question worth asking].”

I think unhappy people procrastinate more, vote more. The average vote is not given by the average reader, but one more depressed than average.
It could be with a little more work. I don't currently support manufacturing, but do have kitting. You can have one SKU depend on multiple SKU's so that if one is ordered it'll place the sub SKUS as well.

For proper manufacturing we'd have to expand that to generate a build order and factor labor into the GL postings.

It's on my informal roadmap but no idea when/if it'll get done. If you're interested in sponsoring that, I'd love to talk! (nathan@argosity.com)
It prints no errors.
The lack of hysterisis and creep means that you can drive them with and open loop drive system. That is a much simpler system to build.
Then it's either Simple, Simple's state of incorporation, or their specific agreement with Bancorp. Whatever it is, the IRS says it's not them.
I suspect lucian1900 was being sarcastic. At least, that's how I read it. I'm not quite sure how anyone could make that much of a stretch with a straight face.
Show HN: Find and Watch TV Shows on YouTube with CouchTube.net
I suppose it saves small events from needing to have a scanner.
Inside Erlang - the rare programming language behind WhatsApps Success
Original article: http://poisson.phc.unipi.it/~maggiolo/index.php/2014/01/how-...
When I decided I was going to get my pilot license I planned to do so efficiently, without burning cash unnecessarily (yeah, right) -- I was prepared with my own plan for every flight... I'd heard numbers in the $8k to $10k ballpark and thought "I'll target that".

It still cost me $15k (in 2012 -- airplane $11k, instructor $4k) to get my Private Pilot License -- plus another $2k in optional expenses like a good home simulator set-up, iPad software, books etc. -- some of which arguably should have made my training more efficient.

While I don't know the costs of getting a Sport Pilot license, I have wondered if it would have been the better route for me.

The difference between the times I fly with a VFR Private Pilot license is virtually no different than I would with a Sport Pilot license. I rarely have more than one passenger (one is limit for Sport Pilot license), and I rarely fly at night ('engine out' at night is beyond the risk I'm willing to take), I've never been above 10k feet.
Continuous Deployment With Github
Depreciating vs investment assets is orthogonal; both lose value more slowly than money in a hyperinflationary situation.

And yes, there are trade offs, one of which is the malinvestments from spurring people to hold non cash. My point was that this, plus the individual welfare loss of the hoarder from having to commit to purchase sooner, must be weighed against the purported benefits of (what you got people to do via) inflation -- and (as I said at the beginning) that most people who make that argument for inflation (even economists) don't offer a way of modeling those relative benefits.

It's like arguing for an apple subsidy on the basis that apples are good, without even thinking about the costs of such a subsidy (ie diversion from non-apple production).
OT: This page instantly kills my Android browser...
As an alum, this is depressing.
Startups, Do the Math
> Clojure beats the pants off Erlang when it comes to performance

Source?
Driving Around The World To Prove Plastic Bearings Are Superior to Metal
> I liked it more than SPARC assembly

Now that's interesting. What is the deal there?
Totally agreed. And more generally, specificity is by far the most difficult challenge in large-scale CSS. Without discipline and some well-defined conventions for selector construction, you will end up with the equivalent of spaghetti code and late-nights deciphering unexpected cascading from other people's styles.

Since large projects will inevitably have to rely on non-semantic HTML and class names anyway (e.g. to differentiate between sibling <p> tags), a simple rule of thumb would be to only use class names in selector construction. HTML elements can still be semantic for other purposes, but the CSS should not care about it.

The other half of the specificity problem is nesting. I advocate strongly against the descendant combinator ` ` in favor of the child combinator `>`. E.g. `.body > .content` is much more robust than `.body .content`. However, an alternate approach would be:

<section class="body">
<main class="body-content"></main>
<aside class="body-sidebar"></aside>
</section>

Either way, don't leave it up to individual developers. This has to be adopted by the team.
Oh, please $deity, no.

I love JNPR and their products and would hate to see how Nokia might butcher them. Although as long as they left the software alone (particularly on the SRXs), I'd be happy. IPSO, while nice and "advanced" (for its time), was an overly complex beast.
No, the big cities shouldn't shouldn't be blue. The average person in eg Shanghai isn't earning over $12,000 per year. Purple most likely however.

"Shanghai's urban residents, with an average disposable income of 40,188 yuan (US$6,379) last year, earned the most among China's 21 provincial areas that have posted their income growth, according to the latest data."

http://www.china.org.cn/china/2013-01/26/content_27800262.ht...
As one of those expats (starting my 8th year in a little fishing village in pacific coastal ecuador), can I just say --

We're on pay-as-you-go plans, but usually on nice phones we brought unlocked from our home countries. I'm typing this on my trusty Air, which is tethered through an unlocked iPhone 4S.

I'm also listening to waves crash. We got our first swell in a month yesterday, and non-locals are showing up a day late ... 4 or 5 of them. A crowd. I was the only one out for the good stuff yesterday, and I sucked the marrow out of it, and am instead enjoying sitting on my balcony drinking coffee and vagando here on HN. Ahhh.

Where was I? Oh, yes.

I can confirm the crazy-fast penetration of both smartphones in general (probably way over 90% android), WhatsApp in particular, and the FB/WhatsApp/SMS mix.

So WhatsApp isn't the internet here yet. But it's definitely got brand parity with Facebook around here. Which is pretty amazing considering their relative valuations.
Yep. That's why book selling ranks started to separate in self help and fiction categories. Otherwise there will ever be self help on the top chats.
Why you shouldn't use vagrant: Real talk from a Vagrant burn-out
Yes, you do.

Nursing:
http://www.minoritynurse.com/tags/men-nursing

Teaching:
http://www.timesfreepress.com/news/2013/mar/23/advocates-say...

".. who bring a different perspective to the job, may connect better with some children and can provide positive male figures in their lives."

Same goes for women in technology or any other misrepresented field.
I'm always baffled by these kinds of statements. I learned ocaml first, so haskell wasn't too big a leap for me. But I did get to watch my wife go through the process of learning haskell, and she didn't have any more problems than learning any other language.

My wife is a web designer. She has no interest in programming. She taught herself PHP and javascript because she needed to use them. When she finally got to the point where she couldn't tolerate PHP's shittiness anymore, she asked me what she should use instead. I said "scala is a good choice, or you could just skip a step and go straight to haskell". She tried both, decided on haskell because she didn't like lift or play, and proceeded to teach herself haskell. She has never read real world haskell, or even learn you a haskell. I just asked her what a monad is: "Beats me, just use do and the arrow things". She's already finished two big websites written in haskell. This idea that you need to be a compsci phd or something to use haskell is simply not reality.
I do not have direct knowledge, but I'm pretty sure the problem with "network" channels in Go is the synchronous nature of channels. Even if we did have a perfect network, that works poorly across a network, and if the network starts degrading even a bit the sync channels just completely fall apart. The language treats them as a fast synchronization method. You can very nearly translate RPC to "channel" in this argument and it works: https://news.ycombinator.com/item?id=2318249 (Err, I did try to find a better explanation that wasn't mine, but Googling up an RPC criticism was hard, because saying "RPC" comes up with a pretty big search pool to be trying to find the word "bad" in...)

My reign library basically just ports over the Erlang idea; asynch messages, PID-like things that can be transmitted across the network and identify the same mailboxes within a cluster. It's meant to be a porting aid, not a solution you'd reach for in Go to create a brand new program. (If you do that, it's on you.) Clustering like this is nontrivial and the big reason I'm sitting on the code locally until clustering is at least working under some circumstances; without clustering support, the mailboxes are just an invitation to write nonidiomatic code for no gain.