skysight-inc/HackerNews huggingface dataset:
My 11 Year Old Nephew Will Stun You
"Switched"? Everytime I see the word, it screams "novice." A programmer should know when to use a language. Every problem is not a nail, so to speak. A more interesting article would be about JS/Ruby developers who learned to use Go.
And putting Go and "front end development" in the same paragraph currently makes little sense.
I'd have to say you lucked into a pretty special deal and not representative of much within 20 minutes of SF (and is that 20 minutes at midnight or during rush hour?). :-)
WHAT ARE YOU A FUCKING BALD EAGLE? OH LIKE MY WIND POWER IDEA?

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

go beat rodney king you fucking bald headed fucks

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

and tell hpil taylor he had bad "intel" lol.

FUCK U AMERICA>

1971. whAT A GREAT YEAR.
Best way to handle interviewer asking me out on a date after tech screen?
Modifying the DOM is usually the bottleneck in web apps. To get a fast app (extreme simplification), you need to only apply the minimum set of mutations. It turns out that in a large codebase this is extremely hard to do. React asks the developer for a virtual representation and computes the diff between the previous one. In most situations, the time it takes to compute the set of mutations is negligible compared to the cost of the unneeded dom mutations it removed.

But, if you need extremely high performance and your problem is small (eg: the text editor part of atom), you can write specialized code that will compute the minimum set of mutations yourself and don't pay the cost of React. That's also why you see so many small benchmarks beating React but those wins don't translate in real applications.

Now, it doesn't mean yet that you should drop React. The great thing is that you can make a React component <TextEditor> that itself uses manual dom operations to be super fast. And the rest if your app uses React for its wins.

In Atom case, they also want to support people writing plugins. Now it's not only technical but becomes political. Do you want to force people to use React for writing plugins? What if they want to use jquery or ember or angular?

You also get into dependency issues. React requirement today is that there can only be one version loaded at the same time, otherwise everything breaks. If you update React in Atom core, you run the risk of breaking all the plugins that were written for a different version of React.

Given those, it makes sense to remove React as a dependency from the core. Fortunately, it's still totally possible to write atom plugins using React
Dutch Offer Preview of Net Neutrality
60x faster, 10x less memory, 1 new unit test, in 41 fewer lines of code
What do you think of the Jolla/Sailfish tablet? It raised almost 5X of their target and pre-order demand has been so strong that they reopened the crowdfunding campaign. Sailfish is a descendant of Nokia Maemo/Meego, with Android compatibility.

https://www.indiegogo.com/projects/jolla-tablet-world-s-firs...
> Immutable data structures are often the most helpful tool in accomplishing that.

This is said often but without much qualification. I've found mutable data structures with change propagation (via observable or what not) to work much better given that the whole diffing thing can be avoided altogether since you know exactly what has changed.

It is my understanding that the DOM is broken in how it handles invalidation/re-rendering (doing it for each modification rather than batching), but again, I don't see how immutability helps fix that problem any better than just doing it the right way with a mutable virtual DOM?
Cricket World Cup: Dilshan Toyed with Bangladesh – Graeme Swann
Some context, please?
This reminds me of a tool named pwnat by Samy, the myspace hacker.

It is a tool that allows any number of clients behind NATs to communicate with a server behind a separate NAT with no port forwarding no DMZ setup, and no 3rd party involvement. The server does not need to know anything about the clients trying to connect.
exicting
Awesome work guyz..!!
Creating scalable APIs
MS Word is pretty responsive as an editor. Adobe Reader isn't even an editor.
Steen Lifts Blues Over Jets in SO
Congratulations! Great Work!
Ask HN: What should I learn, ember or react?
Light is weird! Here’s an essay from a dilettante with too much time spent in Lightroom…

Everyone (including the Wired people in the submitted article here: https://news.ycombinator.com/item?id=9117137) seems to be trying to white-balance the image as if it has only a single light source. "He saw blue in the highlights, telling him that the white he was seeing was blue, and the gold was black. And when Harris reversed the process, balancing to the darkest pixel in the image, the dress popped blue and black. “It became clear that the appropriate point in the image to balance from is the black point,” Harris says."

I don't understand why. The blown out highlights of the background (which seems to be people carrying bags outside a window?) seem to make it clear that whatever's hitting the dress is a different light than what's filling in the background.

The hardest question I feel remains, then, is: if the dress is white, why is the foreground light blue-cast? Generally indoor lighting is yellow than outdoors... possibly a flash? The quality of the image is so poor that it appears that there was still not nearly enough light hitting the front of the dress, but on the other hand I don't spot anything on the front of the dress that I'd say was definitely a flash highlight... my best theory is that it's a 100% crop of a bigger image and the flash isn't sufficient because the photographer was actually quite a bit further away (and had a poor camera/cameraphone).

But that light temperature question is a problem the other way too: if it's a blue dress under warm indoor lighting (hence the yellow/gold-ish tinge to the 'black' parts), what's up with the particular shade of blue the light part of the dress is rendering as? That doesn’t look like blue in warm light to me. That's a really weird shade for blue to render as, I see that shade far more often when looking at white objects in cool light.

People also tracked down (don't have original source, just people reposting on Facebook) this site which sells a very-similar-if-not-exactly-the-same dress in both a blue and white variant (hard to be sure of the details with the poor quality of the original pic)! But neither secondary color (seems to be untinted black in both cases): http://www.romanoriginals.co.uk/invt/70931?colour=Ivory - and in none of the “corrected” blue images I’ve seen does it look like that shade of blue, without clearly crushed shadow detail indicating underexposure. But if that is exactly the same dress, than I honestly can’t say, since there are weird things about both color rendering options! (Why wouldn't the dark lace be blue-cast too? Alternately, why is the blue less gold-cast than the lace if the dress is really blue?)

EDIT: another option for how the exposure got so weird in a blue-dress scenario: there could be another item in the hypothetical uncropped original photo that is not overexposed that explains how both the dress and the background are overexposed? If just the dress was the original subject of this photo I'm surprised by how poorly the camera picked the exposure/white-balance.
Really interesting to watch, thanks for doing this.

Anyone else really impressed by their development speed? I've not used Go and following someone else in an editor can be difficult, but it took me some effort to keep up: you guys never slowed down for nearly two hours!

Did you ever find out why ip.appspot.com yielded "Bad Request"?
You're right, c# does to some extent. On balance I do agree with you, and prefer the set of c# features. Just to clarify - I was thinking of things like this

class Example
{
public static void Main()
{
Predicate<String> foo = Foo<String>(s => s.Contains("foo"));
}

static Predicate<T> Foo<T>(Predicate<T> p)
{
return p;
}
}

I can't replace Foo<String> with just Foo on the right hand side on the 3rd line. I could, however, replace the left hand side with just "var". (n.b. I am using mono, with langver=5. It's possible this is improved in a newer version)

Java will infer the RHS

class Example {
public static void main(String... args) {
Predicate<String> foo = foo(s -> s.contains("foo"));
}

static <T> Predicate<T> foo(Predicate<T> p) {
return p;
}
}

The structural typing of lambdas in c# I believe works with delegates? I at least don't know how I'd do the following in c# (I suspect I'd have to define an override of the implicit type conversion operator from a delegate type to a class, or define an extension method called hello on a suitable type)

public class Example {
interface MyPredicate<T> {
boolean test(T t);
default void hello() {
System.out.println("Hello");
}
}

public static void main(String... args) {
MyPredicate<String> foo = s -> s.contains("foo");
foo.hello();
}
}

The structural typing here is really powerful, e.g. for working around things like type erasure ;) http://benjiweber.co.uk/blog/2015/02/20/work-around-java-sam... or more consise builder pattern http://benjiweber.co.uk/blog/2014/11/02/builder-pattern-with...
Yeah. I had one server with over 900 days prior to Oct. It probably should have been rebooted for other reasons but thats the one that forced it.
The comment replied to was about missing its like in other languages. Didn't mean to imply that its name should be changed in C#.
"Text editor has moved away from 10,000x performance overhead to 1000x"
Your Search is about to get better
I created the blue image myself by guessing at the color of light that was hitting the image and subtracting it using GIMP (#524922 FWIW). It's not entirely scientific, but the resulting blues match very closely to the picture of the dress on Amazon [1], despite the image feeling a bit too dark.

[1] http://www.amazon.co.uk/Roman-Womens-Detail-Bodycon-Dress/dp...
Open-Source Library of CAD Designs for 3D-printed, Underactuated Robotic Hands
Someone posted a picture of a dress on Tumblr; some people perceive the dress as gold/white, while others saw it as blue/black.

http://www.reddit.com/r/askscience/comments/2xbfxp/what_colo...
Highly recommend watching Lee Byron talk about immutability. He covers your doubts very well. http://conf.reactjs.com/schedule.html#immutable-data-and-rea...
Watch this ordinary carrot turn into an edible net
GPS tracking my ski trip in Vail, Colorado
I'm not a fan of just learning a new framework, if you have no use for it. The vast time you spent on learning completely new framework is of course very good in overall but if you have no need for the framework it may feel pointless.

So my advice is to pick an interesting project which you can build using modern techniques like ember or react. That way you have greater motivation to learn and you get results for the work you have done.
Finding the Why
For this sort of thing, with a fixed amount of developer time:
- Performance
- Stability
- Actually working

you can pick 2. Also, if you pick performace, 50% of the time you can only pick 1.

Everything is a tradeoff but it's a lot easier to sell something slow than to sell something that doesn't work, and a lot of the performance costs are due to general techniques encoded in these frameworks that reduce bugs.

Another thing is that things do get faster. I think V8 has gotten 10x faster (at least) on real code since its inception. And that's despite JS not having changed.
I've always done my best work starting at maybe 10pm, but I also don't think it's about the lighting. There are some seemingly obvious benefits--the news cycle is much slower, few stores are open, most people are sleeping--so, fewer distractions overall.

But I don't think it's that. That's when I feel like working.

When I wake up at 8am, I feel like reading the internet all day.

I'm really not sure I can quantify or explain it any better.
> I think React has potential. It's at about the same stage of maturity that Angular was five years ago, and if it's as successful, we can expect it to enjoy five years of being the new darling in the Javascript world, until the Next Big Framework comes around.

React is something which stands astride on a line that divides a framework and library. I believe, like all good libraries out there, which do one thing and one thing well, React might stay for a longer period of time. At the first look of it, it might look heavy and bloated but it professes a far simpler view of building UIs.

The best part is, just like jQuery, it didn't take me more than a few hours to get comfortable with React and incorporate it into building something, something that could have taken a few weeks with other frameworks. I am not saying there won't be anything better than this but I am sure it isn't just another hyped fad.
I'm about like this, but wanted to add that I feel physically ill (nauseous) when I wake up too early.

It can actually be any time of day, I think it's more related to how many hours of sleep I've had.

Sunrise, though, is never a time when I feel good physically. I don't think it's just a pavlovian reaction, either.
The yellow one in your simulation is the one I feel is off, and was referring to with the blue removal. That's not how I perceive it when doing my mental white-balancing attempt (and I can't speak to how blue-dressers perceive it originally). I see that the pixels are light blue, but assume that the material is white. Lightroom does a much more convincing blue-cast removal -- looks pretty similar to this, where the gold is preserved but the white doesn't become yellow: https://pbs.twimg.com/media/B-0WdySWwAEqiDR.jpg (I would upload my version from lightroom, but I didn't bother to save it and I've spent far too much time on this subject for one night :) ).
I don't know. Based on my experience I firmly believe that between not-invented-here vs invented-here syndromes, many more projects fail because they try to do too much themselves. Especially in startups. For anything that is not the laser-focused core offering of your product, pick a good enough library and be done with it.

Invariably, most problems are such that you can get 70% of the implementation done (the fun part) with a reasonable amount of work, but the last 30% (all the little details that you didn't thought of) take +70% of the time. And you also need battle-test it. For example, React is interesting, because it is battle-tested by Facebook, not just because of the approach it took to the rendering.

Good candidates for underestimating the amount of work:

Anything with i18n and l10n (dates, money).

Anything with threads (futures and promises library).

Anything with small errors causing cumulatively bigger errors (scientific calculation and money).

Anything integrating with the real-world outside of your app (sending email)

Anything with charts.
Nop, sticking with Atom :) it's awesome because it lets us write plugins with web technologies. Even though they pull React off of the core, it's still possible to use React to write plugins :)
Even in the highest white gold setting I still see the dress as being blue and black - just with low saturation. I don't get it, but this helps, thanks.
The product is free to use with certain limits. If some of the limits are too restrictive for students, we should chat.
not sure how many people are aware of the eclipse of mars illusion: http://www.moillusions.com/eclipse-of-mars-illusion/. but basically digital screens have trouble and variances in displaying cyan. is the dress possibly cyan?
Thanks, that is very kind of you, I will!
How people can equate wake times with sloth rather than hours slept or hours worked is beyond me.

I'm definitely a lazy scoundrel, though. I like 9 hours of sleep and when I'm awake I write programs to do as much of my work as I can figure out how.
I understand perfectly well what you are talking about. I just think your ideas are foolish. Also, I have no difficulty in reading your posts despite the downvotes they have received, so I'm not sure why you feel you're being silenced. Clearly, this conversation isn't going anywhere, though.
Most of the people that don't believe that immutable, persistent data structures are effective tools to increase performance of reconciliation, only put one foot in (that's my personal experience). That kind of reservation often compels people to "just try immutability on a part of their tree". It doesn't work like that and you often should go all in before you begin seeing the benefits. It's a leap of faith, admittedly.

Almost every application (ever) is a list of lists of lists (and so on). Even text can be broken up into paragraphs/code-blocks etc which form the lists. If these structures form a tree, and that tree is somewhat well balanced, then small changes can be found in log(n) time by comparing reference identity without developer intervention (by either a mixin or Om-like system). log(n) ends up being extremely fast for n in the range of graphical nodes in most UI applications. For everything else, a windowing infrastructure can be used (usually baked into a very sophisticated <ListView> component - our ReactNative mobile applications use this approach (special <ListView> component that exploits immutability without developer intervention)).
Maybe I am too old to get this, but the idea of keeping bending the browser for native applications just doesn't make sense.
What color is the dress – demographic collection
I'll see if I can figure out a good color to subtract to get a better yellow one. IIRC, it was cribbed from one of the news articles on this that showed up tonight, but I'm not sure which one.

EDIT: I'm thinking that the right move might be adding #392c00 (rather than subtracting!).. And I've updated the final image with that instead of the one from before.
Yes, we provide full service from offer to close. Right now that's largely done manually by in-house real estate agents. We're currently building out software to handle more of the process online (starting with the negotiation) but we'll always have expert agents on deck to help or provide the type of advice first time buyers need. What we won't do is drive you around in a Mercedes to hold your hand at an open house.
We have multiple groups who work on the product, some of them working on multiple products, so it's hard to say exactly. My team works exclusively on this product writing the core experiment editor and associated technology and is about ~40 people.
Oh I know it's true. The Wall Street Journal started callingit 'Obamanet' as soon as Wheeler dropped his editorial a few days back. Joke's going to be on them, I suspect.
Strong demand for a crowdfunding campaign perhaps. However it's really a drop in the ocean if you compare their 18k funders to the estimated 259 million tablets that'll be sold in 2016.

Edit: I jumped a year ahead. A better comparison would be to the 233.4 million that are estimated for 2015.
I had initially thought the same about different screens but then I saw it change on my phone.

The first time I passed by my friend's post with the photo on my facebook feed, it was white and gold. I ignored it and scrolled on. A few minutes later while scrolling back up to the top, that same exact picture (same post) was blue and black.

I've seen it switch a couple times since on my phone (nexus 4). Although on my desktop it's always white and gold.
It's fascinating to see all the comments around it on Reddit and other sites. See http://www.explainxkcd.com/wiki/index.php?title=Main_Page for more links.

The largest group of people commenting seem to be able to see both 'versions' of the dress just by looking at it, looking away and seeing it again.

There are also very many who see only the gold version of the dress and have a lot of trouble seeing the blue version.

Finally, there are very few who can't seem to see the gold version at all.

(This is in no way scientific, there is very likely a very large bias present in the commenters.)
I’m so confused. Is it people looking at the dress in person that think it looks white?

Someone looking at this photo on a reasonably standard (or reasonably well characterized) LCD display which their eyes have adapted to is going to pretty much see all of the three versions falling between “pale blue” and “dark blue”. Given the yellow background, proper “white balance” would make the dress look even bluer (see example below). Either way, seems like the photo was taken with a pretty bad-quality cellphone camera. Maybe people have just learned to predict color in pictures from some specific cellphone cameras with awful sensors and processing? Or maybe someone spent 20 minutes staring at something bright blue, and then switched quickly to looking at the photo?

What am I missing here? Does anyone here think the image makes the dress look white?

(Also, there’s not much “science” in this wired post at all. Edit: in response to the below comment, the businessinsider post is also pretty shoddy “science”.)

Edit:

One of the nicest online sources about this topic is http://handprint.com/HP/WCL/color4.html#chromainduct ; the rest of that site is in general the best online source about human color vision. (There are better sources, but you’ll need to go to a university library to read them.)

I wouldn’t claim to be a professional color scientist, but I’m about as much an expert on this topic as you’ll ever find among amateurs. If someone wants a 3-hour lecture in person about the science of human color vision, I’d be happy to oblige (but you have to come to an SF coffeeshop for it; could also be a shorter or longer lecture, depending).

Here’s the original image vs. one I “white balanced” to make the obviously white & black dress in the background appear neutral. Does the foreground dress still look white + gold?

orig: http://i.imgur.com/g461GBr.jpg
; white balanced: http://i.imgur.com/jtjECtR.jpg
(and I actually cheated a bit toward leaving the blue less intense than I would typically make it if color correcting this image)

In any event, I still can’t explain why people are seeing this dress as white. I now think that it’s likely to be unfamiliarity looking at digital photographs and/or some weird adaptation effect, e.g. looking at a dim phone screen while outside in the shade on a sunny day. Or maybe perception is being colored by a general expectation of white dresses (people often substitute colors in this way when they look at e.g. fire hydrants, human skin, clouds, or grass, interpreting the color based on past experience despite weird lighting conditions).
What to expect from something wrapped on a browser playing native application.
Using computer vision to prove that dress is white and gold
> Immutable data unlocks powerful memoization techniques and prohibits accidental coupling via shared mutable state.

Memoization is still more expensive than just tracking changes and avoiding unnecessary recomputations directly (it only starts winning when doing dynamic programming). There is a point on accidental coupling but this is more of a correctness rather than performance issue.

In the high-performance computing field, use of immutable data structures is suicidal; even tries are a magnitude slower than in-place mutable data structures. And he only compares against naked shared mutable state, not against managed mutable state with change propagation.

And that gets to the end of the talk: the real reason is they want to avoid using frameworks that already solve this problem by tracking changes, and React somehow avoids that since you can do just the diff post facto. Ok, I get that.
There's also the (former) elephant in the room that was Bell Labs: the huge R&D lab was owned by Ma Bell, essentially a government endorsed monopoly.

I think it's safe to say Bell Labs represented a large portion of the whole of US's technical and scientific output in the 20th century (reminder: they invented the transistor, information theory, lasers, radio astronomy, UNIX, ... ; it's mindblowing).