skysight-inc/HackerNews huggingface dataset:
Guns already have to have serial numbers (equivalent to VIN, but less structured, and managed by manufacturer, and no central registry).

The issue is that car accidents are accidents (often involving negligence), whereas gun crime is generally willful (sometimes involving crazy people, but generally just criminals).

There's the issue that a lawful collector or random hunter or whatever with lots of guns is a lower risk than a gangster with one gun, and the risk per gun is vastly lower for a law abiding person with lots of guns vs. a bad guy with one or a few.

In fact, I'd bet that gun crime goes down as the number of guns possessed goes up. Obviously 0 is the least, but 1 is the most, and it's probably close to exponential after that. The guy with 31 guns is way less likely to kill someone than the guy with 3.

The only risk when someone has lots of guns is that they'll get distributed to others -- either through theft or through willful straw-man purchase or other distribution. A person who holds ~30 guns for a gang, then distributes them as needed for crime, is a problem, yes.
The First Annual Objectify A Man in Tech Day
as someone who can pay for my own healthcare

Then just do it. It is unfortunate that Obamacare is forcing you to get insurance, but I'm sure you can find a medical plan with a ridiculously high deductible (specifically for people who are wealthy[1]) that will cost you next to nothing[2] and, similar to life insurance, protect you and your assets if something catastrophic happens.

1. I'm making no judgement about whether you are wealthy or just choose to pursue no healthcare.

2. Assuming they are still available next year. http://www.dailyfinance.com/2012/07/13/obamacare-could-kill-...
Fasten Your Seatbelts: Google's Driverless Car Is Worth Trillions

Amazing! He studied and compared all other driver-less cars to Google's and came to this conclusion.

I know a writer getting paid for clicks wouldn't forget that virtually every major car company is working on http://en.wikipedia.org/wiki/Driverless_car#History
Six Magical Tips to Understand the Psychology of Your Fonts
Yeah I agree with most of your points. Australia never had the gun culture the US had (even before the Gun buy back). Most people in urban areas did not own guns, it was (and remains) mostly farmers.

I don't have a citation, but I remember reading a justification for suicide prevention fences on bridges, that found that it didn't just stop suicides from that bridge, it did so without raising suicides in any other way (i.e it lowered the total suicides).

I've always found it difficult to think of a solution to America's "Gun Problem"... It is codified in their laws, and from that is deeply engrained in their culture. Any reform has to first start reforming the culture, in my mind.
I saw this as a way to dig into the order flow business, but it seems they don't have their ducks in a row -- I would have waited for the production trading setup first (which I presume GETCO would provide via OCTEG LLC) before getting PR coverage
The next several years should prove "interesting" for the car market. Driverless cars and assorted state DOT departments pushing for black boxes in cars on the basis of tracking milage are both going to see pushback from the general public.

I've bought two new cars (and 1 used) in the last 15 years. The oldest lasted 11 years and 256000 miles. The used was a truck when I bought my house. The newest is a diesel wagon getting 40+ miles to the gallon, I don't plan on selling it anytime soon.

I will be loath to add GPS for purposes of tax calculation (sure it can be done based off registration or other means -- at least the GPS data isn't there). And, I don't predict any incentive to move people from driving their own cars to self-driving cars.

The above is in addition to the "independence" baked into the American culture about the open road and the automobile.
This is great! I tweeted this but couldn't add you because I didn't find your twitter name or contact address ...? https://twitter.com/dirkk/status/294333906902196224
Over-literal interpretation of analogy and metaphor can be a problem.

(http://www.amazon.co.uk/Its-Raining-Cats-Dogs-Expressions/dp...)

(http://www.amazon.co.uk/Asperger-Dictionary-Everyday-Express...)
Show HN: I made a datagrid widget set based on Backbone.js
I think Russia allows "gas pistols" with a special license too. Nonetheless, a pistol like firearm in general is difficult to aim and use.

Mace is fully legal in the US, but not very efficient.

Actual tasers (those carried by police) are probably illegal in most countries as technically it's a short range grenade launcher (it uses an explosive charge). They are incredibly useful, but are unfortunately overused in cases where they are completely unwarranted. A simplified taser-like weapon would be more useful in this cases (little training, used by someone who is statistically likely to be opposed to firearms in general).
Welcome to HN. Where we state opinions as fact and anecdotes as truth, usually with some hand wavey out in case we're called on BS. :)
Don't bother, libertarianism is like a religion to these people.
A low-cost clone could be mounted on the ceiling in a room. Some stun grenades and tear gas would disable the shooter anywhere in the room. This would be a cheap solution. Include a wireless mesh network connecting the devices, and they could disable the shooter even as he flees the first room.
I don't understand. Why license it out? Isn't this like the iPhone?
def cal(n):
if n == 1:
return [1]
else:
x = cal(n-1)
return [1] + [x[i]+x[i-1] for i in range(1,len(x))] + [1]

who wanna hire a junior developer? I will work for free in SF,CA
A similar sentiment: http://www.shirky.com/weblog/2013/01/remembering-aaron-by-ta...
Or, in more humorous form:

http://www.penny-arcade.com/comic/2004/03/19
Well, you are probably right. I don't know him, which means that I am operating with imperfect data. I still contend that a little more than an apology on a blog is in order. Perhaps a phone call or an in-person meeting if practical. If I am reading this correctly the comments affected Heather to the point that she had to cry. Not cool.
> I hate how both anti-gun and pro-gun groups have blocked real studies out of self interest and fear, and how the debate in general is essentially uninformed by technical facts and often driven by racism and emotion (on the anti-gun side) or detailed crime data and any reasonable concept of competing claims as well as general paranoid nuttery (on the pro-gun side).

Do something to validate their trust first: gun rights groups could easily be placated if the first thing any task force does is come out squarely against the assault weapon ban and demand investigations into what magazine capacity limits should be _before_ suggesting legislation.

Anti-gun groups would be placated by supporting universal background checks. Both would be placated by a Square-like device for instant background check for transfers, and so on.
I do certainly take your point on the "if you were white" front, but I want to use that to lead into something Tony Judt wrote in "Ill Fares the Land": the post-war period was prosperous enough that political movements, in many instances, shifted from striving to overthrow and replace the system towards striving to be included in the existing prosperity. MLK Jr was indeed a black-rights activist and a socialist, but he didn't see his form of democratic socialism as something that required a violent revolution of genocidal proportions the way that, say, Lenin had, or even the way that German anti-fascist partisans had.

>I don't think I could afford to consume that many Playstation 3 games in 1950, either. In fact, I don't think anyone could afford to consume any.

Thank you for making part of my point for me. If someone couldn't consume PS3 games in 1953-1963 because they didn't exist, and someone can't consume PS3 games now because they're unaffordable on today's low salaries (well, low salaries for most people outside Hacker News), then what good is the existence of PS3 games to this person?

Where's the worth in increased production and variety of consumer goods only an elite minority can afford to enjoy?
You know what would be better than a blog post or Twitter apology? Go away for a little while. Don't Tweet. Don't Blog. Don't comment or talk. Go away...and code.

The programmer community likes to fancy itself a meritocracy. Presumably, that implies that you are judged on the merit of your programming ability. Ask yourself: of the people involved in this whole brouhaha, whose code have you read?

We are all very busy, and none among us has the time to read the code of every other individual. This is where the concept of "meritocracy" breaks down. At some point, reputations count. The proper way to do this is: I know Joe. Joe writes good code. Joe recommends Bob's code, and when I looked at Bob's code, it was also good. I now trust Joe when he recommends people and/or their code.

The wrong way to do this is: Jim's a celebrity. Everybody loves him. Everybody parrots what he says. He must write good code.

Celebrity culture is directly counter to a meritocracy. So, my challenge to the "celebrities" involved in this incident: if you fancy your high positions to be well and truly earned, remind us of that fact by going away...

...and writing some kick-ass code.
"You can't solve an administrative problem with a technical solution." (Or something like that.)

The premise of this post is very misguided and ignorant.
I really can't grasp how there's any nuance here. It's really straightforward.

"What you're describing is a conflict of interest that exists at the heart of capitalism. Owners want to pay less, employees want to make more."

Sure, and if workers conspired to illegally appropriate the profits from the company for themselves they'd go to prison. Plain and simple, rightfully so. Somehow if the company conspires to steal higher-paying job offers from their employees that's not particularly appalling or immoral to you? It's one step away from taking the money straight out of their wallets.
Rasterisation doesn't require any real acceleration structures. There are various caches, but nothing comparable to a kd-tree or BVH.
As long as Balmer is still there, as long as they continue to threaten other projects with patents, I couldn't care less about Microsoft or their products, no matter what bones they throw out for free.

I'm not anti-Mono btw. I also like F# and .NET and I even think that Microsoft isn't even the worst company around. I also have a Windows license that I use back home. But I simply don't care.

Also, IronRuby is abandonware.
making assault rifle (type) weapons illegal

What features would you ban and why? Most AWB features don't have a whole lot to do with a weapon's ability to kill people or suitability for criminal use. Magazine capacity is really the only factor that has any practical effect, and there doesn't seem to be much evidence that restricting that had any impact on crime.
Nothing is better than quotes like that

:-)
Update on Dot Com’s MEGA – Website In World’s Top 150
Very disappointed with the people that made these statements, they should know better.

Kicking other peoples puppy is never cool, people forget where they started.

Some times you have to take this sort of crap on the chin and keep hacking away, the best thing you can do in situations like is just ignore them.

I think in this case they have realised how stupid their statements where and are hopefully truly sorry for the hurt they have caused.

Also a note to those with many followers, don't be a dick.
1, freedom is not free
2, you might pay in cash or human life
3, if you like gun control, why not went to china?
In many ways it parallels what people do in C: until you get to the scale where precise logging and style enforcement matters, you just forge ahead in the path of least resistance. So like you said, they printf or console.log, use lint or jshint, use -Wall or "use strict" etc.

Btw I prefer console.error :)
It also seriously limited access overall (either by law or by culture). Otherwise the gun suicide rate wouldn't have been affected, since most suicides are single-shot (except for Russians...), and shotguns/rifles are used more in suicides than they are used in murder.
> it's advantageous for cars to talk to one another

If "never trust the client" is a truism in software, I'd assume it'd be doubly so for P2P communication, and add another doubling for a situation involving humans + relatively high masses and speeds.
Xerox's GUI was worth trillions.
I'm amazed by people's stupidity in continuing to advocate solutions that just don't work. And hopeful for the future of electric and hybrid cars, which will do a lot to reduce this problem. Although, judging from the comments, it sounds like a pretty large amount of the problem has nothing to do with commuters.
Dear Steve, Heather and anyone else that fits the bill

It's okay. People sometimes say hurtful things despite historically having strong opinions about never belittling other people publicly. It doesn't mean that they truly mean it, and it doesn't mean that you should take these negative things to heart either. People slip up because we're multifaceted creatures and despite our intentions to be the best person all the time, well that's just not possible.

Regardless of whether what you're being criticized for is justified or not, it is inevitable if it's been made public. The irony in this case is that the bully is being made feel worse because of his past blog posts, which is also sad but just as inevitable. It's okay Steve, we all fuck up, and the ease of doing it on Twitter doesn't help.

Heather, I promise you that any decent potential employer is still exactly that. Nobody will disqualify you from a job position based on something you've made. You've open-sourced it, so if anything you get bonus points. You will always be criticized, the trick is to ignore the haters and know that people in a situation of genuine critique (i.e. candidate interviewer) will never judge you (as badly) as some people on Twitter did.

Do not let this discourage you from contributing publicly in future either, even if your code IS shit. Everyone's code is shit, at least to some people. As long as you're happy with it, that's all that matters. Also, somewhere down the line you'll look back at it and think "Wow, that's shit code", which just means you've gotten so much better.
I've contacted her privately, as well. I thought it was important to publicly apologize, since I publicly said the mean thing.
both Perl and Python use PCRE

No, Perl doesn't.

PCRE was written because a lot of people liked some of the ideas that were first introduced in Perl's regular expression engine. But PCRE was a reimplementation, and never was all that compatible with what Perl was doing.
Thank you for taking the time to write these translations. In fact, I'm going to bookmark this thread and use it as a reference in the future.

I feel these examples serve more as a selling point for why one would use something like `replace` over a cacophony of flags and pipes. The interface for `replace` is simple and elegant. It does one thing, and it does it well. I think that's commendable.

P.S.
The `sed -r` flag does not exist on POSIX systems like OSX. You'll have to use something like perl -pie, or write a convoluted buffering loop.
The above is in addition to the "independence" baked into the American culture about the open road and the automobile.

Do you think there is something inherently wrong with the feeling of independence and happiness attained from the car culture in the US?

I am still dubious that self-driving and non-self-driving cars will be able to share a road in the future. If this doesn't happen, I doubt Americans will freely give up their 'right' to drive the way they want.
If empathy were a limited resource that demanded to be spent only in descending order of the seriousness of the potential injury, then you might have a point.
There are a few open source projects which I would be willing to ridicule. In general the projects have traction, a significant history, and horrible code which never gets more than marginally better over more than a decade. It is one thing to be starting out. It is something else to decline self-improvement.

The problem though is this (and I have been on the receiving end of very harsh criticism of people I respected, some of which was shown correct over time), that there are often problems with critics jumping to conclusions and at the same time not being very detailed. Thus a response like these tweets can only be a "gut reaction" and never really very helpful to anyone. There is no time involved trying to grok the code. There is no opportunity to discuss what potential tradeoffs have been made or why. These two things need to be corrected.

I don't think folks should criticize code without trying to work with it and understand the API's. I don't think folks should leave a critique like "that's the old 1990's way of doing things" or "that code sucks." It is much better to get something like "So I see a few problems with the code... and ...."

In fact the few times I have gotten the latter (publishing code and getting responses like "I see some important concurrency issues there. This isn't safe to run on production.") I have been happy with the panning because I could fix the problems. But that's a far cry from what the article is referring to and it is, unfortunately a lot less common, IMO.
On the other hand, violence is generally decreasing in the US, so it's quite possible non-coercive approaches could substantially affect the spree-shooting problem.

Deeper structural changes would be needed to fix the actual gun violence problem in US which is completely different from the spree shooting problem (they're two separate problems, effectively): the violent crimes committed by illegally kept pistols (straw purchased, stolen, inherited, bought off the books) and is usually closely related to the drug war. It is also a deep inequality issue: the poor and minorities are far more likely to be affected than suburban whites.
There's a lot of criticism here, but as someone who has never done algorithmic trading before - it's very exciting. I don't believe Quantopian's intention was to target veterans, since I'm sure you vets have your own system for testing and trading already worked out.

As a newbies with no experience in the field at all, it is unlikely that I would've even tried without a platform such as this. If Quantopian's intention is to bring more people into the field and get them exposure, even now, it's quite an impressive stepping stone.
I was one of the people who made a comment about this.

I'm not going to defend that I think attempting to replace sed/grep is a bad idea (especially not in 140 characters), but I will defend people's opinions.

Everyone has one, most of them you won't agree with. Whether they're nice or not. I'm generally not a nice person, at least online, that's my choice. That said, especially with this being the internet, you have to deal with others opinions.

While some people may go above and beyond (even myself sometimes) and actually be very mean with their opinion, that doesn't change the fact that they're entitled to it. If you don't like it, ignore it. If you can't ignore it, then you won't survive.

The fact that people somehow managed to turn this into the continuous drama debate about gender is just pathetic.
> Rasterization also requires "acceleration structures," kept in memory

Yeah but surely not for the geometry itself. In rasterization, we may use simple low-overhead acc. structures to efficiently traverse a relevant sub-set of the whole (but coarsely described) scene for some fancy culling, collision detection (OK that's not really rendering) ... but geometry (vertices, polygons, vertex attributes) does not need to be traversed like that and thus does not have to be stored as individual triangles in an octree or bounding-volume hierarchy or what not. Quite a difference in overheads here. In GPU terms, with rasterization you have geometry neatly stored in vertex buffers and an awesome Z-aware traversal method with vertex shaders. In a simplistic current-gen fragment-shader-based raytracer, each pixel traces a ray traversing through your acceleration structure which may be stored in a volume texture (ouch, so many texel fetches...) since vertex buffers are not sensibly accessible in a frag shader.

> scenes that are indistinguishable from reality

This would also require a high dynamic range output device. Looking directly into perfectly raytraced sunlight still won't glare and blind me like the real world does, but indeed, by 2050...
Plus, it's a good thing that there are others in this race. It creates diversity of solutions, which should end up being safer, more robust and less likely to suffer cascading failures.
(I copied this from another HN posting)

I was one of the people who made a comment about this. I'm also assuming the reason I was pulled into this is because people much more important than me said similar things.

I'm not going to defend that I think attempting to replace sed/grep is a bad idea (especially not in 140 characters), but I will defend people's opinions.

Everyone has one, most of them you won't agree with. Whether they're nice or not. I'm generally not a nice person, at least online, that's my choice. That said, especially with this being the internet, you have to deal with others opinions.

While some people may go above and beyond (even myself sometimes) and actually be very mean with their opinion, that doesn't change the fact that they're entitled to it. If you don't like it, ignore it. If you can't ignore it, then you won't survive.

The fact that people somehow managed to turn this into the continuous drama debate about gender is just pathetic.
Here's a more detailed description:
http://www.dedoimedo.com/computers/fedora-18-kde.html
the hell are you talking about?

every person that created something worthwile in this world has been ridiculed. for good reason. i hate the fact that people here spout that uber positivity crap.

you know what, you mess up -> you get ridiculed, what do you do? you make something better.

The world is not this pretty flower place where everyone can be happy and strive at the same time. there is no rich without poor, and there is no great without bad.

please everyone be happy is a stupid argument to make. it actually makes people NOT improve.

it has nothing to do with elitism developer community. it's the same everywhere. you don't get patted on the back for doing something mediocore at best, well that is, unless you're an mba.
I have seen production code that makes this look like poetry. And I've written some of it.
I get what you're saying for the "already in a REPL" thing, but as far as fork/exec overhead, xargs does a single fork/exec for every thousand or so files you search; the overhead is tiny compared to everything else.
In his "apology", Steve says three times that he was "accidentally" an asshole. That doesn't sound very sincere.
It is an unfortunate fact that this sector of the world has a higher proportion of absolute assholes than other sectors. Egos are extremely fragile, cognitive dissonance is high, arrogance is the norm.

I'd say don't let it get to you, but that'd be dishonest. It'll get to you. The thing is you can't stop. That's the hard part.
Or install gnu sed
I think the detection and logging aspect has a lot of promise as a cheap and widely deployed system.

I'd worry about the liability from false positives with a active response system. Even something as limited as locking the doors to a room to contain the shooter could lead to liability from someone being trapped with the shooter.

If you assume a large indoor setting, something like a mall or school, maybe combine the detection network with a evacuation guidance system that leads people away from the incident. Mass shootings are pretty rare so maybe you could use it as a general "smart evacuation" system. OTOH there's probably a crowd psychology problem in there that makes that unfeasible.