skysight-inc/HackerNews huggingface dataset:
The study appears to be using "arrested" to mean "convicted of a crime for which the person could have been arrested (taken in to police custody)"? Example: I have never been arrested/taken in to police custody but, I was convicted of providing alcohol to minors at a college party and, had I not willingly taken the citation from the officer or, had I been belligerent and uncooperative, I could have been arrested. Technically, you could argue while the officer was issuing me the citation I was under some sort of arrest, but that does not comport with either the legal notion of being under arrest or what most people think of as being under arrest.*

Given the journal, that seems like an odd error to make. I could have that wrong, but it would make sense given that article specifically mentions truancy and underage drinking, two charges which seldom result in arrest.

Maybe that makes the statistic a little less shocking to those surprised by the number? Again, I certainly could be wrong, but it really would be surprising if the 40% refers to people actually having been read Miranda rights, hand cuffed, placed in a police car, etcetera. Even for other common crimes for that age group, like possession (generally marijuana), usually a citation is issued and the drugs are seized but no arrest is made. This is all said from the perspective of a judicial clerk in Portland, Oregon, who works a lot with the dockets related to citations related to minor misdemeanor offenses. Perhaps it is different in other states.

Anecdotally: almost everyone I know well has been convicted of a misdemeanor of some sort for which they could have been arrested but only one person I know has ever been taken in to police custody.

* http://en.wikipedia.org/wiki/Arrest#United_States_2
Fair enough but if you reply to someone...sometimes people assume you mean them.
Oh I see, Pinboard is so innocent, so pure, that a honest tip about how to reach more people who can find their service useful should be modded into the ground.

I've tainted the Jesus of bookmarks by even implicitly suggesting in my post that they might be writing with the intention to be read. No, I suppose their intention is way more cosmic and godly than such low earthly concerns, how stupid of me.

Aight, aight. I never stop learning when I'm here on HN.
Another huge advantage with indoor farming is the decreased need for pesticides. Decreased production and environmental costs + a healthier, organic product for consumers... what's not to love?
Ignorance of things like Lisp is a cultural defect in computer science. It's just a symptom of a greater problem: lack of awareness of what has already been done by prior generations. If electronics engineering were like CS, some twit would be reinventing the long-tailed differential pair today, and trying to get a patent on it, with full backing from his research institute or employer.
There's a lot of religious imagery in the text with discussion about fractal cosmology, mysticism, Lisp's natural connection with the human mind, etc.

It seems as though the author is trying to sell a religious experience to his readers. If that is the case, that's interesting in the sense that it is certainly unlike any other programming text I've read. I personally think evangelizing Lisp should be in the form of making it more familiar, human, and relatable to the average programmer, but I can't help but to respect the sheer uniqueness of the approach.
Correct. To see the original, you can check the journal itself [0] (check for it on google scholar if this link doesn't work) or look for it at your nearest academic library, if they have it. It is published in the April issue. The conclusion was that the difference was not significant for the female population. Keep in mind that the study was based on a limited sample so care must be taken when generalizing conclusions from the starting data to the population as a whole.

[0] http://cad.sagepub.com/content/60/3/471.abstract
http://scitr.com/a1j
First, I'd argue that none of that would be "beginner" things.

Programmers always seem to forget what it is like to not know how to program. A beginner would never use something like that.

Second, when you bring class-oriented Java-style constructs to JavaScript, it looks ugly because it's not what JavaScript is about. JavaScript is different. It's got a completely different way to do OOP, which you have to learn.

I'll agree that JS has weirdness. But a lot of the things we think are "wierd" are things that seem strange because we've programmed in Java or something else.

Ask someone who started with JS and only learned JS. They don't find those things strange at all.
Since it was just released, I doubt many outside of github have an established workflow with this.

Maybe someone with the Windows client can provide more insight, given the similarities.
This is an update not a new release.
Kubernetes on Mesos (scalable Docker orchestration)
I have used both of those.

At the bare minimum, I want them to automatically use the suggested tags, so I can bookmark things with a single click.
P2P would make the service quality depend on how many people were online, etc... I think they'd rather sort it out another way.

But regardless, even with that offer, Comcast scoffed at it, citing Netflix would still be a "large burden" to their network. (which would be even more-so false than it currently is).
OK. this is actually true. thank you so much
Thanks! You're right that gaming isn't that big on Mac. The main target is going to be iOS initially with Mac on the side, but the Mac version is already ready and much easier to link to a bunch of people :-).

The game is written in Obj-C, but I think with either gnustep or cocotron (or I think there was a commercial one that I'm forgetting...), it wouldn't be too hard to port since it's almost entirely OpenGL. I hope that will be in Pentumble's future :-).
Regarding the tone I concede it is a little over the top, but considering the author works for D-Wave[1] building the future of (Quantum) Computing I think it is not without merit.

It may be better to leave the intro part for the end as it may alienate programmers that have preconceived notions about lisp based on hearsay and not actual experience (i.e. it's enlightening, it's old, full of cruft, hard to read, it's functional, Clojure is the future of lisp).

It is also very much a WIP that the author didn't submit so keep that in mind.

I hope he gets to writing the chapter on Quantum computing: http://learnlispthehardway.org/book/3-14-0-quantum-computing...

[1]: http://www.dwavesys.com/
Rex: Minimal Javascript based RPC
Is there a Betteridge's Law for headlines which are so vague that they could be true, without it being significant? I mean, every couple (and individual) in the world could be the first humans to travel to Mars, so it's sort of a weak statement. hgow about "Meet the couple which is the most likely to be the first humans to travel to mars"
Simple syntax "Hello world!"

++++++++[>++++[>++>+++>+++>+<<<<-]>+>+>->>+[<]<-]>>.>---.+++++++..+++.>>.<-.<.+++.------.--------.>>+.>++.
The Mac client has been around since 2011 ...
Raspberry Pi Compute Module becomes Pico-ITX SBC
How to make a product video for under $150
Thinking about this:

By merging children into the parent resource, he traded a reduction of requests with the loss of separation of concerns.

How about adding a layer instead whose only concern is the reduction of the number of requests for the client. It would collect and merge the info from parent and children resources and return it in merged form to the client ?
I think this ingredient will change how a big part of the cloud interoperability problem can be approached. Once you only have to manage a few, relatively static set of VMs, and let kubernetes provide both the API and the scheduler for actually running services, it will become easier to just run your stuff on aws, azure and gce.
that's the one that anyone can just paste and use right? it seems like it must be rate limited as well..
It's complex because it's powerful. ~A is the most common directive; it simply prints an object. '~{...~}' (braces) iterates over a list, applying the directives within it to the list elements. Within that construct, '~^' exits if the last element of the list has been consumed; it's used here to keep the separating space from being printed after the last element. '~@(...~)' (parens) capitalizes words in the output of the directives it contains, downcasing the non-initial character of each word.

So there's a lot more power here than in 'printf' control strings. If you find the more exotic notation unintuitive -- and you certainly wouldn't be alone -- you don't have to use it.
Forget acquitted, what if charges are never brought in the first place? Should the Nixons of this world have a right to be forgotten?
That could be taken as an argument that police intervention in schoolyard violence works.

My point isn't that schools are more violent, but that we're correctly identifying that managing school violence is not part of the teacher role, and simply ignoring it as "boys will be boys" isn't good either.
I did not intend to repeat something pg said. Citation needed.
My mistake! Sorry!
Adding / Updating Meta Tags Dynamically In ASP.NET MVC 5
You don't need to afford legal action to make a FLSA claim; the point about people being unaware of the legal mechanisms available to them (or even the illegality of it) is I think much stronger.

If I was working hourly, I'd pray they make me work unpaid overtime, because when I was ready to hop jobs I'd walk into court with a fat 2x back wages (1x + liquidated damages) [1]. If they retaliate, it's up to 3x back wages.

[1]: http://www.dol.gov/dol/topic/wages/backpay.htm
As an outsider that seems incredibly wrong. The answer to youth gangs is not more security. Perform a root cause analysis and go back to the fact that kids often fall into gangs because parents are not around (working double jobs), they are stuck in poverty with an easy out (crime).

It saddens me to read about solving youth problems by attacking the symptoms rather than the cause. Though I understand why, fixing the cause takes time, is unpopular to those on the political right, while fixing the symptom seems can achieve immediate results (though not long term).
Something I find ironic is that Zed Shaw dislikes both haskell and lisp programmers for a variety of reasons that would only provoke if I put them here, some of which you already mentioned. Search "lisp" in second source.

[1]http://lemire.me/blog/archives/2010/05/31/computer-science-i...

[2]http://learnpythonthehardway.org/book/intro.html
They "get out on the street" by turning off their regular cab dispatch radio that they've been taking calls on and picking up the Uber phone instead.

Presto! More cars on the street!

See also: lifting yourself by your own bootstraps.
The most famous case is probably Neal Horsley, who was found liable (though only civilly) for publishing the home addresses of abortion doctors, some of whom were later harmed. He was sued for contributing to the attacks and lost. These were correct addresses and it was true that they were abortion doctors, but a court nonetheless considered their publication to constitute an implied threat of harm to the doctors in question. There are some less dramatic cases involving the "public disclosure of private facts" tort, against which truth is not a defense (though an address would not usually be considered a private fact).

In the traditional (pre-automation) era intent played a large role. This worked out okay in most cases, because harmful things (like Horsley's site) tended to only show up as a result of malevolent intent. Sites with lists of abortion doctors' home addresses didn't just show up innocently, so if nobody had malevolent intent, they wouldn't show up. Now if algorithms are just throwing up lots of things, there is probably not malevolent intent on the part of the algorithms, but the same harms can result. So different legal systems are trying to figure out what to do about it.
hey from breach.cc/hack:

The result is an executable exposing a NodeJS REPL with a special API to control browser windows and frames direclty from Javascript. Some people will note the resemblance with node-webkit. Well, the building blocks are very similar but the overall architecture is fundamentally different: here we expose the Content API into a NodeJS context to have the necesary semantics and security model to build a browser using only Javascript code. Node-webkit, on the contrary, exposes nodeJS API within the renderer of a trivial browser (one window, one webcontents view) to make it super easy to build native apps using Javascript code.
I'm wondering what do you guys find interesting in this profile?
That's not the issue. It's about whether you think that Lisp is the only objectively correct answer whenever the question arises "what language are we going to use for this?".

Willful ignorance about other languages and their features is as much a cultural failure as, the hypothecial, unwillingness to learn about Lisp.
Black males are disproportionately represented among those in poverty or with low income compared to white males. If the police completely ignored race, we would expect black males to be arrested at a higher rate than white males.

The most troubling possibility that the black male vs white male rate suggests to me is that police might not be taking black victims as seriously as white victims.

Blacks die by homicide at a rate that is around 16 times the rate whites die from homicide, for instance. I haven't analyzed this to make sure I'm not running into something like Simpson's Paradox or something similar that makes it easy to mess up when looking at cross group statistics, but my first impression is that if police were working as diligently to solve crimes against black people as they do to solve crimes against white people, they would be arresting a lot more black criminals than they do.

The female data is interesting. I don't even have a guess as to why white females might be arrested at a higher rate than black females.
> Kickstarter backers pay money in exchange for a specific product of value roughly equivalent to the amount they paid.

Then they're doing it wrong. Supporting a project on Kickstarter is a donation. A vote of confidence. That people are using it as a store and a ridiculously high-risk low-return investment vehicle is completely absurd. The blame should probably be put on Kickstarter themselves for what seems to be a major failure to establish the right expectations.
That would probably actually work pretty well. I've run into a similar problem a number of times and I may try this.

"All problems in computer science can be solved by another level of indirection" - David Wheeler

"...except for the problem of too many layers of indirection." - Kevlin Henney
I don't, but I do know that at my last job the documentation team started using it to bring writers into version control. It allowed a lot of them to grok what was happening without being scared of the command line.
I use it. My work git repo isn't github, so switching between this tool for github and cmd line for work has become part of my habit field. I still go back to cmd line for more complex stuff though.
The 'right to be forgotten' has more to do with the fact that in the past there was a barrier to entry to gain access to this information. Let's say that (e.g.) you were arrested at a peaceful protest in your teenage years. The Internet makes it easy to gain access to this information with minimal effort and/or cost. In 'the old days,' someone could find this information about you (public record and all), but they would have to be very motivated to look into it.

It's the same thing with the move from manned helicopters => unmanned drones for local law enforcement. Unmanned drones significantly lower the upper bound on what local law enforcement can do with air surveillance. Society didn't care too much about reining in local law enforcement on these issues in the past because it was too costly (to law enforcement) to be a problem to society at large.
(Biased, I work at GitHub and helped design the original GHfM)

I use it every day, almost all of the time. I don't use a lot of it, but what I do use is tremendously useful. My workflow is usually:

1. Navigate to the folder in terminal (old habit, or starting servers) and type in `github .` which launches the client for this repo.

2. Sync to pull in new changes (cmd + s)

3. Create a new branch (cmd + b)

4. Commit as I code (visual diff helps me do light code review on the spot). This is definitely the core usage for me — seeing what uncommitted changes I have, selecting out partial commits, drafting up good commit messages, amending bad commits, etc.

5. When I'm ready to publish my branch, sync again (cmd + s)

The key for me really comes down to some really simple stuff: a visual editor for creating commits, and quick keyboard commands to common actions (branching, switching branches, push/pull). It's possible to do fast in terminal, but muscle memory serves me personally much better with real keyboard commands.
still something is missing to be professional. Anyway is a lot better than other home made (:
The very second photo--the one of the stairs--I instantly wanted to re-crop. I want to crop it in a portrait format with the side walls almost if not completely removed.

I agree with the other commentors who question the decision to call these images "minimalist".
Can you note mine too?
> (two drunk people raped each other?)

Don't be silly, it's always the man's fault.
4.8% of Americans are Asian Americans, but only 1.7% of their respondents are Asian Americans or Pacific Islanders?

I wonder what went wrong with their surveying method.
The vagueness of the laws are a different problem. If the laws were just vague then you could have judges interpreting them in favor of defendants as often as prosecutors.

If you had to point to one thing as the cause of all this, it is likely to be the privatization of criminal justice. As soon as you have a private prison or a defense contractor selling military-grade equipment to civilian police forces, you create the incentive for those organizations to lobby for more "customers" through broader prohibitions, tougher enforcement and harsher penalties.
...pricing is the only real general mechanism we have to express need/desire.

There is another one, actually. It's called voting. And it's how taxi regulations came about in the first place.
> How about just sending the full object state back as the response to my PUT request?

That is what I do. I don't see anything wrong with it. PUT effectively replaces the state of the resource so you get it back right away (get the latest state, which should be what was sent in the request, minus a conflict for example if multiple clients do it or you have some incrementing revision id thing)

> For example, what if a single PUT request creates multiple sub-objects?

I'd use POST for creating/adding objects. I think of PUT usually as idempotent and as I mentioned above, use it to replace the state of the resource. So if this one POST ends up creating multiple-sub-objects you can return a json object that encapsulates URIs do those new objects.

Remember resources don't have to map to internal objects, db rows or other such things. You can have the objects or db rows represented or used in different resources. If it makes sense and if you have this transactional interface, maybe it makes sense to have an explicit transaction resource that is in charge of managing a transaction (where multiple things happen and then it kind of becomes very explicit).
I track it in the "charitable giving" section of my budget. Thinking of it as anything else just seems silly.
The answer to that depends both on your scale and also probably on the business model (ie, if you're selling a storage solution you have different needs than a dating website).

I'm intrigued by Rackspace's new OnMetal service, but at any reasonably large scale it's usually a big win to own the hardware (as long as you can afford redundancy).
Like the design and idea. It is not usable at the moment but I'd like the project to get stable and ready for day-to-day usage.
Seems to be very unstable on Yosemite Beta 2. I tried loading this thread, and it the HTML view froze immediately. I then tried to load up Reddit, and it just wouldn't load.

It's a really cool concept, though, I look forward to seeing where it goes. It would be super cool if it became stable enough to be my main browser, because I love the customizability.
What you mean to say is that Lisp is simple but not easy, but that's true of a lot of things.

You might enjoy this: http://www.infoq.com/presentations/Simple-Made-Easy
Yeah, that was a hard one. We just remembered it from yesterday.
High Tech Device Closes Medical Availability Gap for Pulmonary Monitors
There's also Zócalo Public Square[0], a "not-for-profit Ideas Exchange that blends live events and humanities journalism."

[0] http://www.zocalopublicsquare.org/
But they weren't going to pay for rack space and power. Also, IMO offering free rackspace violates net neutrality since a start up couldn't get a similar deal.
Ok, sure. We've changed it to (approximately) that.
What's the fascination?

Edit: genuinely curious
I don't get it. How in the world is that any easier than:

cd /your/src/dir
git pull

<edit stuff>

git diff

<look at stuff; possibly edit more stuff>

git commit -m "edited stuff"

<oops...forgot something; edit another file>

git commit -a --amend
git push origin

Which, of course, has the added advantage that you're using git, instead of using a GUI obfuscation layer on top of git, and therefore learning your tools.

I mean...I sort of get why people do git integration in editors (even thought it tends to lead to ignorance of git), but opening up another, non-console, non-editing app, just for git?
Only 6% of american prisons are private.
The headline made me think I was going to read something about cell phone photography, or maybe carrying around a 35mm film camera loaded with a roll of black and white film. But, instead, the word "minimalist" is being used to describe considerations you should have with every photograph you make. And the photos are not what I'd select to demonstrate the concepts described.
I disagree that the product has been unchanged for years. Their app syncs photos on my phone, the shared link gives a great preview of files (esp videos), they've got a strong API for developers and they're improving picture sharing.

These may seem like little changes to one product but they're making it a rock solid product in one vertical that is slowly creeping out into others.
Of course not. It's more like a browser shell or browser UI written in Javascript (which is still an interesting idea, but not particularly new).

A large portion of Firefox (and SeaMonkey before it) are written in JavaScript, with XUL used to do UI layout.
It is probably higher than 2.7%. The 40% statistic concerns probability of arrest, not expected number of arrests. In plain english, if a kid got arrested twice, he'd just show up once in the 40% figure.
Most definitely not quite pro. And thanks!
I'm not a web developer, but why can't you link to an anchor that is slightly below the header, so the view that the user sees is the same view (minus scrollbar position) they would have seen when they were originally on the page, and "infinite scroll" upwards when they scroll up, and down when they scroll down.

_______________
| header |
| |
| buffered |
| images up |
|-------------|
| |
| Viewport |
| |
| |
|-------------|
| buffered |
| images down |
| |
| |
---------------

Is this somehow technically very difficult or would this screw with usability in some way that would be unintuitive?
Also over 50% of violent crimes go unsolved and over 80% of property crimes. Looks like there could be more arrests if they solved more crimes.
Introducing RunAbove: a new baremetal cloud provider, cheap and powerful!
The author working for D-Wave is a very illuminating fact, given the high probability that D-Wave's products are pseudoscience.