skysight-inc/HackerNews huggingface dataset:
I disagree with the notion of lack of padding that makes rugby safer. I think it's the structure of the game.

In football, once the receiver or running back has the ball, he is going to take a hit - likely from a defender who has been in full sprint for a good distance. Once he has the ball, he has 11 other players containing/funneling him and focused on crushing him.

In rugby, the ball carrier can pass or kick. That makes the game more one-on-one because the opposing team has to cover their guy. The width of the field needs to be considered. As a defender, you can't be reckless, you have to make sure you make the tackle. This means you go lower, you tackle the waist and slide down the legs of the runner.

I played at a decent level of rugby when I was younger... rugby players are not afraid of getting hurt. They do not ease up on a tackle because "i'm not wearing a helmet".
The United States is a wonderful, wonderful place. I've lived in several US states and have worked on temporary visa in foreign nations, so I have something to compare it to.

Yes, healthcare and homes/apartments can be expensive, but there are alternatives for healthcare[0], and you can get cheaper housing if you're outside of big cities.

The flip side is everything else is cheap. Groceries are cheap. Clothes are cheap. Restaurants are cheap. (For lunch today, I had a hearty lunch for $5. And I could go cheaper if I had to.) Home goods are cheap. Cars are cheap.

It's a great place to live. Most of the negative stuff you hear are us wrestling with our problems, when on the whole we're actually extremely fortunate and blessed[1].

[0]: https://www.mrmoneymustache.com/2017/11/05/when-your-shitty-...

[1]: http://www.nationalreview.com/article/455920/2018-great-time...
>the brain slams against the inside of the skull due to stopping fast

Yes, that's the inertia change I referenced.

A crumple zone is unlikely to mitigate the problem in any meaningful way. The problem is that in a hard collision, the head still stops in an instant, but the brain continues to travel at the same rate of speed until it slams into the skull. Effectively slowing the distance over which the head comes to a stop by a few millimeters or so won't meaningfully offset that impact. The brain is still traveling too fast.

The kind of design you're referencing works in vehicles because its purpose is to dissipate the energy of the collision around the zones instead of through the vehicle. But, the goal here is to avoid damaging the vehicle so extensively that the damage intrudes upon the cabin (and its occupant).

However, the vehicle's deceleration itself is not altered in any meaningful way by crumple zones. So, this system really only works if the driver is restrained (e.g. by a seat-belt). Otherwise, the driver would still bear the force of the sudden deceleration when she collided with whatever was on the other side of the empty space in front of her.

Similarly, if the brain could be restrained in its skull, then helmets might have at least some value in protecting it.
I'm not sure that it makes sense to pay proportionately more for a company with more cash. Whatever return Apple produces on its investments in making iPhones and such, cash tends to reduce that. So it seems logical that it would be valued more conservatively than a company that holds less cash.

I also think that it is reasonable to consider that the whole market might be overvalued, given that nobody can predict the future and we are at historic lows with regard to interest rates. So it isn't outrageous to consider a historical average P/E for reference, rather than the average P/E right now.
Is this a conflict of interest?
I'm not convinced it matters in this case, lying only prevents the other end from being extra-smart.

We'll stick with the VoIP example. Packets are going to be dropped independently of any information in the TCP headers. If there's too much load, some of them will disappear. If your client says "yeah I got that data" when it didn't actually get the data, it doesn't increase load any more -- if you're sending a real-time 256kbps audio stream, then you need to be able to send 256,000 bits every second regardless of whether or not the network is capable of that. By not retransmitting packets you don't care about, you're decreasing load.

Of course, if you push the information all the way up the stack to the application, you can do interesting things. You can notice that packets are being dropped and switch to a codec that sounds worse but sends fewer bits per second, and maybe you'll get a better quality call going on with fewer dropouts.

Now that I think about it, I'm surprised this isn't how we deal with degrading things over slow connections in general. I would much prefer to only get the "mobile friendly" version of a page if I'm actually on a mobile connection. Right now, the hueristic seems to be "if screen < desktop; send mobile page". That of course is silly because my home WiFi can happily pipe huge images into my phone faster than the web server can send them to me, while my 8 core laptop with a 4k screen tethered to my phone can't magically make 4G faster. Interesting interesting.
You have to distinguish between fatal crashes and all crashes. Here [1] are the data for the US if you can tolerate that site. What is the typical condition for a fatal crash? It's extremely counter intuitive. It is driving straight, on a major roadway, in good weather, during the day time, while sober, in a 4 door hardtop sedan. Seriously.

I'm reluctant to go social science and start handwaving too much causality there, but on the other hand I don't think it's entirely unreasonable to observe that those 'easy' driving conditions also tend to be some of the highest speed driving conditions. Creates a nasty combination of of a situation where we might be more subject to lapses of attention, due to comfort, and exponentially increased consequences when that lapse results in a crash.

But the really cool thing here is that these are also the conditions that right now the self driving systems are rocking. In other words there's actually a chance you're right that we're not comparing apples to apples, but instead are actually oversampling conditions where fatal accidents are more likely to happen!

[1] - https://www-fars.nhtsa.dot.gov/Main/index.aspx
Prevent starvation in this country now, or prevent uncontrollable infectious global pandemics in the future.
Awesome. Lazy Loading for EF is probably the most requested feature there.

I'm wondering how Kestrel is doing, and if it will finally be available as a freestanding web server, not behind a reverse proxy. Looks like HTTP/2 support is delayed until at least 2.2.
Because the non-technical person has time to dedicate to learning about business' needs while the technical person is busy doing technical stuff for most of their day.
The same stuff we do. They consume what we eat. And each other, and the byproducts of each other. We (the human) consume these latter to greater and lesser degrees as well.
That's why California needs a wall!
As someone who has dabbled in OS development over the years, you'd be a fool to use anything other than C (I suppose you could use a restricted subset of C++ if you really don't want to write anything but a toy OS) or assembly if you have something to prove.
This is exactly true. Technically there are rules against it, but this happens on essentially every play.
if I called my doctor today I would be very surprised if I could get an appointment earlier than April
A few thoughts.

1. It's not been clearly established that gluten sensitivity doesn't exist. Even if current medicine hasn't established it, it's actually quite common for established medicine to be slower than alternatives (e.g. probiotic, medical marijuana, babies needing touch and breast milk).

2. For gluten sensitivity, it's not clear if you're denying people have physical symptoms (bloating, gas) at all, or whether they are misattributing them to gluten. Either way, I don't see a connection.

3. Your comment really has the affect of associating two very different, very emotionally charged things that I think is lazy and exhausting to debug.
A lot of people I think use them to self-treat Lyme's Disease. It's hard to diagnose (and extremely expensive to do so) and many people give up and go their own way.
Well lots of little modifications being done quickly is what we use macros in vi/emacs for. However, I guess this can be solved by the frontend batching.
In ReasonML, most of your code is just Reason (which is just OCaml), but you can easily provide type declarations and use Javascript code in a typesafe way, or you can just drop to raw JS at any point in a Reason file.
Hippie libtards freak out over antibiotics in their chicken but beg to be injected with just as strong antibiotics at first sneeze of the flu?

...Just saying

People are for the most part completely retarded.
It's definitely a problem that pricing is opaque and disconnected, but have you considered that maybe healthcare isn't a good candidate for a market solution? Even without this problem, customers have relatively little ability to choose providers or price shop, and they often don't really understand what they're being asked to buy.

By extension, it seems like the key difference between "elective" and "non-elective" care is that one of them is elective... it's going to be a very different market when a consumer can choose to buy something or not buy it at all, vs. when they have to buy something and may not even understand what or why they're buying it. It's not necessarily that consumers are shopping prices more or being stronger negotiators, it's partially just that demand naturally falls if prices start to rise too much.
You mean more manual labour filtering presumably filtered water again?

These filters are rarely electric and typically hand operated and partly chemical. (Electric filters tend to fail when you really need them.) Or just heat and apply UV light to water.
AI Weekly 2 Feb 2018
Excessive locality of solution is an engineering bad practice.

Think of the crash like a train... if the locomotive can't get traction to go fast, the passenger cars can't fly thru the air at 100 MPH in a derailment, can they? So eliminate shoe cleats. Maybe eliminate shoes and play barefoot on grass. If your feet literally can't accelerate you to 15 mph in one meters length, then you can't hit someone's head at 15 mph when you eventually get there.

There are other interesting rule peculiarities that have nothing to do with equipment. There seems no reason other than sheer display of aerobic conditioning to require wide receivers to line up on one side of a line an dash 50 yards downfield to get smashed into and killed by another guy dashing 50 yards as fast as he can trying to stop him. So change the rules so they don't run as fast as they can? Just let pass receivers stand around downfield, or let defensive backs line up there if they want. If you have to run 25 yards in three seconds to hit a guy catching a ball, someone is going to get killed. If you're lined up a foot away from the catcher, you don't need to kill him to get there in time. Sometimes the best improvement to equipment is to make it not used, in this manner.

Another strange rule change is you have to try to kill the wide receiver because running yards made after a catch count, although trying to kill the receiver before the pass is pass interference with a free down, so an interesting compromise is no running yards after a pass along with any tackling of a receiver an automatic pass interference 1st down or half the distance to the goal. Where the receiver's feet are located when the pass is complete is where the play ends, not where the receiver was tackled after an attempt at a run. This would tend to make the game immensely more exciting because there will be even more aerobic running downfield and more exciting interceptions, vs a tendency to tempt the defensive line into an illegal tackle via short passes.

Another strange rule is offensive and defensive lines symbolically fighting and pushing each other is acceptable, leading to a lot of physical damage. A rule as simple as you touch an opposing player you're both out of the play would be interesting to see. You don't have to hit a guy hard enough to kill him to get him out of the play, just merely touch him. Its easy to kill someone by trying to charge into them so hard you literally flip them over, but hard to kill someone by high-five-ing them as you pass by. I imagine you'd see some amazing dodgeball like madness as players try to remain untouched as late as possible in the play.
When the state concentrates political and economic power in itself, it's theft.

When, say, the Koch brothers concentrate political and economic power in themselves, it's just markets and capitalism.
Still no production-ready ODBC in .NET Core? How is one supposed to work with database engines in a standard way? Java is miles ahead by just sticking to JDBC.

Microsoft first moved off ODBC towards OLE DB only to ditch it some years later.

Working with data and being able to connect to a plethora of data sources is essential to a platform success. .NET Core won't be treated as a serious cross-platform toolkit if it won't offer a reliable, interoperable interface.
For some context, this article in the New York Times presents essentially the same theories/discussion: https://nytimes.com/2017/12/21/technology/eric-schmidt-googl...
> You balance that from some other budgets, or raise more tax.

Fun. So if costs are rising, just keep paying more and more, that will solve it!

Providing cost effective healthcare is the best way to treat more people. If you make it more expensive, people will get less service. This is basic microeconomics. As simple as that.
San Francisco, Ca. Front-End Engineer- Full Time- Onsite

Apply: https://commonsense.recruiterbox.com/jobs/fk0fcxj

We are currently seeking an experienced front-end engineer to join a team of developers, QA engineers, product managers, and UX designers who work closely with UI designers led by a creative director. This role will help build and maintain all things client-facing and will help translate our organization and customer needs into functionally seamless, and appealing, interactive applications. Creating a great user experience is the focal point of this role, and the ideal candidate is curious about new digital technologies and stays abreast of coding best practices. This role will collaborate with a top-notch team of developers on a feature-rich, responsive site and help build personalized and social site experiences to help connect members with each other and the rest of the world.
LOCATION: San Francisco, CA TYPE: Full-time (40 hours per week) CLASSIFICATION: Exempt

WHAT YOU'LL DO: You'll be issued a Mac laptop for local development, use GitHub for version control, and work in a LAMP stack on our dev/staging/prod servers hosted at Acquia. We code to Drupal standards and strive toward industry best practices. Our engineers take pride and ownership in our projects, working closely with product and the other stakeholders to build something that is rock-solid and easily maintained. You'll have the opportunity to help shape the product you're working on and have your voice heard.

Sites You will be working on a multitude of high-traffic websites that garner millions of users/month, including: Common Sense Media (www.commonsensemedia.org): The platform that hosts reviews, advice, and more for parents. Common Sense Education (www.commonsense.org/education): Designed to help pre-K–12 educators discover, use, and share the best apps, games, websites, and digital curricula for their students. Also contains curriculum, professional development, and teaching resources for educators and school administrators.

WHAT WE NEED TO SEE ON YOUR RÉSUMÉ: Bachelor's degree and a minimum of 3 years of relevant experience Demonstrated proficiency writing standards-compliant HTML5 and CSS3 Proficiency with JavaScript in a cross-browser, cross-device environment (both jQuery and Vanilla JS) Understanding of current front-end and mobile development best practices, including responsive design, touch interfaces, performance optimization, and progressive enhancement Experience working with source-control with Git Experience working in a LAMP stack with PHP skills
>A poor person today lives better than a king of old.

That is an illusion to help people with their conscience. It does sound nice, but ...

The poor maybe eat better and maybe have better shelter, and certainly access to cleaner water, but they have significantly less control over their destiny. Also, kings didn't have to work and they were (usually) extremely wealthy, had servants, and could do whatever they wanted to. Kings had people to help them raise their children. Kings also didn't die from an easily treatable but ultimately unaffordable medical condition. Kings usually didn't get evicted for not paying rent on time. Kings didn't get arrested for trivial things and have to spend time in jail because they couldn't afford a lawyer. I could go on and on.
>You could say "just keep posting until it gets traction", but anyone who's built and posted something on HN knows this is really stressful and easier said than done, because most people--no matter how much they believe in their own project--don't want to spam the site they like.

Wait, you won't get in trouble for sending duplicates? I was always under the impressions that mods were pretty strict about one-and-done. Goes to show me I guess.

Edit: Huh. Went back and read the rules, there seems to be nothing against it... It seems like what I thought was "one-and-done" was more "as a guideline, to be well-received, don't submit the same thing often"
Hey, do you have a werk-student or internship opportunity? And, further, possibilities for remote?
That’s basically the concept of OKCupid. Unless they’ve changed it in the last ten years or so.
Huh. This is an interesting concept. The homepage talks about CS concepts being "separated from the distractions and technical details of having to use computers", and that is definitely a key factor for us. Thank you!
If NAT blocked UDP, the DNS client on home computers would never work.
That's because the point seems ideological, without any backing in reason.

Why is a government buying a majority of a company's shares on the public markets bad? Why is one man, or an investment firm buying a majority of shares of a company any better?

An attack on this is an attack on the concept of public markets.

'Public markets' does a lot of work in this claim. There's an obvious difference between shotgun nationalization, and a hostile stock takeover. It's the difference between armed robbery of a grocery store, and buying a loaf of bread at posted prices.

This seems to be a common reaction when market proponents see their own system used against them. (See also: collective baragining on the side of employees vs collective bargaining on the side of management. For some reason, one is bad, but the other one is just the way things are. Management bargains collectively, but we have to bargain against them independently.)
This could be handy for vr?
Hopefully you'd have 0 crashes and not need them as much.

But yeah, 30 mins to get the car packed, and then 30 mins to clean it afterwards
Thanks! We've updated the link from https://www.youtube.com/watch?v=FhX6cANaJ6o.
The NatGeo submission was a good read too:

https://news.ycombinator.com/item?id=16286230

Direct link:

https://news.nationalgeographic.com/2018/02/maya-laser-lidar...
Unfortunately I can personally attest that this happens to military personnel after they leave the military.
The New York Times is happy to make that "heck of a leap" as well, albeit with slightly more cautious wording: https://nytimes.com/2017/12/21/technology/eric-schmidt-googl...
Okay, where does that tell me how updates wil continue until you have a plan? Will they just continue being maintained by CoreOS? Will they stop? What is happening now? If we'll have to manually migrate, how much time will we get before we have to? How much time will we get between you announcing a plan, and it being put into action? When can we expect a plan?

We've got no info, and are supposed to run production systems with that.

This is a corporate acquisition, these things don't happen randomly. Why was there no plan made ahead of time? I'm disappointed and confused.
I wouldn't consider Ethereum to be "a little altcoin". While there may be a correction in the market, I don't think it will be "bitcoin vs. everything else"; at this point it would probably be all cryptocurrencies, or something more specific (individual coins, or classes, but probably not "scrypt-based coins as a class")
A few hints from the article: 810 sq miles mapped, a three year project and lidar flying by helicopter. Another giveaway is the search for MH370. In some dimensions Earth is still huge!
Its still very high per patient, higher than developed countries. And medicare will not necessarily get more efficient as it grows, in fact, the opposite.

Should we remember what the healthcare.gov for obamacare turned out? Billions into a non functional website.

Its true medicare shows some good signs in comparison to private, but it shows some other terrible ones. Lets not forget that healthcare regulation is designed by the same people that run medicare, in a broad sense.
> At least in US you get the medical treatment first and then they hand you a large bill to pay. In poor countries the hospitals will turn you away until you pay a significant sum in advance (not exaggerating it has happened to me).

To complete the picture, in the truly civilized countries when you're sick you just go to the hospital, and they take care of you, no strings attached.

The whole world is not made just of the USA and some banana republics.
"It always feels like the only way to make progress is by making a number of informal suppositions and waiting for a contradiction to reveal itself."

Sounds a bit like the scientific method =)
Make hypotheses and try to falsify them
Sounds fucking lit!
1 in 20 is not low odds at all. Ask any D&D player.
https://github.com/asib/spaceinvaders
/ https://news.ycombinator.com/item?id=10078928