skysight-inc/HackerNews huggingface dataset:
NYMag had a great indepth piece about how the original study was debunked, and the fallout that occurred:

http://nymag.com/scienceofus/2015/05/how-a-grad-student-unco...

Some of my favorite takeaways from the whole thing:

- How you should put time into making impressive-looking data visualizations, and to show them on a nice device. In this story, and a few others, academics and researchers talk about how blown away they were by the research because he had such great visuals:

> The iPad thing was LaCour’s trademark. “He was sort of famous for taking his results from different studies he was working on, putting them on an iPad, and buttonholing people at the conferences and going over all of the research that he was doing, the different findings he had, and basically not letting the people go until they had an idea of what he was working on,” says Tim Groeling, a communications professor at UCLA, who is listed as one of LaCour’s references on his curriculum vitae. “It was infectious,” continues Groeling. “Really cool stuff was on that iPad.”

- There is an online forum that is pretty much like 4chan for the polisci community...this is where the study unraveled, in between all the anonymous shittalking and rumors about who's getting tenure and who they fucked to get it.
That sounds rather optimistic. You really think it'll be a few years?
just hit the stop button after the text loads or use google cache.
Why rust? Why not using Go instead of C++
Perhaps you're right. Though I think the hardware you may be envisioning is different from ours. In the consideration for lipstick application, this device isn't meant to be a robotic copy of a human arm applying various cosmetics a la the jettisons. The goal is to provide makeup application: general cosmetics to specific regions of the face in a given order. From this you can develop cosmetics that can be applied via airbrush and perhaps another applicator (gel, or inkjet) that render this effect. One does not need to stick to conventional solid lipstick nor it's means of application to achieve the desired look of red upon lips. Granted there is mention of kinematics which implies robotic arms and that design path is still a consideration, but recently we have trended towards a means of application via a moveable applicator head attached to rails and guides similar to 3D printing.

As provided in previous links, airbrush is already used for applying foundation, lips, eyeshadow and blush. https://en.wikipedia.org/wiki/Airbrush_makeup
FBI's Says Tool to Hack iPhone Won't Work on 5S or Newer
I think the question was what number you used for the new LHTABLE, rather than the purpose of increasing it. That is, did you double it from 32 to 64? Choose a prime? Something else?
A bit of street-smarts also helps with those tests:

In my one, there was clearly not enough time to do all the questions.

So I picked the questions I could easily quickly answer accurately; followed by the ones I could take and educated guess; then finally as time was running out just out and out guessed the rest. I did exceptionally well apparently :-)

Then I got the job, and worked on a typical CRUD system.
Great to see React continue to improve and streamline as new versions come out. They've managed to avoid the huge bloat that happens to frameworks as they age. Kudos.
Out of curiosity, what would be the problem with say rounding the entropy to one significant digit, and storing that? The main downside I can think of is that it would help attackers avoid wasting time on passwords that are difficult to crack, and focus on the easy ones instead. But then again, if the whole point of the feature is to avoid allowing easy passwords in the first place, could it be worth it?
The answer to the first question is really interesting. We spend so much time building software and have little to show. Its nice that you are taking the effort to build something like this. I for one think APIs are still very crude and need lots of love to evolve into something that we can use without waking up at 3AM on Wednesday because somebody pushed an update. :)
It's pretty variable, but Postgres definitely is not the only one that does it that way (or even close).
That's only speculation. All Wordfence found is that their site had a vulnerable plugin and they are magically linking that to the compromise. No real forensics there.
We updated the patent grant to be less restrictive in response to community feedback about a year ago (several months after the discussion you linked):

https://github.com/facebook/react/commit/b8ba8c83f318b84e429...

Since that change I've heard few complaints, and I know for a fact that several large companies who were previously unwilling to use it are now content with the language.
Does anyone know why Mashable's twitter post links use the address "http://on.mash.to/?"

What is the purpose of using link shortening if you add superfluous characters that don't make sense "on"?

What does "on mash to" mean?
Inconvenience is hardly the reason for the 4th was put in place, saying that we can moot the whole thing because technology has solved that inconvenient bit seems really disingenuous. The 4th doesn't say "no Warrants shall issue, but upon probable cause... except in cases of extreme convenience, then we can just play it by ear."

It is a clear as daylight protection of against governmental abuse. And honestly I don't know about you, but I rather have my house searched then my computers any day of the week. One's a place I sleep, the other has deep insights on me as an individual.
The dart board is a moving target, anyways. All I care about is an average weight loss over a period of time. Maybe it's from experience, but I've never had problems consistently losing or gaining weight by eating by feel.
1) You're stepping outside of the boundaries of what every 3rd party API documents configuring ('add this to your gradle config') when I'm already too much of a bottleneck for figuring out build configuration.

2) You're replacing something that... mostly works out of the box, with something you have to configure entirely yourself.

3) Requires intimate knowledge of the entire Android build chain to properly set up. I might know about ~90% of it after some nasty debugging sessions involving flaky USB connections and commands which return 'successfull' exit codes / stdout spam when they fail - so we'll call the bus factor of that setup 0.9 as my coworkers frankly did not want to know, for which I don't even remotely blame them.

4) Yet another build dependency to install on every dev and build machine (make. *nix isn't an answer either: too many Windows specific toolchains for gamedev to make non-Windows remotely feasible as a primary dev environment.)

5) Not actually solving the remaining bottlenecks. Switching to Gradle got us down to ~5 seconds / build / project for the Java and APK packaging portion of the build, which looked mostly like it was dependency scanning, zipping, and code signing - just like I'd need my Makefile to be doing anyways. I was skeptical that I could do much better. Next, I switched linkers and saved closer to 90 seconds / build / project for even the simplest typo fix in the C++ side of things.

And that's just what's wrong with replacing gradle with a makefile. If we wanted to replace the entire build pipeline and build our C++ with makefiles too:

6) Would need to replace extensive existing MSBuild configurations entirely, or duplicate work between two different build setups. Would need to learn other platform build chains sufficiently as well (XB1, PS4, Win8 Apps... I don't recall seeing full docs on this when I still had access, although over the years I pieced together a distressingly large chunk of the pie. We'll optimistically call it 70% of the pie, for a bus factor of 0.7.)

8) Even with dependency files and substitution magic, make will rebuild more than VS with the right settings. I've also only ever done it with GCC - trying to figure out how to coax a proper dependency file out of MSVC's compiler doesn't sound fun. Mixing and matching compilers sounds like an even worse idea - a great way to introduce subtle rebuild bugs due to built-in #define differences. No, I'm not going to try and target XB1 with clang.

9) Poorer VS integration. Simple things like Ctrl+F7ing to compile / syntax check single files won't work without setting up your own keybindings to (ab)use e.g. "External Commands".

That might be most of what's wrong for my use cases.
I've lived in two studios with a less extreme size difference than that: 333sqft and 450sqft, and the difference between just the extra 117sqft is actually pretty massive in terms of flexibility.

208sqft sounds terrifying to me after living a year in 333sqft.

By contrast, if you're single and don't have too much stuff (say, a bed, a desk, TV, 2-person table, small couch), 450sqft is pretty easy. I spent three years living in that much space.
Yeah I wasn't too thrilled with Angular 2.x either. I had always been watching React and liking it, but I had no experience with it. So one day I decided to give it a whirl and see how far I could get converting the Angular 1.5 app I had already started and get it to the equivalent state in React.

Long story short, I took 40+ hours of Angular 1.5 code and converted it to React code in a single 8 hour work day without any prior experience in React. I was both impressed and giddy. The next day I merged that reactify branch into my develop branch, and continued on.

I feel that React does components better. I feel that Angular 1.5's introduction of the component sugar over top directives and even components in Angular 2.x just felt shoehorned in as an afterthought.

I couldn't even spend a day trying to figure out how to componantize this app in Angular 2.x let alone 1.5.

Now I'm head deep in learning as much about the ecosystem as I can, Redux, Relay, GraphQL, all that good stuff. I've officially ditched Angular for the React ecosystem.
> There were a number of large changes to our interactions with the DOM. One of the most noticeable changes is that we no longer set the data-reactid attribute for each DOM node.

Nice. I currently use another functional reactive virtual DOM data binding mechanism and the data attributes everywhere was one of the things that didn't appeal about react. Since react is getting crazy network effects from community I might check it out for my next project.
How are you sad if you don't know if it's true or false?
Worth noting that (a) this is an analysis of scientific consensus, so environmental effects (like the "arctic methane positive feedback loop") should already be included in the numbers if such effects are significant, and (b) GP was referring 1-3 feet in the next century, which matches your quoted numbers of 70-120 cm reasonably closely.

Still, interesting source.
In ReactConf, Ben Alpert noted that there would be a ~10% performance improvement from v15.0. Is that still true?
I think it was a PITA to learn, but it's also very necessary to interoperate with the existing JS ecosystem. Many libraries have a default export (often, a function) and then a number of sub-exports that are assigned as fields of that. Without the distinction you mention, there'd be no way to specify whether you want to import 'bar' and bind it to Foo, or whether you want to import the Foo member of bar.

Given an extra few days to learn the semantics of import vs. losing access to the millions of npm packages out there, I'd rather spend the extra few days.
What are multiple cursors useful for?
I think you are exactly right, and in a healthy market that's what would happen. In practice, I believe we are so far from equilibrium that it would take such a long time for the trickle down effects to push housing costs in a range which is affordable for people that aren't well off.

Telling people that within 10-15 years if you keep building several hundreds of thousands of houses eventually rents will be affordable is not a winning slogan :)
Even if I have different opinion, it doesn't mean I want to offend you, so please don't be so aggressive. I have no relations with Blizzard (I don't even play WoW, it was long time ago).
Thank you for letting me know who are libertarians - and yes, looks like I support this idea, but in minarchism form :)
Haven't benchmarked again, but it should be. This came from the document.createElement and reactid changes (and some associated internal refactors).
In Spain they illegalised links to infringing content (mostly movie/music downloads) by creating a "Commission of experts" which would rule on takedowns. The reason for this, of course, is that judges and courts were deeming hyperlinks were legal.

This is El Pais singing praises: http://elpais.com/elpais/2012/05/01/inenglish/1335894807_391...

Techdirt is second-hand reporting, but fair: https://www.techdirt.com/articles/20120104/04252517273/spani...

If you can read Spanish, google "Sinde-Wert jueces". This one is good: http://www.eldiario.es/zonacritica/ComisionSinde-jueces_6_16... (its author is David Bravo, a copyright lawyer who's recently been elected to Spanish Parliament, and one of the most vocal personalities on copyright in Spain).
How much of this is down to VCs/incubators insisting startups move to the Bay Area?
Technically it's not as serious as it sounds thanks to the wealth of open-source computer vision libraries and their liberal licenses. For the MVP at least.

It is a challenge nevertheless, which is why i'm doing it for fun. it's unique, has a wow factor, and would personally use it for expressing myself. I have no clue if people will want it so i'll try my best to make using the app fun for them as well.

Hopefully you'll see how fascinating it is when i post a video of the real time facial feature detection i have already completed.
Thanks for your response. I totally agree it is not useful trying to code semantic into math markups.
Sort of:

Just this morning Ray Dalio commented in an interview on problems with Fed controls via interest rates or injecting money via QE, vs times when the economy might respond better to 'helicopter money' or injecting money directly to the people.

http://www.marketplace.org/2016/04/06/world/economy-debt-cyc...

I'm reading further than the Dalio comments, but if one were to implement Basic income with some ratio of "helicopter" injection selectable by the Fed, it would give the Fed another control pedal to better manage the economy. In particular, when investment level injection is just circulating among the financial circles and not making it down to the main street economy which cycles money with buying and selling of more real goods.
Wow, out for only a few hours and they're not pulling any punches with the criticism and suggestions in the comments.

Maybe in a few months we'll end up with one damn fine app.

On a sidenote, one obviously bad thing is the overuse of referral URLs and tracking redirects for every link.
Ok, I had assumed you weren't making such an insinuation since it was an April fool's joke. It loses a bit of its punch when there's no legitimate threat to a programmer's job
Hey, can you add some detail on why you don't like electron?
It's no longer available but Yahoo used to run a service called Yahoo Pipes that did exactly this - you could take arbitrary APIs and wire them up together to do things. It was very cool. https://en.m.wikipedia.org/wiki/Yahoo%21_Pipes I guess the spiritual successor would be something like IFTTT or Zapier.
"(b) GP was referring 1-3 feet in the next century, which matches your quoted numbers of 70-120 cm reasonably closely."

Critical difference is that 1-3 feet is consensus in one case: dramatic mitigation measures.

1-3 feet is NOT the estimate for 100 years of no-action. In that case, "histrionics" as the other poster condescendingly and incorrectly called it, are far closer to reality than rosy projections of strong mitigation that simply is not manifesting in any industrialized nation. Heck, with the global recession of 2008 depressing economies and fuel usage and thus carbon emissions, many nations believe they have made progress when economic downturn is the source. We are not mitigating at all so 1-3 feet is hopelessly optimistic under today's reality...
Seems like a strange view to have. The best paying work is generally in boring, enterprise approved languages. It's probably a competitive advantage for a small company to pick a niche language - I wager they would hire better quality engineers for less money.
It's been 5 days since you commented and I've only just seen it unfortunately, although no longer relevant, I can assure you it does work. ML runs in parallel with Canon firmware. If there's a card in the camera with ML installed on it, it will attempt to run. No card with ML on it, camera boots normally. I've tripled checked both solutions. This post has also been promoted by @autoexec_bin, the official ML Twitter account. You either did something different or your camera is running a different version of ML than mine on a different camera model.
> I would argue that the obstructionism during the first two years

After the 2008 election and until the 2010 election, it was a Democrat House with a Democrat Senate with a Democrat President. It wasn't filibuster-proof (not like they do them anymore anyway) but the Democrats were in charge.
The vim language would be better if it wasn't full of exceptions that have no reason for existing (e.g. `Y` is `yy` rather than `y$`, or `cw` and `ce` being equivalent while `dw` and `de` perform different actions).
I guess the accidental mutability is a good point. Working in Scala, I've never encountered that.

You do learn not to close over local scopes in futures pretty quickly though.
This sounds like taking the design of internet and applying it to the network of devices at home. Awesome! Except I find it disturbing that a patent was issued for something like this.
For most of the libraries I've used so far, they generally seem to follow the convention of having the entire library in a single object as the default export while also exposing each individual function/property as named exports.

In the case that they don't, I generally just try "import * as Foo" to find out exactly what the library exports. Not saying this is ideal, but it really isn't too bad either, in my opinion, considering the flexibility and conciseness this approach offers for the general case.
This unfortunately breaks down with (bad acting) NIFs. Thankfully you can mark 'em as the dirty evil little things that they are (with negligible overhead): ERL_NIF_DIRTY_JOB_CPU_BOUND. [1]

I implore anyone interested in Erlang or its surrounding languages, to read its source code. [2] More specifically, the BEAM. I'll warn you that it's very 80's hackeresque, but in a good way. Incredibly pragmatic. The way they achieve their world-class scheduling? Tip: not via a perfect theoretical design cooked up in some comp-sci lab. [3] If you've been following game engine design within the last 9 years or so, you'll probably have a good idea of how they do it. [4][5]

[1]: https://medium.com/@jlouis666/erlang-dirty-scheduler-overhea...

[2]: https://github.com/erlang/otp/tree/maint/erts/emulator/beam

[3]: https://hamidreza-s.github.io/erlang/scheduling/real-time/pr...

[4]: http://blog.molecular-matters.com/2012/04/05/building-a-load...

[5]: There's a hell of a lot of depth to this problem domain. Charles Bloom's guiding principles for Oodle are spot, and well worth a look.
The easy passwords (for today) were already filtered out. The idea was to future-proof it by recording how hard they were. Rounding to, say, whole numbers still leaks information, but a bit less. So now everything from [13.5,14.5) map to 14, that's still smaller than [0,+inf]. You could use some sort of hidden value mapping them to grades that aren't obviously mappings of entropy (like A, B, C, D). It indicates that there's something about them, but without seeing a table mapping [10,12] -> C you don't know exactly what. That's still a point for data to leak, though, should the mapping be discovered (encoded elsewhere in your database or somewhere in your code).
Technically you would pay capital gains taxes on around 250k of the gain, and 500k if you're not married. You can deduct improvements/maintenance from the gain, but capital gains from owner-occupied real estate are taxed in the US if they're large enough.
>I shed exactly zero tears for someone whose $250k property quadruples in value to $1m in five years. Sell the house and dance with joy at your (untaxed!) $750k capital gain.

Ok, now where are they supposed to live? All the other properties cost just as much, so now they're forced to not only move out of the city, but now they have to quit their job too! How is this productive? You're penalizing someone for living in a housing bubble and not taking advantage of it. Even worse, you're penalizing current residents for having their house values driven up by a bunch of out-of-state (or out-of-country) investors and speculators.
Significantly better sounding synth sound is nowhere near that far out of reach. The sound he's trying to recreate is not something that comes out of a commercial stack of "$2000 boxes".

Da Funk's lead can be reasonably approximated with cheaply available modeling software, or moderately priced analog synths. Here's someone getting decently close with Massive, which is around 200 dollars.

https://www.youtube.com/watch?v=AB1_JxbT_1s

The article's sound is just still too simple. I've not used Octave, but I'm sure that with some work, it could achieve quite a bit more.
> The problem is no one really uses apps anymore

This might be a bit of a generalization. People tend to use apps for websites they visit very frequently (eg more than 2-3x a day). Even more so when the mobile version of the website is rife with bugs and/or limitations.

Reddit's mobile site is passable but the third party apps blow it out of the water on both iOS and Android.
“Windows 95 for Dummies” is the best-selling “For Dummies” book of all time
Use uBlock Origin and the 3rd-party filter "Anti-Adblock Killer | Reek‎" turned on. Works fine.
A natural key. It is not always possible, but when it is it should be used.
Facebook adds video search to combat original content sharing decline
Sounds like that is credit to both Angular and React for facilitating largely library/framework agnostic code.

I should mention that Angular 2 is quite a work in progress currently - even though it has the beta label, it still is very much far from production ready IMO. Components in Angular 2 are largely well conceived, excepting the interactions with inputs and outputs and how they interact between reusable components. React was cited by an Angular team member to me as being vastly easier to use when it comes to intercomponent communication currently - I trust the Angular team will eventually get it right, but for now there are certainly some holes.