skysight-inc/HackerNews huggingface dataset:
Responding to your highly inflammatory hypothetical:

You have gone from a nostrum about an entire population ("...a Black person or woman was less likely to have lead the project a priori..."), which could have included thousands-to-millions of people, to a statement about one particular individual.

The grossest error of this way of thinking is that it is mixing a vague, dubious, and unquantified signal (your a priori "knowledge") with a very high-quality signal (a specific and verifiable statement made by a single person about a single project).

If you're really proposing to do some kind of "Bayesian" weighting of these two pieces of knowledge, you're trusting your machinery for assessment of probabilities way too much. That a priori knowledge is junk compared to the statement on the resume.

Or, to look at it the other way round: If you're so well-calibrated that you're taking population-wide information into account, I shudder to think what you must be doing with other side information like the font, page layout, semicolon count, or paper composition. Lump it into the prior! What could possibly go wrong?!

I must add that you're deploying a hyper-logical argument in a real-world situation in what is honestly a stupid fashion. Nobody who does real-world inference should operate this way.
Shell languages seem to do just fine using spaces to easily specify a variable number of arguments.
In my opinion, it's good preventative care.

The problem with tendinitis, carpal tunnel, bulged neck discs, and health issues that afflict programmers is that you don't know you're susceptible until you already have the problem. Then you're looking at months or years to fix it and learn techniques and equipment to avoid its return.
> The fixation on private keys puzzles me.

Really? The private key in asymmetric cryptography should never/is assumed to never be known to anyone other than the key-holder. Session keys are understood to be shared, and so are by definition not secure (equivalently, I can log my part of the "conversation" with a server, even if over TLS with PFS). So session keys, session cookies, transmitted data -- is always known by more than one party, a secret key should never be known by more than one party.

It is true that most TLS server deployments don't enforce this -- they don't do the asymmetric operations in a trusted computing module, smart card etc -- but they should. They shouldn't store the key in ram, but they currently do.

If you get the secret key, you can do many more things than merely intercept traffic. You can impersonate and fake traffic (fake evidence).

In addition to all this, being able to read arbitrary memory controlled by the same process is also worse than being able to read stuff that is already being transmitted. This isn't strictly a Rust/other language issue (I imagine, but do not know, that one eg could sanely (if foolishly) share buffers across thread pools, and so potentially leak information across clients -- this would probably be a design error wrt. trust boundaries etc ... but no-one is arguing that any language can prevent design errors).

As mentioned in other comments, privilege separation (a la openssh etc) is a great way to help leverage the os/kernel in order to enforce assumptions about the security primitives used. But that's a little beside the point.
There are also the extremely "boring" & practical list comprehensions / iterators within racket itself:

http://docs.racket-lang.org/reference/for.html

eg. fizzbuzz using for, match:

-> (for ([i (range 1 16)])
(match (list (modulo i 3) (modulo i 5))
[(list 0 0) (displayln "fizzbuzz")]
[(list 0 _) (displayln "fizz")]
[(list _ 0) (displayln "buzz")]
[_ (displayln i)]))
1
2
fizz
4
buzz
fizz
7
8
fizz
buzz
11
fizz
13
14
fizzbuzz
>The Evoluent Mouse-Friendly Keyboard has a more sensible layout with the numeric keypad on the left so your mouse may be much closer on the right.(Patents pending.)

Moving the numeric keypad to the left deserves a patent now? I hope the patent is never issued, even with the broken system in place.
The Happy Hacking Professional keyboard solves this in an interesting way: just kill off all the keys you don't need and use Emacs-style modes.

http://elitekeyboards.com/products.php?sub=pfu_keyboards,hhk...

(It's expensive, though.)
In theory that information is used by the company to male sure they are not discriminating against any groups. Ideally that information is on a seperate sheet which is never seen by people in the recruitment process; it goes directly to HR to use for their stats.
It's a race to implement. Looks as if Mozilla is going to get there first. But, I wouldn't be surprised if Spartan/Chakra ended up surprising us with full support when it's released. https://kangax.github.io/compat-table/es6/
As California Drought Enters 4th Year, Conservation Efforts and Worries Increase
Oh, that's fantastic news! I've been sending them emails every few years requesting it, and they always said vague things like, "yeah, we're thinking about fixing that."

As it stands, I keep a $5 105-key cheapo membrane keyboard behind my Kinesis. Works okay for function keys, and Windows happily accepts input from multiple keyboards simultaneously (e.g. key chording).
Put aside many other incorrect informations written on the article, I just want to say that a couple of years ago I visited National Science Museum in Tokyo and there are two entire floors dedicated to talk about Japanese's root. One of it said that the true native Japanese came from the mainland 50,000 years ago when they first invented large ships.

Secondly, there are artifacts and ancient pots remains that can be dated 70,000 years ago and trees and something which I cannot remember well.

After years of living here, I can only say don't believe anything on the article. Especially the fact that it didn't mention Ryukyuans.
Which is made with this: https://github.com/jorendorff/es-spec-html if you really need it in HTML format :)
A well-planned architecture is often the smallest thing that works correctly. A well-architected car is unlikely to have 37 wheels (though a poorly-built one might).

You know, the ideal device is that which is not even there, but its function gets executed. This ideal is rarely attainable, but it's something to crave for.
..and people complain about transparency :)

I wasn't calling it a social engineering trick, more that it just felt like one. To the average person they wouldn't second guess the icon. To those who believe in HTTPSAllTheThings, we question anything out of the ordinary.. and that little padlock shouldn't appear in the tab.

As I said, it just felt weird, sort of the same feeling you get when you go to Apple or YouTube and there's a warning on the lock icon. You just want to hit the back button almost instantly fearing something dodgy is happening.
There is clearly some deeper political dialogue going on here. Would someone please explain it for those of us who have been living under rocks? I apologize in advance for not paying attention in advance.
Is this meant to be a general statement or just a response to some comment?

One thing I do not like about the popular "strong" encryption solutions are that they are tied to relatively "weak" authentication solutions. Instead of two programs that each do one thing, we are instructed to use one program that does two things.

I prefer that encryption and authentication were are viewed as distinct programs. If desired they can be used together. Sometimes we may not wish to rely on the hope of an "encrypted channel", but instead we might just want to send an encrypted blob over an untrusted channel (=the internet).

Obviously it makes sense to send your encrypted blob to the correct destination, but that does not mean you _must_ use encryption to verify the destination is the correct one; it is an option, but not the only one.

For example, it is possible to do the authentication part via some old-fashioned method that does not require the internet.
You're doing better (or worse, depending on your perspective) than this guy. http://www.candlepowerforums.com/vb/showthread.php?309262-I-...
Touch ID stops working after three missed attempts. Not much margin for error.
Erik Naggum [http://en.wikipedia.org/wiki/Erik_Naggum]
I'll add you to the small list of people I'll email when SuperAnimo is released.

I don't have a mailing list. I hate signing up to lists that are all talk about an unreleased product... I rather just show people when it's ready. I have a full-time day-job so I can't work on it as much as I want, but I should have a rough version live at the end of next month.
I have a default zooming of 125% and nobody seems to know how to make the web work for us with disabilities, not even gmail works well.

Scrolling pages always look weird for me. Image libraries like lightbox are a special pain in the ass.
I highly doubt it. And I doubt they will patch it.
Enough with the gates. Please. Anything else. I'd even accept stainghazi.

That said, my MBPR has some screen coating issue. But I'm not sure if I scratched it or not, so I won't join their database.
I think it's an interesting to note that site visitors are seemingly understanding our product's value and utility better than before. I see it as 1 out of 21 people "got it" enough to win their vote, and by the 3rd go, 1 out of 7 people "got it" :)
From what I was reading, the removal of the favicon in Safari was more just a UI redesign decision to remove "clutter". Personally I don't find a 16x16 icon too intrusive, but hey, what ever floats their boat. I was hoping that it was as you said, and was to prevent maliciously designed favicons from tricking users on plaintext sites (where the protocol had been stripped by the UI) into thinking they were on a secure site.

I don't use Safari, so I don't know how they render their address bar.
You're right! Hence why I disclosed that at the end :)
This is not an official list made by YC. Many companies are missing, and I've seen a couple that were not YC.
Also, a lot of the information in the article is outdated. For example, it says that the oldest pottery in the world comes from Japan 12700 years ago. However in recent years 20,000 year old pottery has been found in China.
My first expectation upon seeing the title, was that the author had done something to how irregular (3d) asteroids were affected by gravity (pulling each other and the ship) and explosions, rotations and orbits etc. [ed: not to mention fuel/weight/recoil for the ship and/or plasma boiling off asteroids from lasers etc...).]

To me this is more an example of "correct math", not "correct physics" -- although I suppose it depends on one's point of view :-)
This is sweet. I knew this was obvious enough of an idea that other people would have had it, and potentially taken it further.

One of my longer-term thoughts on this approach is that it may extend beyond simply a "controller" notion. Ultimately, I was thinking the phone could become the sole state carrier, and all other devices (workstations, laptops, game consoles, projectors) could become stateless endpoints which are ephemerally controlled as needed.

For example, you could arrive at home, connect your phone to your home computer, and initiate a "home session" which kicks off all the 'webapps' you have defined for your home-computer environment, on your home computer. The apps are structured client/server, and they save their state back to the phone (but use the computer's processing, display, audio, etc.). When you're done, you disconnect and leave. All your state is saved to your phone, and any other computer you come across can temporarily become your "home computer".

Likewise, any computer can be your "work computer". And any game console can be "your" game console.

The phone, in this context, seems like the ultimate proxy for the individual. It travels with a person. It has access to the inputs and data in the vincinity of the individual. It can be controlled by the individual. What better place to put all of your computational state, than in there?

Anyway, this was some far-fetched, pie-in-the-sky thinking I had about the long-term implications of such an architecture.

Happy to see other people working on the concept.
You missed the important thing though - Touch ID has an attempt limit, so it only works something like five or ten times and then you need to enter the pin/passcode.

The attack in the article does not work to get around this, because Touch ID does not work at startup until you have entered the code.

So brute forcing it is not going to work unless you have the passcode, in which case brute forcing it isn't super useful.
That is still an issue, but it is better than purposefully weighting admissions toward applicants who can afford full tuition.
I think perhaps you've forgotten all the ways to shoot yourself in the foot...

C++ may be an effective language for experienced users, but it's got quite the learning curve (beginning with how exactly DO I write a correct constructor in the presence of exceptions...). Every time I have to work on C++ code I dig out my Meyers book to make sure I'm not fucking something up. C is small enough that I don't have to perform the same ritual.
http://boingboing.net/2009/11/16/is-there-really-a-wa.html

"Neither in developed or developing countries is there a physical scarcity of water. The problem is lack of infrastructure, and more importantly, the lack of management. And those are things that are bad in both the developing and developed world."

Furthermore, treating droughts with water rationing actually makes the problem worse:

http://mises.org/library/clean-water-scarcity-and-market-pri...

"In the case of droughts government monopolies set prices arbitrarily and this sends consumers distorted prices. Just as bad crops increase the price of oranges so should droughts increase the price of water. Individuals then internalize their decisions to make best use of the scare resources — their own finances and the water commodity. Government distorting prices prevents individuals from acting most efficiently to conserve scarce resources."
2015 Chromebook Pixel 2 Review
I didn't learn Ivies commonly gave free rides until a while into my undergraduate at my state public university. I think what you're seeing is more an issue of questioning the specific assumptions that prevent the question from springing to mind, than it is knowing how to answer questions by searching the internet. Remember that their low-income parents and public school are probably doing very little or nothing to guide them through the applications process, and quite likely not even much to grok the sort of cultures where you have selection processes that require a lot of effort and domain knowledge, in general.

This is a non-trivial case of jootsing if you aren't already immersed in a culture that brings you most of the way to asking the question. It's a serious test of reflective intelligence, unlike SATs and acquiring grades and conforming to the college admissions process which are pretty much all about algorithmic intelligence (using Stanovich's terminology).
The few, the proud, the unwilling to be quietly wrong in their own corner.

You need us. :)
Arthur Whitney, author of A+,k and kdb/q always starts from scratch when he develops a new version of his db. From scratch means throwing away even the lowest-level routines like basic string operations and low-level file i/o.
The MS Natural Ergonomic 4000 already solves this problem [and others] for me because it works so well in my lap. The Y in this XY problem is the keyboard on the desk...well and mouse centric interface use.

Mouse ergonomics is just a weak sister of gorilla arms.
Really well written. How do you tell the NIMBY's that they're the problem? How do we get more construction and improve the lot of everyone, not just the monopolist incumbents?
Your points are clearly valids. But wouldn't some of them corrected by a strict mode?

- For instance, the reuse of the original variable could be deduced by the compiler.
- The bound checking for std::vector can effectively be enable. One could imagine an std::strict_vector that do so.

What I am wondering is: does the same idiomatic memory management applied to C++ would require some huge tweaks to the language, some bad tricks, new keywords, or can it be done without changing its design but enforcing some rules?

I, for instance, have no clues how to deal with your "one unique_ptr two threads" problem. Could it be done in an elegant way in C++?
As a generalization, the Japanese are quite interested in other cultures all over. They assimilate artifacts from other cultures, making them Japanese in the process and therefore acceptable in a way to those who are conservative.

Foreign loanwords pass easily into Japanese. They get transliterated into the mora sounds (sometimes beyond easy recognition) and written in katakana. A foreign verb instantly becomes a verb in Japanese with the affixation of -suru/-shimasu (and variations like -itashimasu). So "take-it-easy-shimasu" ("I'm taking it easy") is possible, although the "take-it-easy" part becomes something like テイクイットイージー　(teikui tto iijii). Foreign nouns slip in just as easily, and with the -na affix, foreign adjectives can be used easily. "Wonderful" becomes ワンダフル (wandafuru). Now add -da/-desu and you can say that something is wonderful: "wandafuru desu". Switch to a -na (な)and you have an adjective. ワンダフルな公園 (wandafuru-na kouen: wonderful park) (Just made that up, but Google finds quite a few results for it in quotes). Because the phonetics is Japanese and is veneered over with a Japanese writing system, it is assimilated into Japanese and thereby somehow becomes non-invasive and acceptable. There is a lot of "Japanese English": words and phrases based on English which either don't have English cognates, or the obvious cognates have different meanings. For instance マイペース (maipe-su) is derived from "my pace", and one of its meanings is the obvious one: at one's own pace. But it also means "in one's own way": one's manner of doing things, of living, whatever. Your "pace" could be that you dye your hair purple or whatever, because nobody analyzes what "pace" actually means in real English.
I just pity the poor person who learns C++. I pity myself for having learned it.
couldn't you just use a capacitor to give you a few seconds of power after the supply is cut?
Interestingly enough, one early Apple II-era input method for Chinese would generate the characters on the fly (since the hardware at the time couldn't handle storing, searching and rendering massive fonts) meaning it could generate partial Chinese characters or ones that didn't actually exist.

http://en.wikipedia.org/wiki/Cangjie_input_method#Early_Cang...

In the Wikipedia article it even shows an example of a rare character that's not encoded in Unicode but which can be represented using this method.
"rarely"?

Well, I'll say I don't have to punch in my 4 digit PIN much, perhaps that's what you meant. But the 'full password' - the Apple ID password - I have to put that in all the time. The touchID verification for apple store downloads seems to only hold for an hour or so, then I gotta punch in the full painful password again... :(
Apple-like one page scroll website
A random Carmack tweet is news now?
> As a power user I notice millisecond differences in page render times.

No you don't. Or if you do, it's a strange definition of notice. A millisecond is one tenth of how fast the centisecond counter on stopwatches change -- while one can obviously see that change, could you tell the difference between two different counters going ten times as fast, but at a difference of a couple of milliseconds? I don't think so.

One light-millisecond is ~300 km, or roughly the distance to the horizon at a height of 1000 moh, for another frame of reference.
Making chruby and binstubs play nice
Government Is Crashing the Internet Party (Marco Rubio)
Need feedback for my next course topic – which creativity course would you like
Hi Creative people! I am preparing to develop my 2nd course on Udemy and looking for feedback on what would be the best topic.
I have extensive experience in a variety of creativity and innovation tools and want to choose the one to work on. So - which of the following would you find most interesting, and what would you like to see in it?

A. 10 Ways to use Mind Mapping for Personal life and Business

B. Creative Presentation Ideas with Powtoon (based on 100 creative presentation ideas book I wrote a few years back)

C. The Creative Child - teach your kids creative skills & tools
Thanks!
Belly Fat Increased by Diet Sodas
You mean a cron/at job with curl and json?

(cron repeats, at is for one time jobs)
I completely disagree with this, but am submitting it to generate discussion.
For me, I don't think anything can replace the physical sensation of putting a key in a lock and turning it. That is, the interface feels very "real" and solid. There's something very satisfying about that.

Likewise, as I've gotten into the habit of giving the handle a strong pull after locking to make sure it's locked, I don't think a proximity system would work so well for me.
Job applications do not ask for that information. It's illegal.
The handshake conjecture
> What's the best resource (preferably online) to use to learn about Racket?

You could work through SICP using Racket instead of MIT/GNU Scheme. I'm currently in the midst of this and the differences thus far have been relatively minor (e.g. Racket doesn't have `inc`, `dec` or `nil`).
Windows 10 launches this summer in 190 countries around the world
I believe the mechanisms are something like:

1) ask for password on phone reset

2) ask for password if it hasn't been used for an authentication for ~72 hours

something about people forgetting their passwords if they never got asked for them at all
The Back Office Developers
I don't know with regards to the failures you saw. For the issues I see & fix most are in rust code.

I didn't mean to sound aggressive, we really would welcome reports of safety issues. It's hard to know if servo /really/ is safer without the hundreds of people trying to exploit it that chrome & firefox have.

Servo should be safer & I believe it's safer but I don't /know/ it's safer.
In the US you can be compelled by law enforcement to provide your fingerprint. Not so with passwords and passcodes.
Asynchronous JavaScript and XML

The name comes from this post:

http://www.adaptivepath.com/ideas/ajax-new-approach-web-appl...
> The KYC system is the exchange's, not bitcoin's

This is obvious. What is your point? Nobody is arguing that KYC is a requirement of bitcoin. Let me break down exactly what I'm saying:

1. For the vast majority of people, bitcoin is impractical as a method of payment for every day needs.

2. As a result of this, most people don't want bitcoins, and instead prefer legal tender that is usable wherever they might need to spend it.

3. The most practical and least stressful method for converting bitcoins into legal tender is through an exchange.

4. Exchanges have KYC procedures.

Very simple.
The Kinesis wants my hands aligned with each other at a set distance.

I just looked at my wrists and hands on my Kinesis. While, yes, the keys are aligned along a single axis[1], my wrists don't bend at all. It's not like you have to align your wrists with the keys, your fingers do the aligning.

[1] for the inner keys on each side. The outer columns are dropped down to accommodate the shorty pinky finger.
That happens if you turn off your device. There might be a setting or option you might need to enable. After I've restarted, I enter the password once in the store, and after that, touch ID works.
Please google "need-blind admission lie"
This is essentially the same approach as https://github.com/snowplow/snowplow/wiki/Setting-up-the-Clo....

What's neat and novel to me about this implementation is the use of delimiters vastly simplifies loading the raw S3 logs into Redshift.
This is what Apple's website looked like in 1998
This depends greatly on local law.
Why would you doubt they would patch it? Everything indicates that Apple takes this type of security somewhat seriously.