skysight-inc/HackerNews huggingface dataset:
To get to the "does it work" or "is it worth it" questions one has to first determine what it actually does, what effects the drug has on the human body. For that you want to start with a neutral test subject.

As others have said, many drug studies are looking for a degree of effect, whether the drug out performs some other drug already in use. For such comparisons you need a baseline effect. The US population's drug consumption, while certainly the eventual market, is a shifting target. If you want a common baseline for comparisons, the easiest is a drug-free test subject.

Also, drugs are tested on groups but administered to individuals. A prescribing doc needs to know the effect absent any other drug interactions. Having a patient stop taking other drugs is always an option. So you need an understanding of how the drug operates under ideal conditions and in the presence of other drugs. Prescriptions remain an individualised medical choice.
The runtime system's memory manager could automatically hash-cons equal compound values, reducing their memory footprint. It's like the flyweight pattern, except the runtime system gives it to you for free.
Interestingly enough, I think you missed one of the more important points by focusing only on the stop signs. Red lights can't be red lights to everyone in a lot of places simply by the nature of their construction. It's why the dead red laws exist, and it's that very often red lights were constructed with solely cars in mind and have sensors that cannot detect bikers that signal a request to the light for a change. While this isn't the case at all lights, it highlights the fact that there are clear differences in the classes of vehicles and that the control structures on the roads were designed with cars in mind, not bikes. These laws are simply attempts to rectify this in light of an increasing interest in bikes as a transportation method.
Never heard of the linear search with a sentinel value so needed to look it up. Here is a link in case anyone wants to learn what it is:

http://www.delorie.com/gnu/docs/avl/libavl_26.html
I believe FB also suggests based on location. If both were connected to FB on their phones when meeting in person, the location metadata is used.
Not sure about the legalities of a right to privacy in public spaces, although perhaps I could have used the word unobserved instead of the word private. For me the idea of observation goes hand in hand with the idea of self censure.
" We don't know who will be in command next."
Thats the real issue. Drone armies is every dictator's wet dream, an unstoppable mass-produced force.
You could argue the VCs in fact gave other people's money - investors money, possibly including your pension - to Uber.
In residential areas in the US, I think stop signs are sometimes used as a means to slow people down.
Can you blame them? Trump backer, vampire, "I-don't-like-this-publication-so-lets-kill-it", "competition-is-for-chumps", "lets-create-a-state-in-international-waters-so-we-can-do-whatever" Thiel is just a toxic character these days.
Ask HN: Paid alternatives to WhatsApp
Do y'all know of a paid cross platform messaging service that respects user privacy in everyday, and not do creepy stuff?
"paid" because I'd like them to stay in business.
"She is a nurse" is also not a bias. It's a prior and a valid one - the system will be right 93% of the time.

http://work.chron.com/gender-equality-issues-nursing-careers...

A bias would be if it incorrectly weighted "JOHN" and "nurse", and used the feminine for "John the nurse".
Facebook is becoming what Yahoo was in the early days.
A central webpage where you can find a lot of content and where you go to see what's new in the world. The real homepage of the internet.
Entitled startup founders and indulgent VCs = disaster
> Meaningfully doing it by being obtuse and smug...

I don't think I was being obtuse. I just expected (in the statistical sense of the term “expectation”) the reaction I got, and decided that it don't mind it.
I mean, I'll agree, if you insist on trying to create an abstraction to understand git, you can beat your head against the wall for days trying to figure out how it works. On the other hand, if you just take a couple hours to really try to understand what it's doing and why it's not that hard, and it's way more effective and powerful than any other tool out there. Personally I like tools that are powerful and efficient once learned over tools that I can use without any learning.

Note that I never said git is easy to learn, just that once you take the time to understand it, it's actually quite natural and intuitive.

That article you linked is clearly from someone who liked how simple subversion was and is annoyed that git requires more than 15 minutes to learn. But there's a reason almost no one is using subversion anymore.
I think Chris Rock explains this best: https://www.youtube.com/watch?v=f3PJF0YE-x4
t. nsa malware developer
It will - Nexus Launcher will be Nexus only, Allo and Duo preinstalled, new Google Now.
It seems that you're really saying that your values are immutable.

For the rest of us, it seems we follow the line of thinking that, if our mental model (or "struct", if you will) has values (or types with fields/properties, if you will), that our mental model can be changed to reflect lessons learned (or, our values are inherently mutable, if you will).
The point made here seems to be that often, these native data structures are dicts and lists, because that is JSON. Meanwhile, you'd often want something else when looking at only the internals.
It's not as simple as that. The market becomes more efficient as the volume goes up. The simple example is uberPOOL. Many driver subsidies kick in only when a driver does not earn enough.
> All you need to do is use the `is` operator to see how even tuples (named or otherwise) are objects, not values.

That is not language feature of Python but an implementation detail. Python implementations are permitted (but not required) to intern any immutable value (which tuples, contrary to your description, are), and "is" is a mechanism for revealing what the implementation has done.

You seem to be equivocating between talk of values as a logical thing (where Python absolutely has compound values, including tuples) and as an implementation feature (where individual Python implementations may or may not implement certain logical values through interning.)
That's called dictature. Everybody wants it, but what we get is compromise (democracy) that tries to make happy the whole society (obviously it fails in some places, that are the rules of the game). Think of it as a free-market in economics, but including privacy, freedom, etc. besides money.

Every action I take matters. It just seems that most people prefer a short-cut.

What's strange to me is when people like richard stallman stay loyal to their principles and fight for a better society they get criticized by the same people they want to help!

TL;DR; it may seem that we all want privacy, freedom, etc. but don't want to fight for it.
Just see how that worked out for No Man's Sky...
I was just quoting the cited PDF ("the section cited above shows..."), which the author(s) did on Ivy Bridge.

I haven't benchmarked it myself. It would be interesting to see how the most common cores today do on this...
Vaguely remember seeing that extension. I did not know it ships with Hg now! Awesome! More reasons to stick with hg longer for my company :)
Automated serialization is the devil. Gson and Jackson require you to write EJB-style objects to get automatic serialization - default constructors, with getters and setters for each field - to achieve automatic serialization.

The problem with this approach is that you've completely abdicated the power of the type system to ensure that your objects are valid. What happens if a field is missing from the JSON? Well, that field just becomes null. So now you have one of two options:

1) Write highly defensive code with null-checks everywhere. This is a pain to write, a pain to read, and almost impossible to get right and actually prevent null pointer exceptions. This is a nightmare. Switching to a null-safe language like Kotlin doesn't really help you beyond making sure that you actually code in all the null checks - the code is still ugly and a pain to maintain.

2) Call a (potentially) expensive verification method at the beginning of each method call for your object. This is less error prone than having null checks everywhere, but it's not much of an improvement. Because verification happens not at object creation time but rather when it's used, you'll find yourself with a verification exception at the entrance to some business logic where the JSON was passed to your system a week ago, immediately stored in a schema-less ORM, retrieved now, so you kind of have an idea that you have some client which didn't populate the field, but you have no idea which of the many, myriad versions of the client is responsible. So now you're fucked, and you're doubly fucked if you're losing data because of it.

Or you could just take advantage of type safety and write immutable object factories which refuse to instantiate invalid objects. Then you can write clean code using objects which you know must be valid because of type system guarantees. Libraries like immutables.github.io make this a piece of cake.
DOX THE NSA. CYBER WAR NOW.
I second this! The ability to easily create intersection types would be awesome!
Yah, most of the descriptions (just a little extra decode, aka PowerPC AS), and sharing the hardware actually apply to the iSeries, which _IS_ POWER based. But of course that is a minicomputer not a maninframe...

It seems the vast majority of people who consider themselves knowledgeable about computers are just massively ignorant/confused by IBM's product lines and capabilities (and don't even get me started about the nonstop and openvms). Which is a bit of a shame, particularly in the case of IBM i, which is probably one of the most interesting OS's still in support/production.
It's not that simple. Say you just bought an antique record player on ebay for $600. Say fedex lost it. Want them to just give you $30 for the price of the wood and metal?

The value of something is more than just the sum of the raw materials. What you're describing is literally how art works. If you pay for the insurance according to a $1 mill item, then you should get your money. There should be other ways of protecting against fraud.
That syntax is too heavyweight (IMO). AFAICT, most of the time, when people use inheritance, they don't want to define perfect subtypes. They just want to reuse as much already implemented behavior as possible.
What's worse is having a boss that's a pushover in one direction. From above, it's always whatever upper management wants, and to his team, it's do it now or you're fired.
"... Oftentimes, they don't trigger traffic lights to change, because many run on inductive sensors buried in the road (the reason for all the "Dead Red" laws in the map above)."

This drove me crazy when I lived in Seattle. Many of their lights would never turn. So I would have to get off my bike, walk over and press the button. Now that I live in NYC, Idaho stops are the norm where nearly everybody, including the casual cyclist does it and tickets are few and far between, it not only takes my commute from 15 minutes to (literally) 4 minutes, but I feel safer because I'll usually leave a huge pile of traffic behind me with a clear road around me for blocks since they stop at every light and I don't.

Of course, NYC has a 25mph city-wide speed limit, so that helps dramatically.

I think the most important thing here is being obsessive about looking for cars and yielding appropriately. If you fail to do that and are a daredevil who just blindly runs out into traffic, which I see fairly regularly, you are putting your life at risk and potentially others around you as well.

Edit: Looks like Seattle just passed a dead-red law last year! Now if they would just classify electric skateboards as bicycles like California did, that would be spectacular.
> The ability to sell portions of your right to justice is both an important freedom and a check on the ability of those with power to trample on those without.

How? If everyone has equal access to justice and the justice system, there is no need to "sell portions of your right to justice".
While I would expect we will see every bank releasing APIs sooner or later (http://www.theregister.co.uk/2016/02/10/consumer_trust_centr... shows the UK heading this way already), you may find it easier to work through an aggregator (plaid, yodlee, quovo, etc) initially for consumer-facing experiences.

Other commenters point out that some US banks have shared some early APIs, but most are not for public consumption and are limited to "partners". I suspect we'll see some restrictions on API access for a while still while regulators and banks get comfortable with an API approach.

Citi has had a Mobile Challenge for a few years with some API test access (http://www.citimobilechallenge.com/), and the Open Bank Project has a sandbox (https://openbankproject.com/) for their version of banking APIs.

But for now, unless you want to leverage aggregators, I think you'll need to just keep reaching out to the banks to be included as a "partner" and try to get early access, or wait til they open broadly, and I wouldn't expect to see that til the next few years for most large banks.
Am I alone in liking Peter Thiel? None of what he's done, including the blood, seems particularly wrong to me. With the exception of supporting Trump. But I think he supports Trump because he feels influence on the man is underpriced considering his 20% chance of winning, rather than any love of his policies.
> iOS Keeps trying to autocorrect dcma to scam.

Perhaps that's because the acronym is "DMCA", from "Digital Millennium Copyright Act".
FB is constantly popping up a message to me saying, "Is (xxx) xxx-xxxx your phone number? Confirm it now to secure your account" despite the fact that I have never given them my phone #, nor ever used Whatsapp. I'm sure they know perfectly well it's you, they just aren't (for whatever reason) doing anything about it yet.
What about the fish's excuse?
Chatbots are the future of computing
> Drivers might be angrily remembering the last biker they saw flout the law, wondering when traffic police will finally crack down and assign some tickets.

How about the laws where drivers have to maintain a minimum distance from cyclists? If I ever see that law enforced, I might start giving a shit about other traffic laws. Running lights allows me to get a head start on traffic and hopefully get to the next light/stop sign before drivers try to murder me by passing within inches so they can stop 100 feet away a few seconds sooner.
Correct me if I'm wrong, but my understanding is that companies maintain patchsets that they periodically update to apply to newer mainline versions. A lot of it ends up merged into mainline eventually. They're not really forks.
I don't think that Google Glass strictly needs to be considered body-interfacing to the degree that it's failure presents real hazards to the person, but what it does allow us to trivially bring a screen with data into not just day to day lives, but literally everything.

I think right now lots of people are trying to boil the ocean and try to make AR truly part of our bodies, when really there's a huge amount of low hanging fruit in simply getting information to be ever-present and available.

Flicking your eyes up is a good first step. Later, overlaying the same information into our field of view. Later still, integration of that data into the body, rather than just presentation of it to the physical senses.
You can hide online. I'm more worried about offline abuse (losing job, being persecuted, being beaten, etc.).

Yes online harassment is a BIG problem but forcing to reveal your identity may not be the best solution.
Mutable objects are totally fine. They're just not values.
JSON is a serialization format that was based on the data structure notation for Javascript. It is, however, a serialization format. Javascript objects are a superset of JSON, as they can contain arbitrary objects and functions, which JSON can not, and "true" Javascript object notation can elide quote marks or use apostrophes for keys, whereas JSON strictly specifies double-quotes around keys.

The problem that arises in Python and other dynamically-typed languages is that there exists a default deserialization that is so good it very strongly tempts the programmer to use that exclusively. However, as good as the default serialization may be, it's also quite dangerous, for the reasons you mention and more. In strongly-typed languages there's a stronger focus on parsing the JSON instead, which has the advantage of producing objects with stronger guarantees (which isn't quite the same as pointing out there's stronger typing here, you could theoretically get the same guarantees in Python with some sort of JSON schema library or something), but has the disadvantage of generally being more challenging, since it's hard to beat the conciseness of "json.loads(s)" in Python. There generally is a default serialization in strongly-typed languages, but it's far more likely to become inconvenient if you need anything beyond simple numbers and strings, and people generally learn to prefer true deserialization in my experience, unless they, alas, start their program out from day 1 inputting and outputting JSON and accidentally structure their entire program around the default JSON structures and end up with the exact same problems as you'd get in Python. But as long as JSON isn't the very first thing to go in you're generally in better shape.

(I have witnessed a Java program primarily written as a map of string to map of string to map of string to string. It was unsalvagable. And for all the cynicism I may occasionally muster, I don't say that often, because refactoring can be pretty powerful in Java, but this was beyond help. It actually had no JSON in site, but the same fundamental forces were in play.)

Personally, despite preferring the more strongly typed approach in most ways, I must confess that when I'm working in Perl I am generally unable to resist the temptation to just JSON::XS::decode_json, and cover over the differences with unit testing rather than dealing with "true" deserialization. I make myself feel better by also telling myself that if I do anything else, I will confuse my fellow programmers who don't generally expect to see fancy deserialization routines when dealing with JSON, which is true enough, but in my heart I still know guilt.
While driving & cycling, I observed that most cars here in Quebec pass through stops at speeds ranging from 15 to 30 km/h by doing what we call an american-stop in Quebec-slang ("stop américain"). I suppose this also happens in the US.

In a car, 15-30 km/h feels like you are really close to be completely stopped. It turns out that these speeds are pretty much the average cyclist speed range. (Cyclists may appear to go faster because they are smaller, just like trains look like they are slower than they really are).

I guess most frustrated car drivers don't realize they are also "breaking the law" at stops. I can only recommend they start cycling, the endorphins would calm them.
The three messages you give above are perfectly good members of a cleaned-up history. Each has a clear meaning, and small is good when it comes time do bisect.

Messages like "stuff", "it works", "xxx" and "everything I did last month" are not so good, but very common. Moreover if you are in the habit of avoiding them -- that is having each commit do one thing with a clear intension -- then you will keep finding times when you wish you had done something differently an hour ago. And then `rebase -i` is you friend.
If you are granted restricted stock subject to vesting, in the US you owe taxes only when the stock is both released AND vested, meaning the tax bill comes due in stages as the shares vest, not "right away". If you give restricted shares that vest over time and are only released upon a change in control, you can further defer the tax bill due date (though at the expense of the eventual bill being higher on average).
There are no examples. Social/price dumping is the big boogie man here in Europe used to regulate, tax, sue or just plain forbid foreign companies from competing aggressively against local companies. Branding the permanent menace of social/price dumping is just cronyism and protectionism in disguise, it hurts customers, innovation and employment. I hate it when populists and even regular politicians uses it and I hate it even more when people buy it, really makes me cringe but there's nothing I can do I guess.
Would Lulsec in its prime have been willing to piss off the equation group? To me the answer is clearly yes.
That's fair, I guess it's not really a different class but a different shade of the same thing.
> That is not language feature of Python but an implementation detail.

So you're saying that the behavior of the `is` operator is implementation-defined?

> values as a logical thing (where Python absolutely has compound values, including tuples)

The (informal, unspecified) metalanguage that you're using to reason about Python programs has compound values. Python itself doesn't.
I'm all for acceptable public transportation to be the norm, but until then cars work fine. Roads also weren't originally built for bikes. I actually don't know how many of the bigger cities look now, and I imagine most of them have bike lanes, but places like where I live have bikers just taking the right lane because there's no extra space. There also isn't enough space to expand the road to make room for both of us. Ultimately they're a huge hazard because they're difficult to see and hear. I really don't think they should ever mix cars and bikes. Or at least not in high capacity areas. Also you're desire to exercise is completely your own, I'm glad you enjoy it, but it's a personal choice.
The standard Win32 theme is the classic, an engineering marvel. Everything else that came after that - starting with the infamous native Windows XP theme - was and is a horrible mess.
Have you no honor or sense of duty then? What the hell is money anyways? Will your wife or husband really care if you make a dollar more or a million more? Will your true friends give a damn if you treat them to dinner every night and not be allowed to return the favor? What does your daughter mind if the book you read her before bed is engraved with gold? Does the extravagance of your son's wedding make any difference in his love for you? What a shallow life you must live if all you can think of is money. I'll grant, giving those dollars to the poor is a noble deed, but where did they come from, at what cost? Raise the taxes, encourage your representatives and senators to give much more to the poor and none of us have to pay for it with our souls.
No it is a reason to change
It's only a good thing when it's done with an agenda you agree with and not when it's equally available to others?
Imagine this being used on homosexuals in the middle east. Or imagine it being used on the modern day equivalents who most view similar to how homosexuals are viewed in the middle east. To take away the ability to pass is extremely dangerous for at risk minorities.

And everyone should fear because such tech could also be abused to falsely accuse you of being in some hated group. Police lie about drugs often enough to be a threat to liberty; they need less tools they can lie about, not more.
> While I fully understand the technical background to what exporting such data would enable those acting in bad faith to the letter of the license, whats happened here is that 1) emacs users didn't get better highlighting 2) kdevelop never had a chance to even consider gcc as a result and 3) gcc is now failing to compete with another compiler that it really needs to.

Yes, that is not the most beautiful moment in the libre software movement. I'm pretty sad about it.