skysight-inc/HackerNews huggingface dataset:
Thanks for the dismissal. "Heart tugging", isn't what I was going for, sport.

Your lack of desire to take seriously your responsibilities to those you share the sidewalk with is a problem for me. You want to be on the sidewalk so you'll be safe, while at the same time, refusing to acknowledge any risk you're imposing on others. That doesn't fly with me. Slow it down, sporty.
The court that this came out of has zero ability to set precedent (I mean other than that they decided a case that may go on to set precedent later).

Federal district courts are like state trial courts. These judges can pretty much do all sorts of things and we don't really care because they'll get fixed hopefully by the appeals courts.

The appeals courts are the first line of actual precedent but only for those courts that are below them (federal appeals - only binding on lower courts in the same circuit, state appeals - only binding on the lower courts of that state).

Appeals courts are not binding upon other appeals courts and usually the US Supreme Court doesn't like to get involved unless it's so clearly unconstitutional or if there is a circuit split where some have gone one way and some have gone completely another (because the federal system is supposed to be much more uniform than than the individual states).
After quickly clicking through the api documentation I don't understand why I would use this over a hosted NoSql database like mongohq. I still like having additional options though.
resu_nimda:
Many roads, especially in older cities like Chicago, were not in any way built as 'car roads,' as they were built before the widespread adoption of the car. Many were poorly retrofitted in an attempt to move automobiles in quantity, but this has generally been to the great detriment of the neighborhoods they pass through.
Damn, I was hoping Balmer was out. No such luck.
Unfortunately, the site does not behave gracefully under heavy traffic. Berkeley resident here, tried to order one of each, but the "place order" page just times out and I am not sure if my order was actually placed, or if I should try again.
And barely over a year later, Valentina Tereshkova kicks NASA in the teeth. Wonder how Mr. Lloyd felt when that happened.

> Original Mercury astronaut Deke Slayton wrote in 1970 to future NASA astronaut Marsha Ivins, ‘The exact time when we would seriously consider women is indefinite, but I am sure it is inevitable.’”

NASA was most definitely a boys club back in the day. I mean, you can see the old footage of the guys dealing with the Apollo 13 mess ( http://www.youtube.com/watch?v=kxOKVHhFVJU whoever chose the music for that should have been fired ) you can see just how much testosterone was in the air... along with the cigarette smoke.

It's a strange dichotomy that the "Free world" was less free to women at the time than a Communist country.
That's a fair point for why your argument is germane to HN, but for what it's worth I still don't agree with the argument.
I thought it was people fleeing the inner city for the suburbs that caused sprawl.

It sucks, but so do the cramped cities like SF and Manhattan. You can never get a moment's peace and contemplation, and they're even more crassly commercial than your average strip mall.
Yeah, it's extremely hard to set up a circumstance where the person in behind is not at fault.

If you get hit and get propelled into the car in front of you, it's your fault you hit the car in front of you (although this may vary by state).

If the manual transmission car in front of you shifts into neutral on a hill and slides back into you, it's your fault.

The person behind is usually in control of the space between cars and they are held to be responsible for it. You can possibly make it not their fault if you shift directly into someone's lane at speed right in front of them and then hit the brakes.
Very thoughtful comment, and not too obvious; thanks.
That's my point though, the US travel system didn't just become structured this way arbitrarily, it was a conscious decision to design our infrastructure in a way that was hostile to anything other than cars (pedestrians, bicycles, even horse-powered transportation). Cars were the way to the future, or so they thought.

Now, we have a hundred years of data and experience with the automobile, and it's become obvious that the fossil fuel powered car isn't a good long-term solution to the urban and suburban transportation problem. Literally everything about them is bad for the world, gathering and burning the fuel, the destruction required for their roads, the massive amount of space needed to store them, and the death and destruction they cause daily. Electric (and other alternative fuel) cars are less bad, but only in one small way, they address a single issue in an inherently flawed model.

You say that Europe has an advantage because it's cities are much older, but it's important to understand that the Netherlands and Denmark were both on the same auto-centric trajectory that the US was on coming out of the World Wars and industrialization. Denmark only started rebuilding their cycling infrastructure after decades of disuse when the energy crisis in the 70s made using a car extremely expensive. In both countries, people realized just how bad cars were. The deaths of cyclists (especially children) sparked mass protests where people demanded cycling infrastructure, and they got it. They were able to convert a car-focused city (perhaps less so than Los Angeles or New York, but still) into a bike focused city. They were able to do it, why can't we?
U.S. VC Investment Doubled In Q2; Bay Area Companies More Than NYC+LA+Boston
Per-pass performance gets worse. Overall performance gets better, because fewer passes need to be made.
Recapitulating a comment from downthread, but, look at DNS for an example of how the IETF botches compression in its "simple" protocols. Not that compression isn't fraught (look at TLS), but I see its use as a sign of maturity.
I meant volunteer to mean "not get paid".
In this case, they were probably using AD just because of Exchange, so if you want to ditch Exchange for Gmail, it's an odd choice to use AD as your identity provider, esp if you're a company known for wanting as little on-premise IT as possible.
I got a flurry of automated calls and emails once my order went through, I would expect if you have yet to receive a call then your order didn't go through.
I'm not convinced for average embedded device parsing HTTP headers represents significant amount of energy spent. Are there any data that suggest that for average device - I don't mean Google's specialized routers or any other hardware specifically designed to parse HTTP - this change would produce measurable improvement? In other words, how much longer the battery on my iPad would last? I don't think I'd gain even a single second, but I'd be very interested to see data that suggest otherwise.
> In the political environment in which Americans live, which seems to resemble the old Soviet system in some ways,

Can you tell us more about this?
The entire file may be resent, but practically it works just fine for me. The total volume is only 250mb and it is updated infrequently.
It is illegal. Cops, in almost all cases, don't care.
No, you're very lucky to live in the Netherlands.
At least it was not a resume black hole. It even came with a real signature...
There are places not accessible by roads with bike-accessible speed limits. Those are much more common than places not accessible except by interstate. (Incidentally, biking on the shoulder of the interstate is permissible in my state, with the occasional exception of some cities and bridges without shoulders.)
There is a wikipedia page with lots of content. Some useful characteristics are:

- free entry and exit: people can enter as suppliers or exit. Many markets are like this. Some aren't such as hospitals in most states in the US where you have to get a certificate of need, and it will only be granted if yours won't affect existing ones.

- mostly homogenous fungible products: you can do this for shoes, eggs and solar panels since they are substantially the same. This is significantly less true for nuclear submarines for the military because they are custom designs, and limited to builders with appropriate blessing and security clearances

- available information: the demand side can get information about the supplies on offer. You can do this for shoes and pretty much most things that have lots of reviews on Amazon. You can't for US healthcare since even pricing info isn't available in advance, nor is exactly what you are going to get.
Unix is dead?

Aren't Mac OS X, iOS, and Android basically unix OSes?

I'd say Unix won.
There are already two letters which serve this purpose. Eð /ɛð/ (capital Ð, small ð;) and Þorn (capital Þ, small þ;) What's the point of yet another letter?
I am sorry to hear of his death. He sounds like someone I would have liked to know.
Fair enough. 30k/sec sounds pretty nice. Sadly, I imagine that's a local instance. We need a solution that can handle orders of magnitude more than that though. Which, from my understanding, means multiple instances. And I have no experience with scaling Redis. I'd kill for a good turn-key solution.

Edit: Someone contact me. I want to give you money!
فوازير مسلسليكو الحلقة الاولي
فوازير مسلسليكو الحلقة الاولي
فوازير مسلسليكو الحلقة الاولي
فوازير مسلسليكو الحلقة الاولي
http://www.yallamoviez.com/2013/07/InitialFawazeerMslcelikoEpisode.html
Update: Upon testing, it's more subtle than that.

Mysql will still use the column for a covering index and run the query in a single-pass, but it will still generate a temporary table for the results (and do a really slow sort unless you do 'order by null'). It doesn't look like mysql has any way of doing date grouping without temporaries even in the trivial cases. I guess eliminating the sort was enough for my queries.

Using date()-like functions, date_format(), and left() all have identical query plans and roughly comparable performance.
Well they acknowledge NSA now so it seems that there must have been a point in the past when they acknowledged it for the first time. Furthermore as another commenter points out NRO was not acknowledged until 1991 even though NRO was mentioned in public documents in the 1970s.
I think promises are easy to understand.

Lets start with the most basic element of a promise: the `then` method. It is so basic in fact, that the spec only covers on how this method should behave and nothing else. All the other functions that you see in the libraries (Q, whenjs, etc) just have a lot of combinator functions that's built on top of the `then` method. Take the `Q.all` for example, it functions the same `then` except it wait for all promises passed into to it to finish before continuing with its own `then`. So understanding how the `then` behaves is essential to understanding promises.

IMO, the advantage of using promise is how composable it is. To achieve desired effect, you can take a few existing promise combinators, compose them together with just object/array literals and function calls.

For example, the other day I needed a html form to submit with a load mask covering the form while waiting for the submission to complete. The problem is that this submission can take anywhere from 21ms to 1500ms to complete. In order to achieve good UX, I needed the load mask to be not just a flash in the extremely fast case, but also not taking more than necessary time to complete in the extremely slow case. So I did this...

Q.all([ asyncFormSubmitReturnPromise(), Q.delay(500) ]).then(function() {
// hide mask & other cleanup
})

For comparison, to achieve the same effect using asyncjs...

async.parallel([
function(callback){
asyncFormSubmit({
success: callback
})
},
function(callback){
setTimeout(callback, 500)
}
],
function(err, results){
// hide mask and cleanup
})

I want to mention another advantage with promises: it creates an uniformed interface that disregards whether the loading is synchronous or asynchronous. Say for example you're writing a select box widget that needs to populate the dropdown's content. Your widget can expose a method just called `load` and it takes a promise. Now whoever is calling your `load` method will have the total freedom to pass in a promise's already resolved or pending to be resolved. If you have the data at hand, it's just as easy to wrap it in a promise `Q.resolve(data)` and pass it in.
Brazil will not offer asylum to Snowden
AFAIK all Latin1 characters codepoints with Unicode too.
If they did want to serve this audience, they would actually want to make it easy for someone (possibly the employees themselves) to build a Free encryption layer on top of them.
The guns and knives are the most popular images on the account, but are vastly outnumbered by pictures of bottled water and soda.
Bike lanes apparently don't help as much as you'd think. There is a psychological aspect to providing a bike lane that makes car drivers think that bikers are already protected by the lane, meaning, in the end, that they don't actually give bikers as much room.

Edit: Bike lanes increase safety but I just added it to point out that it's a relatively complicated situation. I think lower speeds were the biggest factor towards increasing safety. I can't find the study either so the above really isn't worth all that much, my memory being what it is.
I think in many regulated industries Coq itself would also need to be certified.

What industry is this?
Off-line access.
I think the implication was that we should make public transportation better along with decreasing the amounts of cars.
The biggest problem right now with online file storage services (sorry, I meant "The Cloud") is that while they all do basically the same stuff, there's no standard protocol for accessing them. It's a bit like if every website used a custom protocol instead of HTTP, and web browser vendors had to explicitly collaborate with each web site (or use the website's SDK) in order to be able to retrieve content.

Imagine this: All the major players in the space (Dropbox, Box, Google Drive, Skydrive, Sugarsync etc.) as well as app developers got together and came up with a standard way of doing this that makes it possible to use a single protocol & API for all online storage providers. I see this being a good thing for everyone - users can choose whatever service they want, app developers can easily provide their customers with a ton of options, and storage providers don't have to explicitly produce their own SDK or court developers to do integration with their service. We did have WebDAV, but that doesn't seem to be widely adopted by any of the major players.

I've been facing this problem myself with my own app; it's a lot of work to support all the major services and this is really just plumbing stuff that everyone would rather be taken care of so they can focus on the more important stuff. I had a meeting with Box recently where I proposed the idea of an open source framework for iOS which would provide a common native API that abstracts over all the different REST APIs used by different storage providers. The people I spoke to seemed quite open to the idea and agreed that it would be useful. I don't think a library like this would necessary be considered a bad thing by any of the major players, as it evens out the playing field and makes it easy to support different services.

If you're interested in taking part and/or using such an API in your iOS app, I'd love to hear your thoughts on the matter. I have some code already (which I haven't released yet) and am looking to clean up the API a bit, but I think it would be useful to a lot of developers.
I think the point remains though. The average consumer doesn't know the difference between a "major" airline and a "regional" one and shouldn't need to. Their safety record is just as applicable. Its not as if a consumer will see a regional affiliate and change their reservation because of it; its effectively the same experience.
I thought about this problem, but it was more to do with soliciting anonymous feedback from a group of close nit friends. It's a hard problem to fix, but I think maybe running the text through something that reduces it to all lower case and all txtspk, with some sort of grammer-fucker-upper might remove some of the personality attached to the original text input.
Does the email replacement sound like a support ticket system to anyone else?
These numbers are a little off. Most commuters are going to scoot along in the 8-12 mph range. People riding for exercise or training for a sport are going to get up near 20 mph. Amateur bike races will hold sustained speeds of 24-30 mph for a few hours (depending on the terrain). In the TdF this year the fastest team in the time trial averaged 35 mph for 25 min. TdF sprinters can hit 50 mph and 70 mph on mountain descents.
Wall Street Rip-Off: Thompson-Reuters sells data two seconds early for a fee
Iraq War vet starts to build an online identity network, ID.me
Boy, wouldn't it be crazy if applications included debugging modes that told you exactly what they were doing?
> Note that none of these confiscated weapons by themselves necessarily constitute an intent to use them.

Exactly. If these were instances of the TSA actually protecting us then "passengers who try to go through security with a firearm usually get a citation and can face a fine" would not be the case.

Not unless our plan is fining and citing terrorists out of existence.
Rangzen: Delay-Tolerant Decentralized Microblogging Smartphone Network
The general availability of bike friendly travel options in the United States is one that it woefully underserved.

In the past couple of years I have heard of so many bike/vehicle accidents that I no longer ride anywhere that can be reached by a motor vehicle.

I used to ride on the road but the best option for me was a bike lane that offered about a meter of space between myself and vehicles in a 55 mph zone. In many places I had to risk just riding on the edge of the roadway and hoping for the best and I had my share of getting brushed by side-view mirrors. No more. It is simply too unsafe to risk riding anywhere that I am not physically separated from traffic.
This isn't about what should/shouldn't be, I'm talking about how the legal system views these things. Vehicular homicide has a requirement of negligence, because traditionally the justice system sees a qualitative difference between a grandpa who backs over a grandchild who runs behind the SUV and someone who chooses to drive despite being blind drunk.

In terms of the hit-and-run == negligence...the two things correlate...a drunk driver may be so drunk that they don't realize they've killed someone. Or more maliciously, they do realize it but don't want to take a breathalyzer at the scene of the crime. However, there are cases (which does not seem to apply to the case in question) in which otherwise well-behaved drivers have killed someone unknowingly or for some reason panicked and left. It's still a crime, but it's not "homicide"
Javascript has some really, really bad parts. It also has some very good parts. PHP has the former, but not really the latter. The most common argument made for it is that it's drop-in-and-go, so you don't have to worry about things like application servers or deployment strategies. I would argue that that's the worst thing about PHP. Languages (and frameworks, etc) are well characterized by what they make easy. PHP makes it really easy to do things really wrong.
The headline is a bit odd. The TSA blog gives clear and simple instructions on how to take your weapons onto a plane. (Not loaded, not in your hand luggage.)

Some people have said (on HN as well as other places) that the TSA have never stopped weapons getting on board a plane and if they had they would have heavily publicised it. In fact, they stop about 20 to 30 guns each week from getting on board a plane. Those guns and knives are posted to their blog.

Perhaps posting images on Instagram will let more people know that the TSA manage to stop some weapons (although I don't care about the guns they stop, I care about the gun they don't stop and which is then used to harm someone) and to help remind people to put guns into checked baggage instead?

(http://blog.tsa.gov/search/label/Week%20In%20Review)

Note that I'm not defending particularly defending TSA here.
The huge leap that has to be made for Federal Government CIOs is the psychological attachment they have made between software that works and huge price tags.

Sometime, long before I ever came along, CIOs in the Federal sector became convinced that the only way for software to work was for it to be big, sold by SAP/Microsoft/Oracle, and have a huge pricetag. Anything else is a huge risk in their world.

They just don't believe that something that takes so little money, man-hours, and time to implement can possibly satisfy their requirements and replace such a huge portfolio of bloated legacy systems.

I built a metadata management system in a few weeks as a "rapid prototype" for a branch of the US military. It satisfied all of their requirements, was fast, secure, and stable. It was storing all of the production data and was made to be production ready by simply flipping a switch. Then the CIO saw it.

"Wow, this is amazing. Can you give the code to Team X so they can build it in Sharepoint?" 8 months later, a stunted, awful version of my prototype was demoed. The thick-client interface was gone, replaced by the awful, non-responsive Sharepoint bullshit. The Postgres back end that cost nothing was replaced with an expensively licensed SQL Server DB. The Google-like "search as you type" capability that was in my "prototype" was gone. Infinite scrolling in the grids was gone. Did I mention that they force their users to use Internet Explorer 8 because of "security reasons"? Never in my life have I witnessed such a huge level of IT incompetences as that on display in the United States military. This is almost surely due to endless bloated budgets which allow wankers like this to continue to keep their jobs.
You say that like you think a custom binary protocol would be harder than writing a HTTP server, even a simple one, from scratch.
As usual, men invent thing, women feel excluded, women try to invade, women are told to feck off, men eventually give up, women ruin thing, women celebrate "accomplishment".

Rinse and repeat ad nauseam. yawn

This is referred to this thread by the way:

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

(Where apparently I can't comment, lol.)
This feels kinda wrong, but I have to keep in mind that these people chose to give up these items.

From the TSA Blog (I cannot confirm if true)

When prohibited items come through the checkpoint, passengers are given options:

1) Take the item to the ticket counter and check it in your baggage or a box provided by the airport.

2) Many airports have a US Postal Service or other shipping services area where boxes, stamps and envelopes can be bought so you can ship your items home.

3) If there is somebody seeing you off, you can hand the prohibited item to them.

4) If your car is parked outside, you can take the item to your car.