skysight-inc/HackerNews huggingface dataset:
> They even say in the article most of the gun deaths are by suicide.

It says "suicides, accidents or domestic violence." These are all vital statistics in determining the deadliness of guns.

Gun advocates have been arguing here that suicides shouldn't be counted, which doesn't make sense. Access to an effective suicide method is one more consequence of a gun-owning society. It should be acknowledged, analyzed, and discussed.

It seems as though advocates are arguing that the statistics should be filtered to make guns appear less statistically deadly. That's nonsense. This is a comparison of deadliness; a gun death is a gun death. Despite a decline in gun ownership, gun deaths are trending upward, and the NRA opposes smart-unlock features like thumbprint identification that contrast with the myriad safety controls placed on vehicles.
Discipline is only a small part of the answer and IMO the wrong place to start with, especially for people who have never had good fitness habits. You can only begrudgingly force yourself to do difficult tasks for so long. That's why fitness gyms see big influxes during the new year and then traffic dies off a month later. It's not necessarily that people aren't disciplined, its that they're bored.

What's more important is finding activities that are naturally motivating and fun to do. These habits are far easier to build when they are more rewarding. Rock climbing, squash, swimming, martial arts. If its fun, then you WANT to go more often. You actually think about improving your skills. And then you naturally build discipline because the cost of missing out becomes more expensive to you.
Suit yourself, remain ignorant.
"tumblr is blocked where I work"

You need a new job ;-)
One point in the article is the lack of oversight on gun sales to criminals.

If we're talking about "gun sales to criminals," we are way way less likely to be caring about gun suicides.
To add a third reason: to save it and view it later.
78 comments here, 61k signatures, and nobody has pointed out the glaring grammatical error in the first sentence of the petition.

I reckon that the intern who read the thing got a laugh from it.
There are people that believe that's already happened. The Waco & Ruby Ridge incidents of the 90s fueled the "government out to get you" mindset and started people talking about "not letting it happen again". And by talking I mean openly in mainline churches in the midwest-not gun shop boasting.

Since then it seems like federal law enforcement has taken a softer touch with their sieges. This could be simply a change in doctrine to avoid bad press but enough people believe it's more than that.

Also, these days it isn't so much about guys with guns from Wal-Mart as it is country boys that did a couple tours in IQ/AF as a 11something and their friends. <digression> That's also why the NRA is touchy about funding for studies on things--there's a perception that "the powers that be" want to diagnose everyone who served with PTSD and then use that as a reason to take away their guns. This is compounded by some despair over disarming IQ villagers so they are easy pickings for ISIS and the perception that "they were training us to do it back home". </digression>
One thing is for sure, if the define broadband as 25/3; mentioned elsewhere; and do similar for "unrestricted access" or whatever terms they use you can guarantee that is what you will get and likely the most you ever will.

Welcome to mediocrity by regulation. So the new baseline will be less than what I have now and what I have now can cost more since it exceeds the requirements... they can even brand it "ultra" or "extreme".

As soon as ISPs go under such regulation they all arrive at the lowest common denominator.
I think this is more about economic policy and less about government representation. It's hard to get more capitalistic cutthroat than the OS or high-end semiconductor industries.

And I'd imagine a majority of it is a consequence of the head start. If China had started development of both even in 1981, and sheltered their internal market from our product -- well, it probably would have turned out a lot like the Soviets, viz inability to maintain computational parity. But they would have something more complex.

Good luck developing an entire ecosystem now (ARM aside, but that's mostly due to Wintel's blindless on where mobile was going).
You're one person, there are 300,000,000 others that matter as well, and it's an established fact that Comcast, as a whole, is a horrible company. Their customer service is atrocious, and something I myself have had to deal with.

John Oliver had it right, it is literally "preventing Cable Co. Fuckery"
Thom Yorke May Have Made $20M on Tomorrow’s Modern Boxes
YouTube got an interesting DMCA takedown request back in the day: it was issued by the Chinese government at the time of the Beijing Olympics. The details escape me but the title of the video was something like "Olympic Gymnastics Beijing" or some other searchbait/clickbait, with a plausible-looking thumbnail, but the video itself was a super-critical video directed at the Chinese government. China issued a bad-faith DMCA takedown on the grounds that they are the only authorized distributors of what the video claimed it was.

IIRC YouTube refused to block the site for this very reason; the "10 days later" would have ruined the clickbait purpose of the video as the event would have been well over and actual legitimate outlets for its content would have sprouted up.
GREAT SALARY Core Developer at Dailymotion in NYC
Thank you kind stranger! :)
They still speak the same language, although in 60 years of separation the vocabulary has diverged a bit.

Earlier discussion: https://news.ycombinator.com/item?id=8766411
Féminisation – Chirurgie Faciale
Petition: If Congress enacts Title X, we'll lose net neutrality forever
They are used, but hard vs. soft realtime is tangential to the broader discussion here.

If we stick with the video game example, it has a real time goal: having frames displayed at the target framerate. The "soft" aspect comes from the fact it's tolerable for a game to fail some deadlines. It's certainly undesirable, but a few minutes of frame-y gameplay is not game-breaking.

Depending on the particular system, there will be tolerances of how frequently and in which ways a realtime deadline can be missed without constituting an overall failure of the system.
Introduction to WAMP, a Protocol Enabling PUB/SUB and RPC over Websocket
I have a 2012 Nexus 7 and I intend on doing a full-wipe when I upgrade to Lollipop because of the Nexus 7 flash issues. My Nexus 7 has really slowed down under Kitkat in the last few months and probably needs a good reset.
Building Custom Elements in HTML – Web Component
"If there is one figure closely identified with cannabis, it’s probably the late reggae legend Bob Marley – and late last year, Privateer signed a 30-year agreement to use his name on what is likely to be the world’s first global marijuana brand, Marley Natural."

Bob evidently keeps his promises even beyond the grave.
https://www.youtube.com/watch?v=zErP5QoMA3w
EDIT

Even though most gun deaths are suicide [1], your odds of killing yourself via suicide are still low. There's slightly less than 1% chance of your life ending via suicide. Taking away guns to stop suicides is a pretty big NNT.

===

[1]

Accidental discharge: 591

Suicide by firearm: 19,990

Assault by firearm: 11,068

Unknown involving firearms: 248

http://www.cdc.gov/nchs/data/nvsr/nvsr63/nvsr63_03.pdf
A lot of hardware manufacturers offer their own SDKs for interacting with their beacons, not letting you get the UUID of the beacon itself. Are you interacting with all providers' SDKs?
Some of those are surreal. Is it me, or did they photoshop farm machinery into their fields?
Posted 10 hours before your comment:

https://news.ycombinator.com/item?id=8855367
In my experience, implementation inheritance always makes the problems you complain about worse, not better. With implementation inheritance you've got to go and trace a class's entire inheritance hierarchy all the way back to the root if you want to reason about a method's behavior. With interface inheritance the number of implementations you need to look at is always 1.

More generally, interfaces give you a way to provide an absolute minimum in semantic guarantees down toward the root of your inheritance hierarchy. This is critical if you want to follow the Liskov substitution principle. And you should always want to follow LSP.
It has a depth limit, as well. It's truly a 2x2x2 cube. In my current setup, I can lean forward quite a bit, till the monitor is a little too close for comfort, but I cannot lean back at all. In playing with it, I've noticed that there's sometimes a bit of latency in the edge detection; I'll lean back, do some eye-ing for a second or two and then all of a sudden it cuts off. It gives me the impression that they're not actually enforcing a cube per se, but that their technique has increasing error rates outside of a sweet spot, and they have an errors-over-time cutoff.

I have a lot of sympathy for the difficulties in the implementation. The eye moves only a tiny amount, so you need a high-resolution camera to detect where it's looking with any accuracy (this is why they require USB 3). If the camera is already pushing the limits of inexpensive consumer camera technology, you can't easily expand its field of view without compromising accuracy.

Here's a paper that talks briefly about the technology: http://www.tobii.com/eye-tracking-research/global/library/wh...
IMO ack is a useful complement to grep if you do development: http://beyondgrep.com

Also, for general bash stuff, these are great, and IMO much better than the TLDP site that always ranks high on Google:

http://mywiki.wooledge.org/BashGuide

http://wiki.bash-hackers.org/doku.php
DFW would be correct if it weren't for the fact that every candidate for a major office that you are likely to encounter in your lifetime will be one of the garden-variety shitbags that's already a part of the entrenched establishment.

On paper, voting for a president vs not voting increases your chance of changing the world by about 1 in 50 million. In actuality, no matter who you vote for, its essentially going to be the same type of person.

I think that we are at a point where its still useful to vote in local elections and even in the presidential primaries (in some states, only a few thousand people show up for presidential primaries), but after that, the odds of making a meaningful impact are astronomical.

I still vote in all elections, but when I do it I fully understand that I am wasting my time.
When can I buy a phone with a Type C connector?
It's not really fair to indict this bug on OpenSSL's complexity. Over the last couple of years, both NaCl [1] and TweetNaCl [2] had carry propagation bugs not unlike the above. I'm surprised this kind of bug is not found more often.

[1] http://tweetnacl.cr.yp.to/tweetnacl-20140917.pdf

[2] http://blog.skylable.com/2014/05/tweetnacl-carrybit-bug/
Inside Trello, the venture-backed task-list app thats determined to get big fast
Possible that KitKat is "good enough" for most users?
Could you add a "hearing test" to your app, which does at least rudimentary tuning? Call it "headphone calibration" and I bet you'd improve the listening experience of people who don't know they are hearing impaired.
The issue was that one of the carry propagation conditions was missed.

The bug was discovered as part of the development of libsecp256k1, a high performance (and hopefully high quality: correct, complete, side-channel resistant) implementation of the cryptographic operators used by Bitcoin, developed primarily by Bitcoin Core developer Pieter Wuille along with a number of other people.

Part of our testing involves an automatic test harness that verifies agreement of our code with other implementations with random test data, including OpenSSL; though to reduce the chance of an uncontrolled disclosure we backed out some of the low level testing after discovering this bug.

This randomized testing revealed the flaw in OpenSSL. I suppose it's also a nice example of statistical reasoning (p=2^-128 that a uniform input triggers the misbehaviour) doesn't itself express risk, since while we've put enormous amounts of CPU cycles into tests we've certainly not done 2^128 work. In this case the reason our testing revealed the issue was because we used non-uniform numbers specifically constructed with low transition probability to better trigger improbable branches like carry bugs (https://github.com/bitcoin/secp256k1/blob/master/src/testran...). I used the same technique in the development of the Opus audio codec to good effect.

(Whitebox fuzzing tools like Klee or AFL, or branch coverage analysis, while good tools, seem to not be as effective for errors where the code completely omits a condition rather than having a wrong condition which was not exercised by tests.)

In libsecp256k1 the field operations (nearest parallel, we don't use generic bignums) are augmented with proofs of correctness (e.g. https://github.com/bitcoin/secp256k1/blob/master/src/field_1... ) though only a small part of our provable correctness can be machine checked currently. Of course, correctness proofs are only one part of our strategy. Fortunately, because of the much smaller scope of libsecp256k1 we likely have an easier time hitting a higher level of assurance than OpenSSL does.

We were initially unsure how serious the bug was and came up with several sophisticated attacks that were fortunately prevented by OpenSSL not using its optimized squaring operation in all the places it could have used it.

Perhaps most interesting is that one of the reference implementations of curve25519 had almost exactly the same bug as OpenSSL: https://gist.github.com/CodesInChaos/8374632 but it seems to have gone largely without notice.
Also, hilarious side point: what happens if an autocratic regime customizes Linux/*BSD and ignores their open source licensing obligations?
The NRA is against anything which gets in the way of a patriot and their duty. RFID and similiar 'safety' features can be used by the government to identify gun owners, confiscate weapons and suppress the public's right to revolt against their tyranny. Americans have a sacred right enshrined into the Constutition to be able to bear arms in order to respond to the presence of government with deadly force.

It's no different the the argument people here sometimes make that black markets and TOR are necessary for freedom of speech and civil liberties, even if having them means enabling criminal activity - because the greater threat is always the threat of a government which can't be spoken up against. In the case of guns, the greater threat is always a government which can't be put down.
Obama won’t fire Aaron Swartz’s federal prosecutors
It would be fun to set off a forkbomb with a small sleep call in a system and watch it cause pandemonium. Shoot a couple of the rabbits so that they start infighting, and then watch the system slowly eat itself as legitimate processes enter the fray :)
I don't see the direct connection between the suicide risk of a single gun owner and the ratio of suicide to homicide in total gun deaths.

The claim regarding suicide vs homicide is easy to confirm (https://en.wikipedia.org/wiki/Gun_violence_in_the_United_Sta...). It is not possible to predict every suicide, the best we can do is make an approximation using obvious risk factors like hospitalization for mental illness. There are millions of gun owners in the US, so yes the chance of a suicide is small.
Ah, like you say, there are many different techniques. The type I'm describing in the OP is Vipassana[1], which is a systematic scan of physical sensations, part by part throughout the body. Not 'thinking of nothing', nor 'daydreaming'. Of course, some other people do use those sorts of techniques, so confusion abounds.

1: https://en.wikipedia.org/wiki/Vipassanā
> > Well, among the key facts necessary to understand that is that the "safety features" are not pure cost-free benefit, and the NRA believes the costs outweigh the benefits.

> Sure. Advanced safety features in cars probably cost a lot to develop, too, and I'm sure there's a lot of people who think seatbelts are lame and cars would be cooler without them. But car companies actively work to promote safety while the NRA seems to actively undermine it.

The cost at issue here is generally not monetary.
Most safety features are designed to prevent the weapon from firing, which gives rise to the expression "loaded club."

Consider, e.g., the magazine safety, which prevents a semi-automatic weapon from firing without a magazine, even if a round is already chambered.
If I owned a handgun, which I do not, I would absolutely want this feature.
The likelihood that it would prevent a potentially fatal negligent discharge is much higher than the likelihood that it would be the decisive factor in me losing a gunfight.
However, there are combat techniques that depend on the weapon firing without a magazine, and competitions in which it would be difficult or impossible to participate without that ability.
There is also the risk that the safety would otherwise interfere with the operation of the weapon.
I wouldn't find it surprising at all if the fault lies with qemu's implementation rather than with some inherent property of 9p. The performance test I ran was with qemu's virtio 9p implementation: compared to a kernel compile on the host, one in the guest took a few percent longer on a virtual block device, or hundreds of times longer on virtio-9p.
On Solaris you don't ship statically linked binaries. All Go binaries are linked with libc.so. In fact, amd64 Solaris doesn't even support statically linked binaries at all. It won't exec them.

The situation is exactly the same as on Windows. Windows Go binaries are dynamically linked agains Windows standard libraries, and Go binaries use the shared libraries instead of doing system calls themselves.
UDP is just not as reliable over NAT (mainly due to crappy NAT implementations). SCTP tries really hard to keep it working (including heartbeats on idle connections), but implementing the 50% of SCTP that HTTP benefits from over TCP will work exactly as well as HTTPS whereas SCTP over UDP runs into lots of tiny issues due to nobody having tested it on their $5 NAT before putting it in a wifi router or a DSL/CABLE modem.
There was an alan kay video on the front page yesterday.
I don't think I've ever upvoted after reading/watching what's been shared. I normally upvote, if at all, prior to clicking, otherwise I would never remember.
Goals, Objectives, Habits, and Triggers
I feel you.

On the other hand I understand that it is a business. So the business thinking is „not to throw away what you do last 18 month“.

But as you pointed out, if something doesn't work, you should not be scared of a change. Even if it mean to delete everything what you did and start over.
Being cynical about it, UK banking has been investing in the unregulated end of the cannabis industry for decades.
Even better than USB 3.1 is Wigig and wireless charging. Broadwell does support Wigig. Where are the Wigig docking stations now?
You might find this interesting -

" Computer Science in the DPRK
A view into technology on the other side of the world "

http://media.ccc.de/browse/congress/2014/31c3_-_6253_-_en_-_...

EDIT - ok, it's already linked in the article. It is interesting.
This post reminds of this response to Dropbox launching here:
https://news.ycombinator.com/item?id=9224
It's much, much simpler than that. You just project a ray from the X-ray point source through the center of a voxel onto the detector, interpolate the X-ray energy detected, and add that energy to the sum in that voxel. Repeat for each voxel and each x-Ray taken (CT scans take a bunch of x-Rays going around in a circle), remove some noise, and boom you've voxelled the data. Fundamentally you're just summing the energy that passes through each point in space. It's trivially parallelizeable.
Not me; I want a thin retina laptop with long battery life...
From CES: "A story in three acts" https://twitter.com/dakami/status/552986333434490880 If you can't see it, it's advertising DisplayPort over USB Type C!
When I was even more of a newbie programmer than I am now, I stumbled across Pharo and the Seaside framework. Both of them have excellent tutorials which taught me a lot about MVC, OO, and proper application design. I went on to build a prototype in Seaside and found it to be a very enjoyable experience.

For instance, if I messed up something in my code and had an error, the debugger pops up. In this debugger I can not only browse the stack trace and manipulate those objects, I can actually fix what is broken and resume execution of the program from that point.

In Seaside's dev mode I can toggle viewing all the components that make up the currently displayed page (a page isn't a textual template, but is constructed from objects). I could manipulate those objects in the browser and see the effects of those changes immediately. This was useful both in exploring solutions to problems and in debugging code.

Having experienced such tools, it's hard not to miss them when programming in another language. I used to use Light Table with Clojure and Javascript to kind of recreate the effect, but what the author writes is true: abandoning your familiar textual tools lets you do some really awesome things. It completely changes your development and debugging workflow.

I'd love to be able to program in Smalltalk professionally, but I really couldn't find that kind of gig (especially entry level) in my area. But even if you can't see an immediate business use case, just spend a weekend going through the Pharo and Seaside tutorials. If learning lisp is important "not because you'll use it but because it will forever change you" (to paraphrase) then learning Smalltalk is important in the same way. Just be aware that when you have to go back to another environment, you might be a bit sad. :)
There is a surprising lack of Engrish in the included apps.
Well, that's where the gains are still to be had (whether we want them or not).
Has Bitcoin Gone for a Random Walk?
http://jpos.jurassicpark.sk/

http://www.jurassicsystems.com/
I've seen this technique used with transparencies on an overhead projector before. Things get interesting when the fields aren't aligned exactly.

https://www.youtube.com/watch?v=LCIsIfEOEI8
The problem with retrospectively explaining success is that you fall prey to both survivorship bias and narrative bias. In physics this is known as anthropic bias.

All post-hoc justifications for the success of any business are dangerous because the gloss over the most important fact: the only reason we're asking the question in the first place is because the thing turned out to be successful.

So what can you conclude from this that is actionable and applicable to you? Absolutely nothing other than the fact that we aren't good at predicting the future, but are good at retroactively fitting the present to the past.
Inductors do this as well. The changing magnetic field causes the windings to vibrate, creating an audible sound. The sound my work monitor makes sounds like an inductor to me.
Nope. In is_subtype:

> # If `sub` is a formal type, then it is accepted if its bound is accepted
https://github.com/privat/nit/blob/2323b17d46c873e8c6c41b75d...

Ruby is dynamic and the interpreter is feature-rich. People are just exercising self-discipline. Nit intends to be “a robust statically typed programming language” which is very different.

Also, could you point me to the Nim feature? All I see is overloading.
IIRC, the main issue with nonTLS HTTP/2 is broken web proxies. This is why Google deployed SPDY in https only, and also why they didn't use SCTP as the basis, but instead reinvented about 50% of it on top of TCP.

Google didn't want something that would break even a tiny percentage of existing installs.
Seems like they could do this by just adding a second iSight to the top of MacBooks. That's a much more appealing feature than a touchscreen for a laptop for me!