fjhqjv's comments

The request was in my initial question.

If someone makes an argument that asking for legal counsel has a reasonable chance of leading to being killed or imprisoned for life, I would expect them to backup that assertion with some evidence upon request.

Stories about people being killed by police in other contexts don't provide any evidence to support the initial assertion.

I never asked for references of police killing civilians, as I'm aware that this happens. I'm specifically interested in references of police killing civilians for requesting legal counsel, especially in the course of questioning.

If this isn't something that routinely happens, then it is not a significant danger to the life or liberty of the average citizen to request counsel while being interrogated.

It's not that lawyers think you should never talk to police, it's that you should wait until you have legal counsel to do so.

Please cite references if you're suggesting that people in the U.S. are routinely killed or jailed for life without trial for requesting legal council.

This seems like it should be addressed more towards non-technical founders who should learn to code, not specifically women.

Otherwise, it's built on the assumption that most females on Hacker News don't already know how to code, which may or may not be the case.

What recourse would you have for someone repeatedly walking into your house at night to steal your stuff?

That's a non-violent crime, but it's still deeply disturbing for the victim.

I feel like the title is woefully misleading. This is just a hello world tutorial.

I like to go one step further and simply add a global event delegate to transparently tie DOM elements into a UI controller scoped to a particular portion of the application (to account for sidebars acting differently than the main content). Since 95% of the events handled are click events, it saves a lot of time.

The whole thing ends up being about ten lines of code to implement and handles event binding for practically the entire application. Literally ends up cutting out thousands of lines of boilerplate in larger applications.

I've also found that the actual event object is only useful in a very small amount of cases (drag events and such), to the point where if I ever really need to pass it along, I'll just write a custom event controller for it (using data-handler to specify the custom controller).

When I have too much free time on my hands, I cut out the data attributes entirely and instead route using good old normal hrefs, which as a bonus can render on their own if something goes wrong with the JS.

I wish the article would go more into keypress events in general and properly organizing code to make attaching shortcuts to it simple, rather than building yet another antipattern into the Jenga tower of bad jQuery code.

The real root of the problem here is systematically tying UI actions to events on specific elements in the DOM. Instead of working around it, why not write slightly cleaner code in the first place?

It's also not strictly necessary to use a third-party library for this unless you're butting heads with one of the edge cases the library is designed to solve.

How long can a computer hard drive remain in working condition while buried in a landfill?

    I wrote a haiku
    to run through a hash function
    and send to strangers.

Every time this document is run through a particular function, it returns:

> d15396b27a2b176e6315c9fbbec09e2c2e042e595755902e5ff5eccec1ca634b

If I changed a single character of the document, the function would return an entirely different string.

This means it's very, very difficult to come up with another document that returns the same string when run through this same function.

If I sent my string to a bunch of strangers, they wouldn't know what my haiku is. To find it out, they would have to run through every possible document ever written (and that ever could be written) to hope to return the string.

But if someone decided to say they wrote my haiku, I could prove I wrote it first by showing that the document returns the unique string that I sent off to strangers.

What this service provides is a way of making it easy for strangers to store and date these strings for me, because they're doing it anyway when they're using Bitcoins.