skysight-inc/HackerNews huggingface dataset:
Let me take the counterpoint: If peer review was a rubber stamping process then most journals or conference would publish most papers. Just take the journals and conferences I mentioned earlier and you'll see that their rejection stats are above 60-70% if not more.

With regard to the paper you mentioned http://jrsm.rsmjournals.com/content/99/4/178.full

You need to go beyond the title of the paper. Please read the whole paper you are referencing and then please tell me how the following extract is running opposite to what I mentioned earlier:

"
Opening up peer review
...The final step was, in my mind, to open up the whole process and conduct it in real time on the web in front of the eyes of anybody interested. Peer review would then be transformed from a black box into an open scientific discourse. Often I found the discourse around a study was a lot more interesting than the study itself. Now that I have left I am not sure if this system will be introduced...."

The simple fact is you understand peer review to mean how it is currently employed i.e. one time process used in the pre-publication stage (you do the review before the paper is published). That type of peer review is flawed as some bad papers still go through the process. What is proposed is having an on-going peer review so that over time, only the stronger papers stand. It really is not difficult to understand.
I'm the Bee in Beeminder. I think that beeminding your github account is going to be amazing for hackers/founders -- a way to force yourself to always be making forward momentum. We've been tracking how much code we write for over a year now -- though in a bit more structured way. We track user visible improvements (it has to be something worthy of tweeting @beemuvi for the hardcore fans of beeminder). We've been doing one-per-day for 733 days now and if we ever fall behind we pay a user $1000. It's been invaluable in keeping us going!
>This isn't really correct, because it ignores the fact that modern out-of-order CPU's also have out-of-order memory pipelines.

Not only that, it's assuming that a processor with 4X the clock speed will be 4X faster, and then says "well if it isn't then having 4X more cores can be better than having 4X the clock speed." Which is obviously true, but ignores that Amdahl's law isn't about clock speed, it's about single thread performance. If the brawny core has 4X the single thread performance (clock speed being irrelevant) then it still always wins over four cores each with a quarter of the single thread performance.

If there is anything to be salvaged from this it's the idea that putting, say, two brawny cores next to a whole bunch of wimpy cores is a good design for heterogeneous workloads. Which is kind of what we have with CPU (few brawny cores) + GPU (many wimpy cores). Though what might be advantageous is to see an architecture where the brawny cores and the wimpy cores run the same instruction set, so that the OS can schedule code on the brawny cores first (or put the highest priority threads there) and then if there are still any ready threads left to run put them on the wimpy cores, with the programmer not having to distinguish between the two when writing the code.
Spatial visualisation of multilingual tweets in NYC
Very long command lines on Windows
Google Glass Will Be Out Just in Time for a Very Expensive Christmas Present
http://en.wikipedia.org/wiki/Nordic_model

Here. Why shouldn't something like education, and generally doing a great job at not being completely depraved by consumerism, lead to less stupidity, and therefore also less stupidity in the form of racism? Why assume instead they're just as racist, but it's just they're all the same, so they trust each other? You can't just latch on to the first random thing that comes to mind, to me there is zero indication that any of this has to do with racial diversity, and pointing out differences in said diversity, even if I accepted them, would still be a non-sequitur, correlation ain't causation.

Maybe these people have simply realized there isn't any point whatsover in stealing random babies, which is not rocket surgery. Kidnapping? Sure. But stealing babies because you care less about people because they have a different skin colour? WTF. That's such a brainfart if you ask me.
None of the banks talked about in this article can make money. Only the Federal Reserve Banks can. Equating one of the non-profit, tax-exempt Federal Reserve banks which are controlled by the Federal Government, but "owned" by member banks with a consumer finance bank is ridiculous.

Heck this article is talking about subsidized bank borrowing costs. The Federal Reserve Banks have zero borrowing costs!
One pattern that has held-back my personal side-projects from ever achieving any real value (other than my own education) is that I'm always finding ways to drop back of schlepping and back into experimentation and analysis. Knowing this tendency in myself has held me back from any serious contemplation of actually quitting my job to start a business; I can schlep with the best when the goal is in sight and preferably there is a gun to my head (like an insane deadline I've signed up for). But I don't know how to do it when the value of the work is questionable, or so far down the road that I can't really see it from where I am now. I'm constantly plagued with "what if no one ever wants to use this?"
That was the first thing I thought too. But then I realized maybe this is more of a fear (rational or not) for those of us in the US.

However, leaving the strollers that close to a road (as in one of the photos) just seems like a bad idea no matter where you are.
> Parametric polymorphism is very simple, and has been a completely solved issue for a very long time. There is simply no excuse for a brand new language to be decades behind on something so easy to do right.

Go has addressed this; their approach is Go's interfaces, which combines the best of all worlds: duck typing with static type checks and type inference.

> Go is harder to prototype in, and it is easy to add bugs when refactoring because the type system is so poor.

This is where we'll have to agree to disagree. It's definitely not harder to prototype in - and I say this as a functional programmer - and if you find the type system to be inadequate when refactoring, it sounds to me like you're trying to write idiomatic Haskell in Go. Go's type system, by design, stays out of the way - if you're writing Go idiomatically, you really shouldn't be thinking very much about the types as you write them.

As for generics, this gets beaten to death on every single Go post on HackerNews. Yes, Go would ideally have generics. Yes, there are tradeoffs involved. Yes, those tradeoffs have been explained by the Go developers at length. Yes, they would be open to including them in the future, if somebody addressed the existing concerns. No, nobody seems to mind that they're missing from the language as-is, given those tradeoffs.
PS4 Hardware Revealed
Smart phones are ubiquitous, but people still get them snatched on BART, and they're actually holding them.
If this type of behavior continues to be tolerated by users, the entire industry will suffer the backlash at some point. A few companies using obfuscated or unclear defaults will make it more likely that the government will bring down heavy legislation on all companies.
Citi has offered virtual account numbers for its credit cards for a while, which solves the "Once someone knows your card number they can use it to conduct any transaction they choose" problem. It's still a hassle to remember to go to citicards.com and generate a new number, provided that Chrome helpfully auto-fills your saved number.
This isn't correct because in either case you're almost certainly sharing the same memory controller, which still has to service requests one at a time (if they are randomly dispersed in memory). Furthermore if the memory access takes long enough the single-core can context switch to another process and run non-blocked instructions there. The 4-core version doesn't magically have 4 times the memory pipelines, and the 1-core version won't stupidly sit waiting for a memory access to return.
Coding a Horizontal Navigation Bar with jQuery Dropdown Menus
I wish this were the case more. I graduated with and electrical engineering degree, but over the years I've spent the bulk of my time coding up DB, big data stats, ML, etc. to help me do my job. Trying to explain I'm more than capable while I falter with simple puzzle based question is an impossible gauntlet that has kept me from even considering a career shift. (Granted I'm a much better analog designer than I am a java code.)
To be honest, that looks like it has a some drawbacks when used with different domains that use the same authentication backend.

Think Google's different domains (google.com, google.co.uk, google.nl, gmail.com etc.) The demo gives a different hashed password whenever the TLD differs. And seeing that Google by default redirects you to the homepage of whatever country you're in at the moment, you might end up getting burned by the extension when travelling.
There are quite a few pictures here: http://www.google.com/glass/start/what-it-does/
I think he's taking about a solution similar to the RSA key cards typically used for VPN login at some big companies.

https://encrypted-tbn3.gstatic.com/images?q=tbn:ANd9GcSP3PxS...
Indeed, the inverted pendulum is a textbook exercise. This is how cranes work: you don't want the heavy thing at the end of the cable to swing. This is how helicopter-cranes work too, but with added wind. They almost look as if they were nailed to the sky: the only trick is to have fast sensors, which are a given for literally decades now.

The only change is that sensors are manufactured in such large quantities, that they are so cheap that they are omnipresent (ie. almost every phone -- inconceivable decades ago). Quadcopters are also more stable by design than one would think (easier to stabilize than conventional ones).
I was actually a little worried when I read that everything can be handled from the Admin GUI interface. Knowing that there are CLI tools available makes me a little more comfortable.

For some reason reading through steps like "click here" makes me less comfortable than "type this".
I don't understand this comment. Many companies share investors, especially at the level of Facebook and Spotify.

Are you trying to suggest that a mutual investor somehow has enough product control to strong-arm Facebook and Spotify into this?
Simple solution, don't use the same password for all of your accounts and read the instructions, it says username or facebook email.
>I miss the huge repositories of game reviews from sites
like GameSpy - being able to look up reviews of old games?

Try MobyGames [1] for that. They collect user reviews as well as quotes and scores from and links to reviews from professional reviewers. Unlike MetaCritic MobyGames has a lot of information on older games and references reviews from sources that may be long gone (e.g., Computer Gaming World).

I'd also suggest Retronauts [2] and Insert Credit [3] if you like podcasts.

[1] https://www.mobygames.com/

[2] http://www.1up.com/do/minisite?cId=3156908&ct=PODCASTS

[3] http://www.insertcredit.com/
As a parent of two small children, I can assure you I obsess over the plausible and common scenarios as well.

If you look at it rationally, having kids is utterly terrifying. We have logically evolved to care very deeply for our offspring. So you have this tiny living organism whose health is critically important for your own happiness. And this organism is physically separate from you, mobile, frail, loud enough to draw attention to itself, unable to protect itself, inquisitive, and completely unaware of danger.
Its in the article. Theres a minitouchpad on the right side, you enter search queries through voice, and Glass connects to your smartphone through Bluetooth to use its 3G/4G/Wifi connection.
If you look at how they were actually deployed in Europe, you'll realize that it's not much different over there. "Chip and Pin" is if anything worse than no encryption, because it gives the illusion of security. I don't know about the situation in Asia.
> The biggest promise that Node makes is the ability to handle many many concurrent requests. How it does so relies entirely on a community contract: every action must be non-blocking. All code must use callbacks for any I/O handling, and one stinker can make the whole thing fall apart. Try as I might, I just can’t view a best practice as a feature.

Nonblocking I/O isn't just a "best practice" in the sense that consistent indentation is a "best practice," it's a core tenet of the Node ecosystem. Sure, you could write a Haskell library by putting everything in mutable-state monad blocks, and porting over your procedural code line-for-line. It's allowed by the language, just like blocking is allowed by Node. But the whole point of Haskell is to optimize the function-composition use case.

The Node community has the benefit of designing all its libraries from scratch with this tenet in mind, so in practice you never/rarely need to look for "stinkers" unless they're documented to be blocking. And unless they're using badly-written blocking native code, you can just grep for `Sync` to see any blocking calls.
Yes. I think you are seriously underestimating the intellectual capacity of those people. Telling them "it doesn't matter how nice it is, or clean it is, or generic, or reusable, or maintainable, it is just to see if you can do basic introductory level code" solves the problem. Anyone who still stands there like a moron writing nothing is useless as a developer, regardless of the reason they stand there.
Why Your First Mix Is Likely Your Best Mix
I have no idea why they rejected in this instance.

Not sure if such accreditation really prove anything other than that a company is willing to jump through some hoops to get a sticker though. It's like PCI accreditation and other stuff like that.
So...what's the solution?? "Use public key encryption" doesn't help us much. Especially when you claim "it's not hard". Disposable numbers have been tried many, many times and the user experience stinks. Maybe with the prevalence of good mobile experiences, their time has come?
4 Ways Get More Traffic With Less Money
The financial companies are the most technology adverse group out there. They are risk handling and money moving engines and not interested in innovation. Every advance in technology is a direct result of legislation (like the recent addition of check scanning at ATMs) and legislation never follows the cutting edge.
Smile Plug: ARMv7 + Arch Linux + Node.js
If the the card brand, say Visa, would generate a public key that I could use on my web server to send them their credit card data, then I, my payment gateway, and maybe even my even my merchant bank, would never have to know the card number. VisaNet could decrypt it on their side with their private key and determine the issuer and account information to process it. Just the customer and VisaNet and the issuer probably needs the card number itself. Everyone else just needs to know the result of the transation.
Do you define "brawny" via higher clock frequency or more internal logic (out-of-order execution,prefetching,etc) or both? I would say "both".

> Faster processors are exactly as slow as slower processors when they're stalled - say, because of waiting for memory;

But they might not wait as often, because they have bigger caches, better prefetching logic, etc.

> Many slow processors are actually faster than few fast ones when stalled, because they're waiting in parallel;

Only if your memory supports those parallel accesses. If the memory access is a bottleneck, they might just as well wait for each other.

> All this on top of area & power savings of many wimpy cores compared to few brawny ones.

The "brawny" cores still have a lot of room to improve their power saving.

This fight is not over. I believe reality just stay complex and the answer will be "it depends" forever.
It's not really a VM. It's more like a tool set for writing compilers.
I upvoted this because I agree. I just spent about a week writing an app in Clojure, and it doesn't feel entirely like something in the Lisp Way[1]. That doesn't make it wrong, bad, immoral, etc; it is different. It has some interesting ideas which I think should be fed back into other Lispy languages via libraries (easy parallelism, immutability).

[1] This is the hard to explain part.
I didn't mean to imply it was hard. As to a test of programming knowledge, I'm glad I'm not in a position where I'm exposed to people who would fail such a test :)
Why is everyone jumping to blame Spotify for maliciousness? All I see is that they have a bug where they instantly assume emails = Facebook login. Then they try logging in using that email, and because this user reuses passwords, it works.

It takes two to Tango, but I see incompetence on both sides rather than maliciousness.
That may be, but I don't recall seeing any outrage to speak of when he was still alive.
Answering "In the context of an interview, [I get] frustrated because my default response to not knowing the answer to a question ... is to go out and research the problem [and I cannot do that in an interview]" is a nice response to not knowing an answer and would get bonus points for honesty and self-awareness.

The best candidates will recognize and comment on the ways in which frustration can be either constructive or destructive.

"This contrived situation is not one that applies to the average day in the workplace," is a serious over-generalization. Enormous amounts of code are written based on contrived beliefs about the way business does or should operate. The world would be much better off if programmers were better at recognizing and constructively commenting on these artificialities.
I think head-mounted-display virtual reality is a huge missed opportunity for next-gen consoles. They could have really done it right in a way that PCs can't yet, with special hardware support for low latency and stereo rendering, and a guaranteed large audience so game studios could justify applying their full budgets to AAA VR titles. It would be a huge differentiator at a time when consoles seem to be converging to a very similar place. It could be as big as the Wii was.
I feel stupid.
Yeah, I don't have an answer for that one.
I'm a ReQL guru!
Feels like over-reactive writing. Of course big business works to protect its interests and offload costs of business to customers. Big business is also terrified and highly resistant to change to systems that are generating profit that may reduce profit, regardless of any social value.

Why is this so shocking to the author?
The turbines become slightly radioactive. http://natgeotv.com/asia/worlds-toughest-fixes/videos/going-... but one more loop and your home free.
Wow this is really interesting. I read the title and honestly didn't know what to expect from the article when I clicked on it. My mind was wandering towards some kinda sci-fi setup or something.

Hooray cultural ignorance!
The more you know.
Quite so. I'm thinking that the whole lean startup movement in some ways exacerbates the schlep blindness problem PG refers to. If you expect instant rewards/feedback/traction before discarding an idea, you might sometimes be overlooking something.
Alright, I tried it. Frankly, I'm confused as to why this is getting so many up-votes. If someone could elaborate what they enjoyed so much, I'd be interested to hear.

I didn't enjoy this experience one bit. It didn't feel interactive to me. Each step is basically "Run this query that is already typed out for you" without any explanation, whatsoever, about what each part of what I was writing was doing. This was followed by an invitation to click a link to documentation to try something else on the line of code you don't understand.

It begins with:

>r.db('test').tableCreate('tv_shows').run()

My first questions: what is r? What does db() do? Is there a test database somewhere? Why do I have to call run() when there's a button saying "Run this query"? Do you sometimes not run() things?

The tutorial doesn't remember your position if you go back to it so it's a good thing, I guess, that it opens a new tab for you when you access the documentation to list the tables.

Let's move to the second step:

>r.table('tv_shows').insert([{ name: 'Star Trek TNG', episodes: 178 },
{ name: 'Battlestar Galactica', episodes: 75 }]).run()

Even more questions: What happened to r.db('test') that I needed to use? Is r now that database? Why didn't I just do r.tableCreate('tv_shows') before?

I did this with basically every step of the process but stopped just short of finishing because I wasn't learning much and wasn't sure where it was going. I found myself simply wondering what the heck RethinkDB was.

This tutorial could really use some more explanation, interaction, flow and direction. Tell me what I'm about to do. Tell me why what I'm about to do is worth my time and cool. Start with r, go from there. At least I won't be lost from the get-go.

Let me write stuff out as you're telling me what I'm doing. That's interacting.
There is no solution for credit card fraud because the credit card companies do not pay the bulk of the fraud that happens. I have been the subject of fraud both as a merchant and as a consumer and in both cases i was the one that paid.
this place is close, but i bet they are running into the same issues. it's a shame, because it really could stop a lot of fraud using it.
http://dynamicsinc.com/Corporate/products_dynamic_cc.php
(note, they only now offer one type of card via one bank, they seem to have been sidelined)
To me, Common Lisp appears to suffer from bad timing. It was designed on the cusp of paradigm shifts from timesharing to networking; from text interfaces to graphic interfaces; and from computers being rare to being ubiquitous. Hitting it's peak in popular consciousness in the midst of the Black Friday and S&L recession didn't help either.

My view is premised upon the idea that a major deficit of Common Lisp is a poor access to contemporary independent user interfaces. The solutions that exist are not competitive with the leverage Clojure enjoys from JVM (and .NET).
Existing Rails API Solutions Suck
I doubt that work important to the company is done this way. Otherwise, they'd expose proprietary information. Of course, I could be wrong.
A Schedule that Changes with You
As a sailor, you might be interested in Velocitek's products (http://www.velocitek.com/). I used to work for them, although now I have no connection beyond a friendly interest in seeing them do well. Solid products.
Ah, there they are. Thank you.
I never used the word malicious. I used the word "behavior". Behavior encapsulates incompetence, poor design, maliciousnesses, etc. I don't presume to know what was the behind the implementation...I just don't think it should be tolerated.
I'm groping blindly here, but from the references in that message to cgo I think it might have to do with calling into foreign code. Presumably Go's scheduler can't yield when you're inside C code (I'm not aware of any lightweight thread system that can achieve this) so you have to block there, which means you can no longer schedule other goroutines on that thread, and thus you have to spawn a new thread if you want to get any work done. But I'm just guessing here.