skysight-inc/HackerNews huggingface dataset:
It's not all of a sudden. And I'm not talking about super blatant racism where every business owner is like "I don't like those black folks so I just won't hire them".

It's not all of a sudden because in the US, we had slavery and then Jim Crow. There was never a time where everyone lived equally, and then all of a sudden all the black people were unemployed. They've always been disproportionately poor, uneducated, unemployed, and that's a really tough cycle to get out of.

And it's not blatant racism. A black guy with a Harvard MBA doesn't have much of a problem getting a job in this town. But there's still plenty of subtle, unconscious racism. A black guy is more likely to be rejected for any given job than a white guy with a comparable resume. There's plenty of studies on this issue, here's the first one I found: http://papers.ssrn.com/sol3/papers.cfm?abstract_id=422902

The employer here doesn't hate black people, they just decided to hire the white candidate for a reason they probably wouldn't be able to put their finger on.

These black people don't have any business connections, so it's a lot harder to get internships and jobs. Half the adults they know when they're in college are unemployed or in jail. This is more of a poverty problem than a race problem, but race still plays into it. You can't get a job in your dad's office like your white friends did, because your parents were constantly passed over for jobs like that.

These black people have a much harder time starting their own business. Their family doesn't have any money, and they seem to have more trouble getting a loan than white people do.

I want to reiterate that this is not all of a sudden. There has never been a time in the US where all races lived in equality and harmony. If 90% of the unemployed are black, it's probably always been that way, right up until none of them were unemployed because they were all slaves.
Beacon Tracking with Node.js and Raspberry Pi
some things never change!
Signed. They drive me nuts other than in some specific cases. It can be ok, for example, for a picture blog where I am just browsing, have no defined goal, and don't care where I am in the available results. For everything else under the sun: no thanks.
Your heart rate – How and where on Apple Watch
Rutan Launches Kickstarter Campaign for RC Models of SpaceShipOne
Yes, I agree infinite scrolling is kind of inconvenient, but what do you guys think of one-page-websites in general? For example, a lot of company landing pages do this nowadays, and it looks something like this:

--------

some background pic

some call to action

---------

about section

----------

product section

----------

other people are saying section

---------

example usage section

---------

api docs section

---------

some social section

----------

footer

-----------

And as you scroll down the page, various transitions and animations (powered by jquery) popped out telling you more about the product / asking you to make an account.

I personally have made a good handful of websites like this, but I never really enjoyed the scrolling down craze because I use Emberjs and dumping everything into one application.hbs really isn't what Ember is about. But what's the consensus out there? Do people enjoy layouts like this?

edit: formatting
There are plenty of scripts to only display the ones which are visible. They get hidden as they are scrolled off screen.
Is there anything wrong with being "stuck in an ES3 world"?
Thanks, lots of great insights in here. Jives with my instincts, but important to hear it from someone else as well.
It's really easy to burn an additional 500+ calories with exercise, which is very significant. Of course it's not a substitute for a proper diet, but it can be a huge factor in weight loss.
Sex is actually more apt. People who find it easy to attain sex and let themselves indulge often outperform the average population by orders of magnitude. The drive for sex is operating at a fairly basic level, as is greed. Both are probably supported by evolutionary biology, which made both drives somewhat 'open ended,' driving people to want more than they actually need. Getting more sex has a synergistic effect, often enabling people to get even more sex, in a way analogous to money.
Why Craft Brewers Are Turning Beer into Wine
Accelerating carbon loss through hyperventilation will make your blood alkaline, possibly to dangerous levels. https://en.wikipedia.org/wiki/Respiratory_alkalosis
I'm working on a photo organizer for my family's photos which has about 115K entries. I want all of these to be visible in a single pane, so I implemented what I call "near-infinite scrolling". It could also be called "transparent pagination".

It avoids the issues of infinite scrolling really well. What you do is have a very tall div, say 8 million pixels. Inside of that you add a div that you move around as the page scrolls, let's call it the viewport. Whenever there is a scroll event, you check and see if the viewport is no longer visible on the screen and then repopulate its contents.

This is indistinguishable from a very long page as far as the user is concerned. You can grab the scrollbar and jump halfway down. You can hit the "END" key and jump all the way to the end of the results. If you scroll faster than content can be loaded, scrolling doesn't suddenly stop when you reach the end of the loaded content, then have the content appear and have to start scrolling again.

The back and forward buttons work as expected, at least in all the browsers I've tried. Refresh does too. This doesn't require any extra work on my part. The browser goes back to the page and sets the scroll position correctly, which fires an onscroll event. This is then treated like a normal user scroll, which will cause the viewport to be moved and the necessary information to be drawn.

In my case it's a grid of square images so the math is straightforward. I load three extra rows above and below what is visible in the viewport.

Unfortunately, I don't have a demo available in a public place. I've implemented this in jquery, then again in ember, then again in react (as ember was too slow). I'm working on getting it working with the ember glimmer branch. If you're interested in looking at my broken code, it's at https://github.com/jewel/hypercheese.

If you are using infinite scroll to replace pagination, please consider using this technique.

Edit: SlickGrid has something they call "virtual scrolling" that appears to be using a similar technique. Here is a spreadsheet with 500,000 rows: http://mleibman.github.io/SlickGrid/examples/example-optimiz...
I find some truths in this analogy:

I remember, when Py3 first came out, everything was incompatible -- unnecessary incompatibilities like the u" notation for Unicode string literals that was dropped. Unnecessary incompatibilities in the C-extension-module implementation layer. And so on. The list of incompatibilities was just huge.

Later several of them where dropped, like the string literal trouble ... But than the trouble was already done. Many extension modules where not lifted to the new version, since the overhead was to big.

I think, many more projects would have adopted Py3, if more extension modules would support it.

The huge library of extension modules was always the strength of Python. Now we have many projects still running on Py2, because Py3 did ignore this strength.

I think, when it would have cared more for compatibility from the beginning, much of the damage done would have been avoided.
>People don't realize what a trivial amount of calories working out burns.

I think it's more that people don't realize how stunningly high calorie counts for "bad" food can be. Like a cookie might take 20 minutes of exercise to burn off the calories, but that's more about the cookie than about the exercise.
Asian woman, especially in the US, would not be strongly against relationships with non-Asian men. Plus the societal norm is for the guy to initiate and pursue. So if you have a small subset of white men who have a fetish for Asian women, you'll naturally get more of those pairings simply because Asian men dont have as much of a fetish for other races as white men do.

If you do the math, you'll also see this. If Asian women had equal preference for white or asian men, you'd see a fairly equal distribution of Asian/White pairings (with that of Asian/Asian). If you take a look outside you'll see there are still vastly greater amount of Asian-Asian pairs than Asian-Nonasian. The Asian-men preference will be greatly less pronounced for Asian American women, but it's extremely strong for Asian born women.

If you don't agree with looking, or you lack a sufficiently large sample size of Asian friends to gather info from, see this quote from Wikipedia:

"Social enterprise research by the Columbia Business School (2005–2007) concluded that while East Asian women statistically prefer East Asian men for marriage, they show no discrimination against White men, causing Asian women/White men pairings to consistently become the prevalent form of interracial dating & marriage in the United States.[6]"
Yeah, perhaps as an additional block device you can mount with whatever permissions you want.
Hi, I'm one of the Babel contributors.

I can sympathize the initial fear of transpiling. However, it really is much better than you think. Source maps have made big strides in the past year and Babel has excellent support for them.

Besides source maps, Babel does a lot to keep the generated code as similar as possible to the input. There are very few features that require complex transpiling.

Another neat trick I've learned recently is that when you are debugging in a modern browser that does not require certain features to be transpiled, you can simply blacklist them in Babel and debug them natively. Then when you are deploying you can turn transpiling back on for everything and support every browser. (Note: be careful that you don't blacklist features with buggy implementations)

Transpiling is quite nice, and it's very likely that you already do it with something like Uglify or Closure compiler.

> npm may eventually support two versions of the same module, which would enable you to deliver libraries as both ES5 and ES6 for Node.js, io.js and client-side module systems that are based on npm.

This will actually be necessary in the node environment if we are ever to migrate to ES6+ features without causing breaking changes for module users.

ES6 isn't just some nicer syntax/features, it's the future of JavaScript and transpilers are the way we are going to get there.
Radioactive decay is still a nuclear reaction though...
A 45 minute full HIIT workout should burn about ~1000 calories; not exactly trivial.
Project Habakkuk WW2
Agreed - nicely done
It says a lot about her that she answered so gracefully about her ex though. That garners a great amount of respect from me. So many exes are just bitter and eager to stick the knife in. It's refreshing to hear someone say positive things about their ex.
> Stallman's focus on copyright law and intellectual property law

Channeling Stallman here, there's no such thing as "intellectual property law". There are a bunch of laws that work in very different ways, evolved under different circumstances, and have different purposes. Copyrights are for ensuring authors retain economic and/or moral rights on their work, patents are so that inventors will disclose their inventions instead of keeping them as trade secrets, and trademarks are so that consumers don't get duped into buying the wrong product. There are other sets of laws that have other purposes and histories, such as regional designation or shipwright designs.

Lumping them all together as "intellectual property" promotes oversimplication and confusion.
I mean if you never want to improve the language I guess not. The point was that ES5 adoption was really weak at best, and ES6 has been very strong.
That's an unnecessary politically charged remark, bordering on flamebait, IMO. Discussing communism is interesting, but this really isn't the place for it, and anyone who strongly disagrees with your remark has to either let it slide or enter into a completely tangential discussion.
I would think few are delusional enough to think that true free market capitalism exists in the US. I am certainly not one of those people. The use of "free market" in my case is just a term of trade to mean a "mostly free market with lots of caveats".

That said, no need to waste your time with a long reply. I really don't think it is worth anyone's while to engage in a typical HN battle of minutiae. You know: What is the meaning of "is" type discussions.

My only point is that businesses are not driven or managed by greed. That is very, very rare. As an entrepreneur yourself I would hope you can agree with this simple statement without looking for corner cases that could support a 300 comment thread.
Couldn't you temporarily disable JS to resolve this?

EDIT: not saying it's optimal, just that it ought to at least get you to where you could apply for a job.
I found this other comment from her a lot more interesting. And somewhat eye opening.
http://www.quora.com/How-can-I-be-as-great-as-Bill-Gates-Ste...

> They are unlikely to be reading stuff like this. (This is not to slam or criticize people who do; I love to read this stuff myself.) They are more likely to go straight to a book: perhaps a biography of Alexander the Great or Catherine the Great* or someone else they consider Great. Surfing the 'Net is a deadly timesuck, and given what they know their time is worth -- even back in the day when technically it was not worth that -- they can't afford it.

This paragraph kind of reverberate with me. I like checking HN. It's interesting and while most of the times you don't learn about X, at least you know what it's out there. And I tell myself I'm "working" keeping myself updated.
And then spread thin across different subjects. Because, hey! these days you have to know everything. Even more if you want to build a business and have to wear all the hats.

OTOH the words of Richard Hamming on "keeping an open door" come to mind.

Timebox and prioritize seems to be the best solution.
If that block is falling down then it's actually little heavier at the bottom, by E_k/c^2, where E_k is its kinetic energy.
Thanks, I see it, but it significantly reduces set of results. For example, there is no MySQL+Dart runs.
Wasn't (isn't?) there a meta-tag for this? I remember in Opera, I could press some shortcut that would go to the next page in forums etc.
To my knowledge, the most prominent analytics-based example of where infinite scroll was harmful comes from Etsy. My most read personal blog post [1] was a summary of a great Etsy talk given by then-engineer Dan McKinley on "Design for Continuous Experimentation" in which he mentioned how infinite scroll failed at Etsy:

http://mcfunley.com/design-for-continuous-experimentation

One of the examples he uses was how Etsy spent months engineering an infinite scroll feature in their product search -- without any debate over whether it would be successful (at that time, just about every big site, Tumblr, Facebook, Twitter, etc had implemented it)...When they finally finished, their A/B testing found that infinite scroll had a profound negative impact on user engagement. This talk was from a couple years ago, I rechecked Etsy and it still looks like they haven't gone back to infinite scroll.

McKinley said they didn't know exactly know or investigate why infinite scroll (he said that there didn't seem to be any technical problem) caused this negative effect, just that it was undeniably a negative effect, and it was a lesson in how you should not just jump into a big project without experimentation at every step. My theory is that when it comes to finding for what you are intentionally searching for (and this applies to Google and Amazon) and then acting upon it (i.e. a purchase), infinite scroll may seem more helpful but in reality, it may cause the user to get "lost"...The user might see something interesting in the first page of results, but rather than stopping to check out those results, the infinite scroll tempts them to keep going and going...and after having consumed several pages of results, the user forgets that there were good things at the top, and never returns to them.

edit: that said, when it comes to just browsing a stream, i.e. leisurely discovery for Facebook/Twitter/Tumblr...I think infinite scroll feels like the right feature.

[1] http://danwin.com/2013/01/infinite-scroll-fail-etsy/
That's... quite an unprofessional mistake to make.

If you have Arvo, the design looks sort-of-okay. I have more of a problem with the ad copy.

"Easily tag items to where they can be purchased" is non-standard English and doesn't do a great job of communicating what's going on.

I had to chew through it a couple of times to work out what it meant.
Also the idea that exercise has a huge affect on mass loss is also pretty wrong. If you've got a large amount of weight you need to lose, the only needle exercise is going to move is your willpower, downward. Making it difficult to stick to what works, which is eating less. Shedding mass is way more about building willpower and good habits than it is about playing metabolic tricks.

The picture changes when you're down to those last few pounds. To get those off, you have to keep up the reduced caloric intake, and you also have to exercise. If you slack off on the former, you'll gain weight back. If you don't exercise, you won't lose any fat.

Building habits and willpower is a journey that takes at least a year and involves changing your relationship with food. To a large extent, we see food as entertainment, it takes a long time before our subconscious minds' adjust to thinking about it as fuel. Inherent in this is replacing that hole left in our psyches where food entertainment used to be with something else as entertainment.

It was a whole year after I started dieting before I started looking at salads as a perfectly acceptable lunch, perfect for getting a feeling of fullness without blowing up the calorie meter. For a long time I played this game of trying to get the most value out of my calorie budget, still mind thinking of food as entertainment.

I did intermittent fasting, which was effective at helping me lose weight but not at keeping it off because it didn't solve the food-as-entertainment issue. Once I got down to a more reasonable weight I stopped, and before I knew it I was fat again, though not nearly as fat as before. I hadn't stopped thinking of food as something to cure boredom with.

I eat better than I ever have, and look more youthful at 31 than through most of my twenties. Ironically, I feel I also enjoy food a lot more than I used to. I taste it better, I find it more interesting. In a Buddhist non-attachment sort of way.
That's a very direct way to put it. That's the most direct application of "first principles" that applies to startups. However, most people who "talk startups" seem to do a hazy pattern match with other attempts that have already succeeded.

EDIT: Also, the overarching first principle of startups will be of less direct help when dealing with every-day minutiae. Often, these are your problems on the way to solving the customer's problem. However, applying the overarching principle to such schlepping may also help you find an even better problem to solve.
No mass is lost in this reaction. The mass of the atoms remains the same. The energy that is released is due to the difference in bond energies. To balance the equation you would need to add a Q to the other side, corresponding to the bond energies.
aka, middlebrow dismissal.
Japan looks to distributed/cooperative control to manage energy deregulation
If you're interested in this point, you should read Gary Taubes' book Why We Get Fat.

http://www.amazon.com/Why-We-Get-Fat-About/dp/0307474259

The third chapter is all about why exercise isn't a good way to lose weight. It is generally a fantastic book.
This seems like the way to do it. You basically have the browser load in pages of content, keep x pages above the viewport, y pages below ready to scroll on to, then you're holding x+y pages. You remove pages when scrolled far enough past and add pages to keep y-1 pages in hand. The problem then is that a user might scroll through a lot of content and then choose to scroll back - eg if they're sampling for quality first and then selecting on a subsequent pass.

How do pdf viewers handle this wrt memory conservation. If you have a 1000 page pdf, scroll through a couple of hundred pages (using a infinite scroll type view), what does the viewer do with viewed content, it has to cache it somehow, right?

Maybe the infinite scroll needs to be more accomodated by the browsers rather than just not used. I know in certain circumstances (image search, reddit on mobile) that I find it useful.
Yes, removing elements from the DOM will allow browsers to free the memory.

Some site (Tumblr I think) did something like this a while ago where it would do something like this, it was very fluid:

1. When a new section has been appended to the bottom of the page…

2. Calculate the current height if the topmost div and save it explicitly as the div's height…

3. Then remove all content from that div.

4. And when another new section has been loaded and appended do the same thing, but with the second topmost and so on.
Much of this is a function of potential and kinetic energy. High speed trains are going to have more kinetic energy, and therefore more potential for fatality.
right on, like the FUSE in question.. but securely mounting something remotely means storing a bootstrap key somewhere anyway. Turtles all the way down :)
Horrifying Prophetic Dream About America?
The Layman's Review of the Samsung Galaxy S6 (Edge)
Im going to have to call you out here. I think you are clearly trying to irk me. But I didn't suggest that white men dating Asian girls is a bad thing, or any racist anti interracial attitude. So I'm not sure what the point of your comment was. It's kind of offensive and latently racist to suggest that I must be Asian and I must be bitter because you took one of "my girls."

Why not just respond to the point I made attempting to explain the prevalence white mail Asian female pairings.

How am I supposed to make my point (assuming I'm right about this) when I've got people like you attacking me with off-topic slightly racist remarks?
> Unfortunately, the people who suggest that paper don't realize that it's a very technical treatise and not an appropriate introduction for the types of programmers who ask the question.

I think the main value of that paper for newbie programmers is not to learn all the nitty gritty details about floats (which would be futile), but instead get the idea that floats can, and will, behave unintuitively, and that they are not just decimal numbers like many beginner materials propose.
What problems of infinite scrolling does this solve? Sounds to me like you've just implemented it in an unusual way.
Hear hear. They're a terrible time sink, and I think this is deliberate.
That sounds like something Ulrich from Silicon Valley would say. Hilarious and true.
Spalding Gray’s Catastrophe
Maybe they need to pass `-Dhttp.address=...` to the start script[1]; Play binds to `0.0.0.0` and port 9000 by default.

Here's the corresponding error from the log in Play[2]. Not sure what else it could be...

[1] https://github.com/TechEmpower/FrameworkBenchmarks/blob/mast...

[2] https://github.com/playframework/playframework/blob/2.2.x/fr...
One possible downside of this technique would be searching in previous "pages" would be difficult / impossible. Since element is removed once its out of view port, browsers' search function can not find given text. Although it should be acceptable if you have only images.
Hey, just released the first stable version of postgres package for meteor.js