skysight-inc/HackerNews huggingface dataset:
Yes, to me the dress looks gold and white. Granted, we're looking at a side of the dress which is in shade (thus there's a tint). But, in my mind, the dress is clearly white and gold.

My wife, on the other hand, first saw it as blue and black. Later it seemed to change for her.
Windows defender complete guide
For context, here's a discussion from the Atom forum that we had way back in August about the future of React in Atom:

https://discuss.atom.io/t/whats-the-status-of-react-in-atom/...

There are a few issues in play here:

(1) Atom wants to support a world in which every Atom package can install whatever version of a dependency it wants, including React. This is very common in Node (incidentally, this causes problems if you want to use singletons or instanceof in Node), but fairly uncommon on the Web (where React is primarily used). That is, it's rare that you inadvertently load multiple versions of React in your single-page application. If you did, you would likely get an error when adding one React component as a child of another React component because of the way React vends ids. (Solutions are possible, but none is employed today.)

From Atom's perspective, that is a problem. The only way they can work around it is by providing "one true version of React" with Atom core that all packages must use, but then Atom is forcing all packages to use a particular version of React. That would violate Atom's philosophy of letting each package choose its own dependencies.

(2) This is not just an issue for React, but for any UI toolkit whose components are not guaranteed to interoperate across versions. To sidestep this issue, Atom has currently decided to use the DOM API/HTML custom elements. I would call this the "least common denominator approach," which satisfies Atom's design goals, but fails to provide a higher-level abstraction for building UI in Atom. It's a tradeoff.

(3) React does not currently support the shadow DOM or custom attributes, which is the new direction that Atom has chosen. As React has not yet been evicted from Atom core, I recently upstreamed a change (https://github.com/atom/react/pull/1) to add one-off support for Atom's primary custom elements, <atom-text-editor mini> and <atom-panel>, in the fork of React bundled with Atom. As I develop Atom packages using babel (formerly 6to5) http://blog.atom.io/2015/02/04/built-in-6to5.html, which has default support for JSX, building UI in React has been a lot of fun. However, the lack of support for custom attributes makes it difficult to do things like add an appropriate onChange handler to an <atom-text-editor> to update the React component's state as shown in http://facebook.github.io/react/docs/forms.html.

(4) React is still version 0.x.x, which means it has not yet committed to a stable API. This makes choosing a version of React to bundle with Atom an even more uncomfortable decision for the Atom team, assuming they were willing to do so in the first place.

None of these items implies that there is something fundamentally broken about React's model. It just means that the React team has some work to do in order to support Atom's use case. The performance graphs cited in the original post are also significant (and of interest to the React team), but even if the performance problems were fixed tomorrow, that alone would probably not be enough for Atom to pull React back into core right now.
Looks like someone has rediscovered what Edwin Land pointed out in 1959 [1] which is that the perception of a color depends on what is around it. There was a great video of Land walking with a square of one color from background to background in a single shot and the color of the square appears to change as he changes backgrounds.

[1] http://www.millenuvole.org/f/Fotografia/Per-quali-ragioni-ve...
In my talking about it on FB and with my girlfriend, yes people believe very much that it is white and gold.

I have only seen blue & black.

My girlfriend had it change color after about an hour, and started seeing blue & black. The lighting in the house & brightness on her screen were unchanged.

I didn't think "the science behind" it was very scientific. I read a better article, with a (to a layperson) seemingly plausible explanation regarding rods & cones & different types of light combinations: http://www.businessinsider.com/white-and-gold-black-and-blue...
From the post: "Smartphone owners “use an average of 24 apps per month but spend more than 80 percent of their [in app] time on just five apps.”"

So you want to be one of those 5 apps, maybe being into the other 19 is acceptable. There isn't space for everybody.

I'd like to know how many web sites smartphone owners look at every day. My unsupported by data gut feeling is that there is more space there: bookmarks are not more manageable than apps but web sites can be discovered and accessed from other sites and even linked from within apps (think FB). I won't recommend going app only. Example: Techcrunch has both and I don't think they would ditch the site. Anybody from TC here?

I dare to say that apps are for frequent readers, probably not all of them.
In the mobile apps world, some ad networks (ej. mopub) have a new type of ad named "Native Ad".

With this type of ads you have control on how you display them, and the intended use case is to make the ad look like a part of your application.

This is an explanatory PDF:
http://www.mopub.com/wp-content/uploads/2014/09/Native_Ads_O...

I believe that something similar is what the web needs.
What? No.

Political debates occur when everyone involved agrees that they're at "A" and they want to get to "B", but they disagree on the best path to take. A technical debate is when there is a fundamental disagreement about whether "B" or "C" is the better end goal.

In the EGCS case, the goal of building a cross-platform compiler collection was clear, but the process of getting contributions accepted into the mainline had become increasingly onerous for a large number of (potential) contributors. With LLVM vs GCC, there's a fundamental difference of opinion regarding the importance of modularity of the compiler stack (LLVM) vs speed and efficiency of the generated code (GCC).

In the case of node.js vs io.js, it seems to me that everyone still agrees they want an Ecma standards-compliant, evented JS runtime built upon V8 and libuv. If io.js had forked, say, because they wanted to rebase on JSCore or Rhino, then I could see the value in keeping both projects around.

As it stands, if I am a developer, and I want to help build an Ecma standards-compliant, evented JS runtime built upon V8 and libuv...then where do I go? node.js? io.js? If that choice is made based on governance model, then we're enriching the world of governance models, not the world of tech.
Who changed the title of this post and why?
It's indeed a mere droplet among total tablet sales. But given the obscurity of Jolla, it's surprisingly strong demand for something not being provided by other tablets. This could mean that slowing demand may due to current tablets, not the tablet market itself.
But the perception is different per individual, not per "what's around it."

Further, the image's colors is changing somewhat spontaneously for some people, including my girlfriend.
Today's xkcd: http://xkcd.com/1492/
That's strange, the 20-or-so people I've read that had it changed all had it change in the other direction--white & gold first, then blue & black later.

FWIW I read that the real dress, as observed in person, is blue & black.

EDIT: Girlfriend reverted. If nothing else, this is good for a giggle.
Health Experts Highlighted Nutrition Principles and Guidelines
Sublime Text is all three.
I think it's because we are pedantic. In a pedantic way no more world hunger, but people still die in car crashes, is correct. Pedantically correct.
Scala has almost every feature of C#, while the inverse is not true. I miss visual studio a bit when doing scala, but never the language. When I'm doing .NET work, I sorely miss scala.
Thanks for your reply!

I work in this field and have written lots of code, both mutable and immutable, declarative, OO and functional, to solve a variety UI problems. I've also written my own language-enabled editors using multiple techniques (see comment https://news.ycombinator.com/item?id=9117234 for the one I'm working on right now, but you can see https://www.youtube.com/watch?v=SAoRWmjl1i4 for an Eclipse-based one I did in 2007), so I've definitely got multiple feet in the game.

I don't work in Web, most of my UI code was written for Swing, SWT (Eclipse), and these days WPF in immediate mode. It seems like React is solving a bunch of JS/DOM problems, so maybe my experience doesn't transfer, but I've found that for my work, it is much easier to just go with mutable data structures that support change propagation, so you make a change that affects a line in a block (my current editor architecture, block - lines - more blocks - more lines - etc...), the change is just...O(1) because the line can be damaged/repaired directly! So why would I give that up for O(log(n))?
Atom already wraps jQuery - they wrote their own DSL for mutating the DOM called space-pen[1]. They tried to get rid of it later (and rightfully so), but its too late now.

1. https://github.com/atom/space-pen
I already proved it using computer vision that it's not black and blue :)

Stop this madness!

https://news.ycombinator.com/item?id=9117560
Yes, docker is immune to vulnerabilities because containers.
Quite a few use after free there.
Funny thing about trying to standardize products or frameworks - You start with one fine product. Someone wants a bit extra, so they make a fork of the project. Then someone tries to make an all encompassing product to cover all the subsets. So there is a third one out there. Now you have to maintain not 2 but 3 separate projects, and document everything. The same story happens so often, people still try.
LendUp (YC W12) is hiring devops, data engineers, back end engineers, and more
Why? I hear this a lot, but I never understood it. I do a lot of work with reflection to achieve things I can't otherwise do (around application extension, dynamic systems for games, etc.).

I mean, attributes are reflection, and they're absolutely invaluable.
Fantastically written article. I found the most interesting question near the end. I've never been a proponent of socialism, but in a world where work can be filled by the push of a key by unquestioning automata, could it become viable?
I had the opposite impression when looking at the React docs. JSX was intimidating and getting the quick examples to work resulted in several errors. JSX is of course optional, but the way that Angular just worked, without any non sense of installing anything, is what really drew me into the framework.
New session of Principles of Reactive Programming starts on Apr 13 at Coursera
Awesome, but I am just looking for differences in those whom perceive it differently.
On the dress, I see blue & black.

I see neither white nor black in that comic.

I do see gold, and I see a lighter blue on the leftmost dress.

Anyway, I see his point (there's a bit of an illusion), but I don't think he's mirrored what happened with the dress. The dress' background is not changing, and people view it differently.
From an user experience this optimization seems to have little effect I would guess. When you type, 2ms isn't noticeable. But it's a sign of good engineering and focus on details.
Don't frame the question implying it's a binary decision.

Ask "What should I learn _next_, ember or react?" instead.

(My opinion is that you should _always_ be learning new things that interest you. Learn them both - what you're _really_ doing is learning how to learn better. And _that's_ the skill you _really_ want. Unless you're just looking for resumé keyword fodder, in which case just grep your local job ads, I'd bet Angular would rank higher than either ember or react right now - at least where I come from.)
Still interesting is the differences in who perceives it differently. Take the survey : http://digitalorchard.co/dress/survey.html
I used computer vision to prove the image shouldn't be perceived as black and blue to us.

http://austingwalters.com/that-dress-is-gold-and-white/

A bit about myself, I've been doing research into this very thing for the past two years at UIUC.
As always, these items are only presented as "problems" because of the presence of government. So when government steps in and solves them, all pro-state individuals shout a glorious "Hurray, take that free-market!!'.

>Seat Belts: If individuals wanted them, the car companies would have followed suit. You forget that not only were seat belts mandated to be installed, but people were FINED if they didn't put them on.

>Air Bags: If there wasn't a state, I'm sure you'd have safety organizations putting out reports/studies about effectiveness of air bags. Rich people would buy them in their cars, poor people wouldn't, and they don't do that now anyways. Not sure how you see this is as something "government" fixed as it's different to seat belts, which are mandated?

>Fuel efficiency: Ah yes, another environmental tax meant to incentivize good behavior. Let me know how that's working out. All this does is drive up the cost of cars unnecessarily under the pretense of environmental benefits. Again, if people wanted it, you wouldn't have to force them to do it. This is the basic basic difference that most pro-market, and anti-market sentiments boil down to.

>Racial discrimination: This was enforced and perpetuated by state laws. Some would argue it still happens today with certain mandatory sentencing laws, minimum wage, etc.

>Taxation without representation. What? You want the market to solve a problem that solely exists because of the state, revolves around the state, and is absolutely not subject to any market forces at all? Perhaps if I could "choose" where my tax money was spent, then there would be some sort of market force driven by individuals. But that's nowhere near the case.

Now, a little more on-topic. You are absolutely right that we can't rely on the market to solve all problems, but in the presence of a state. The temptation is always there to "correct" or "slightly nudge" the market in directions we want it to go, rather than what the collective unconscious has decided. The free-market is more democracy than democracy is right now, and people fundamentally can not accept that.
Perl 6 is my MMORPG (2009)
Welcome to the wonderful world of writing portable C and C++ code across multiple compilers and OSs.
Access to the account is only possible using the private key. There is also the private key recovery function: http://en.dcoinwiki.com/Restoration_access.
However, there is a problem with twins. Only one of the twins will be able to become a miner, another will have to use a regular anonymous account.
IBM Verse – Business Email Solution
>Over 1 Billion people use a React application everyday (Facebook + Instagram web)
It's fun to actually see which parts of public websites are written with react by running this in the browser console:

setInterval(function() { Array.prototype.slice.call(document.querySelectorAll('[data-reactid]')).forEach(function(element) { element.style.background = 'rgba(255,0,0,0.1)'; }) }, 500)

Some pages to try it on: https://instagram.com/natgeo https://www.facebook.com https://www.airbnb.com.au/go/US

edit: the snippet is from Pete Hunt who is on the core React team (https://twitter.com/floydophone/status/557348616080076800)
Network API--replicate some command line program functionality into an API

Improved package tracking interface. Put in your hash and get like an actual map or something.

Browser extension to browse amazon with unit pricing. "$0.05 cents per ounce" or something.

Online app for the game werewolf
The problem with ads is that they suffer from the tragedy of commons. Each individual advertiser wants to be more prominent. All together virtually force you to block ads. In special cases, when a third party reviews all ads, as on PennyArcade, the ads tend to be much less annoying.
P.S. Isn't the PGP web of trust also a decentralized solution to Sybil attacks?

PGP web of trust requires a secure channel to broadcast the public keys, so it's not the type of P2P network that the Sybil attacks is applicable to.
It's not "just" use websockets. These may be intercepted by proxies with connection limits, timeouts or just plain not understanding websockets at all.

You will need to detect this and apply a fallback mechanism.

Which goes back to the point of this post: easy in theory. Much harder in practice.

Where I work we ended up using Microsoft's signalr-library to avoid having to learn and tackle all of these issues ourselves.

Yet we still needed to add some additional Band-Aids around the libraries provided to be able to support all cases we wanted seamlessly.
This consensus algorithm looks pretty good, but it seems it could get into trouble in cases where the distribution of outcomes is multimodal. One thing that is mentioned is that users would be reporting on several events simultaneously (let's say k events), but it seems entirely possible that there could be strong consensus among k-1 events, but multimodality in the reported outcomes for the kth event, making it very difficult to see who is wrong and who is correct for that event.

I know that Augur is planning to allow people to report event outcomes as "invalid", and that might clear up some of these cases, but what about an event where the outcome initially appears to be objective, but after-the-fact it is unclear and open to interpretation, resulting in two distinct camps of reported outcomes (and hence multimodality)? Perhaps one solution would be to simply declare events with strongly multimodal properties in the distribution of reported outcomes as invalid, and thus avoid the somewhat arbitrary decision where one mode would be declared the "consensus" by the algorithm, costing reputation to those who reported the other mode as the outcome.
I can suggest you a free educational service for those who want to learn to touch type, which helped me a lot http://www.typingstudy.com :-)
I thought you just wanted to link to both proposals and not poke at Node.
Your analysis is interesting, but it doesn't make sense to "prove" that an image is a certain color. Color is a construct of the mind. Given that so many people claim to see black and blue, you analysis proves only that your model of vision is insufficient to explain human experience.
Disappointed in W3C for Recommending Longdesc
I agree - I find React has a higher initial overhead than Angular. Frontend web development is complex, so in the long run, the complexities will still show if you make a misstep.

That said, I'm happy with my time so far with React. I haven't gone into nitty gritty engineering with it yet due to not having the time to start really coding on my project with it, but it has been fairly simple relatively speaking.

I'm excited for Angular 2 though - the amount of planning going into it is excellent, and I believe it will also turn heads with its simplicity & performance.

Frontend web development is seeing some exciting changes that should ultimately make our development ecosystem much better to work with.
I believe there are some government departments out there (Norway perhaps?) that do this.
Dear FCC: Thanks for Listening to Team Internet
My experience of bootstrapping vwo.com for the last 5 years has been the most phenomenal experience of my life. I've realized that constraint for our growth is not money, rather learning and understanding what matters in business and what doesn't. It's slow and gradual learning that I'm enjoying the most.

Last year, I was exploring whether funding could help us grow faster. Talking to VCs and the firms that got VC funding gave me the perspective that raising funds is RARELY a one-time thing. Once you raise funding (and dilute 25-30% of your company), no VC wants that money to be sitting in your bank and earn 0% interest. So your burn rate increases exponentially and most VCs want their funding to burn within 18 months. This means that in order to sustain the company you'd have to raise the next round and dilute another 25-30% of the company, and this keeps happening until exit/IPO where the investors typically end up holding 80% of the company and pretty much controlling its destiny. And remember it was who you toiled day and night to make your dreams successful.

Someone who had raised funding advised me - as long as things are going fine, you the founder are in control of the company. And if you're not growing fast-enough (think 100% year on year), the investors are in control. It's not that VC money is bad per-se, however, I think losing control of your company as a consequence of external funding is bad. Disruptions happen, new competitor emerges and you could be thrown out of your own company.

For us, having HQ in India gives us a good cost structure (although funding scene in India is changing that fast, salaries are getting through the roof) so we've been able to fund, reinvest profits and grow the company profitably (and have a nest egg for worst case). However, given the costs in SF / bay area, I'm not sure how would one go about bootstrapping a company for long. Would love to hear thoughts from fellow bootstrappers in high cost-of-living cities/countries?

PS: A bootstrapped company I really admire is Zoho. They're 1700 people and they say they have two IPOable products within the company. Very admirable.
EFF Supports Early Push in Congress to Update Online Privacy Law
I was staring good 15min to this picture and could not see anything white about it, so I'm surprised too. Another reminder that we cannot trust our perception even on such "obvious" cases.
This needs a middle-blue and gold option, 'cause thats what I'm seeing.
I can see the blue and the white but I cannot see black. Even the darkest images I'm still seeing a gold tint. Can anyone help me out?
>I'd rather you not call me anything. As I said, it doesn't matter who I am. That's not the issue I'm interested in.

Actually, argumentative technique is extremely important. Arguments only work as a method of changing peoples minds if neither side cheats.
You don't have to be a CS to select the blue channel in Photoshop.
I don't see how you get there from here. If a product requires fixed costs there will be prices paid and profit even if marginal costs are negligible. That's the software industry in a nutshell.
I see it as more gold and a blueish white hue. So not taking that survey cause it seems to constrict me into some weird combination I can't agree with.
I see white & gold, my wife sees light blue & grey, my daughter sees purple & gold and my son sees white & gold too. Strange, but a great breakfast topic of conversation
But the read and write are symmetric, of same sizes.
The notion the entire Internet will narrow down to 10 or 20 non-gaming apps, is obviously absurd. There's clearly vastly more room on the Web. It's going to stay that way.

Take a simple example. Quora, Answers.com, Yahoo Answers, eHow, Wikipedia, Stack Exchange, WikiHow, How To Geek, WebMD, Instructables - and about 87 other sites people turn to via Google for information or answers.

There's zero chance a person is going to use all of those in the form of apps. However over the course of time, I've used every single one of them via Google search results (some a lot more than others). On the Web, those services have a lot of real value; were they just apps, probably at least half of them would not exist.
I hope you’re joking. Speaking as someone who has spent many hundreds of hours reading color science papers, and another several thousand hours color-correcting photos in CIELAB space, your analysis is absurd.

If you ever come to San Francisco, I’ll be happy to explain why over a coffee.