skysight-inc/HackerNews huggingface dataset:
Accepting user registrations generally entails obtaining a means of contact which can be used to unlock an account whose password has been forgotten. By far the most common contact method used is email. GP may not have mentioned it in so many words, but the implication is trivial. Requiring unique registration on a site also demonstrably results in significantly fewer people actually making use of the site. It's perceived as a burden, and people not unreasonably wonder why they have to providing sensitive information in order to find out whether there's anything there worth providing sensitive information. As ever, whether or not you think this should be true doesn't affect whether or not it is.

Too, leaving aside the question of whether it's a security risk for the user, maintaining a password database is certainly a security risk for the developer. Having your password database stolen is a credibility disaster. Similar exposure of a collection of OAuth tokens, none of which provides any access whatsoever to privileged data and all of which can be trivially deauthorized by their owners or en masse by the application developer, is about as minor a concern as any security compromise possibly can be. From the developer's perspective, that's an extremely strong argument for three-legged OAuth.

Addressing the other alternatives in detail: Using session cookies alone is great, except that they will eventually expire or be deleted, at which point all progress is lost. That's not a major problem, I suppose, but I can see people potentially being annoyed by it, especially shell cowboys who solve everything with one-liners. I'm not sure what "The site could generate a registration for the user" even means. And I think there's a fair argument to be made that authentication via OAuth with a third party hits a sweet spot between user convenience on the one hand, and persistence and distinguishability of identity on the other.

Finally, I'm really not sure why "they're tracking you!" is such a concern in this case. Yes, third-party tracking is an increasingly ubiquitous reality of life on the modern web, and yes, in many ways that is a very bad thing. On the other hand, there is such a thing as nuance, and I think it's a pretty long stretch to argue that it is likely to result in a major privacy violation to let on to Github, or for that matter Facebook or Twitter if I had accounts with them, that I'm a programmer. I suppose it's possible there are people who need to keep that a secret for some reason, although I can't imagine what reason that might be. For them, it's probably not worth it to use Advent of Code, even with a throwaway account. For me and apparently quite a lot of other people, it is. I'm having a very hard time seeing the prima facie unreasonability of that perspective that it seems like some folks do.
It's a very old idea, almost as old as the Higgs mechanism: https://en.wikipedia.org/wiki/Induced_gravity

Getting it to work is another matter, though.
The papers coming out of Microsoft Research are a goldmine (relatively speaking as far as academia goes) for programming language and graphics research, just to name a couple of areas I'm familiar with.
Your point is actually orthogonal to the OP's.

The OP was claiming that Apple's architecture is flawed and that once they realize the error of their ways, battery life will improve dramatically. That's just not true.

Your point is that the public SDK limits 3rd party developers from doing some stuff that Apple can do with the private SDK. That is, of course, absolutely true.

Letting the public SDK (or at least parts of it) lag behind the private SDK, while certainly frustrating to 3rd party developers, is the right thing to do. The situation is exactly the same on the iPhone, iPad, and Apple TV. Apple has employed that strategy from the beginning with iOS, and they believe it to be the correct strategy, so they will almost certainly stick with it.

I don't work at Apple any more (pushing toward launch on a startup!), but based on over 8 years of iOS history, I think it's safe to say that the public watch SDK will get more powerful over time, as private-only features are deemed ready to release to 3rd parties.
Recent discussion: https://news.ycombinator.com/item?id=10566776
Yeah, but it's so limited.

I really want them to add support for multi-airport "sfo, smf to hkg" and multi-city "sfo to lax to hkg" to the web search parser.

And the mobile web app is decent but compared to desktop very limited. For example, the dates grid shows just a few days vs. 7x7 for depart and return. I think that's one of the most important features. I find it frustratingly inefficient on mobile.
It's not of course that they have spare time. It's that they're forced to spend time on it because society demands continuous performance of gender and rewards highly people who do it well. It's not abstract; it's practical.
> I play video games, and I can't imagine what the latency would be like over a mesh network.

1. Neither can anyone, because we don't have examples of large-scale usage of mesh networks, and the amount of research that has gone into mesh networks is nowhere near as extensive as exists with ISPs. There's no reason to assume that mesh networks will always have higher latency, especially in places where i.e. Comcast is choking connections.

2. The small-scale mesh networks which already exist are demonstrably adequate for many, many use-cases. Mesh networks which handle text and image web browsing, email, instant messaging, are still extremely useful even if they have trouble handling streaming video and video games.
Fair point - knowing more bears the risk of mixing things up. What overall harm are you thinking of?
One of the major roles of academics is to put words and define concepts around things that already exist but that lay people do not consciously think about.

The idea of pondering the role of masculinity comes from the feelings and actions men feel and take, it doesn't define them the other way around.
Few people know that the USSR was invading Japan from the north at the time. If we had just pressed on a bit longer, the Allies would have won anyway. However, we would have had to split the spoils with the USSR. So dropping the bomb served two purposes 1) it ended the war a bit earlier so the Soviets were not needed, and 2) it sent a message to the world that we would do whatever it took (in this way it is just like the fictitious Star Wars event). Wonder why we bombed civilian targets? B/c we only had two bombs. If they didn't do the job it would have been too late (per point #1).
OpenWrt and WiFi for $12.95
World's Worst Tablet Computer Teardown
So are dlls :-)
Which is why the U.S. should have stuck with the British empire like good little drones.
>Strange thing to think. Companies do not produce browsers - employees do. In fact, not even employees. A handful of talented programmers produce browsers. All the desire in the world from a company won't improve the ability of those handful of programmers.

Strange thing to think. As if the core mission of the company, the motivations of the management, strategic decisions to hire people and structure projects etc, the funding and priority they give to specific products etc, don't determine and affect the end product!

Put that way it's as if a great browser engine can even get out of some accounting software house, if only the right programmers chance to work there.
> The Imperial Grand Moff Tarkin is no worse than Democratic President Harry S. Truman — and no one worth listening to considers Truman to be a monster.

OK. So how do we start considering Truman to be a monster? He slaughtered 129,000 people, mostly civilians, in cold blood.

The author makes a perfectly sound argument that the Empire was no worse than America, and then somehow drives that to the conclusion that the Empire was good by refusing to budge on the cultural dogma that America can only possibly be good. There's a much simpler answer here, it seems to me.
I think the contrast drawn isn't with a simple language, but with a too-simple one. As Einstein was paraphrased, "Everything should be made as simple as possible, but no simpler."
ad 1: why not attach a credibility score to relations (probably aggregated from multiple sources) and query against those too?
Well, we've got the armed part down.
Linguistic differences are a major cause of regional tensions within India.
It's obviously the primary product to ANY browser development team.

The question is if its also the primary product of the COMPANY the development team belongs.
> why the rancor and assumption that the OP and other commenters (like the GP) haven't also had physical jobs?

I'll be happy to accept evidence to the contrary, but by the looks of it the OP has not.

> I certainly have…

Good, so you'll appreciate my viewpoint a bit more than those of us who happen to have lucked out and have been desk jockeys since the start of our professional lives.

> It's all I did the first several years of my life. And like you, my life is now quite different.

My assumption is that because of having had a period in your life where you worked really hard for relatively very little pay that you appreciate what you have today a lot more than you would otherwise.

> You have a different point of view, but it's not because we haven't done physical work. In fact, in my case I'd say it was my experience doing that kind of work that leads me to identify with what the OP describes in the linked article.

I subscribe to some parts of what the article relates to but I take exception with certain parts and the casual way in which 'men without a college degree' (which the lady writing the article is not on both counts) are being labeled as implied slackers because 'We know they watch more television and do less childcare than working-class women, and are less likely than more affluent men to work long hours'.
I've seen people applying DMSO to their joints as some kind of arthritis treatment. I can only assume that what these people buy is actually massively cut with water, or they'd have already been poisoned by whatever residue was on the skin at some point.
Nothing in particular, just admitting the possibility.
Here's one way you could do the clipping generically in Go[1]. This has a Clip function that uses a type assertion. Another (perhaps better) implementation would add Clip methods to both Rect and Poly.

Either way, I don't think this example proves the necessity of generics. Some algorithms are certainly more difficult to express in Go (graph data structures/algorithms in particular in my personal experience).

[1]: https://play.golang.org/p/xYQWDS41A0
I've done both. I found manual labour hard but overall easier hours by a big margin. I have physical issues from the non-physical work and I know people who've had (true) burn-out and stress-related illness. My personal experience is that I can keep going physically when I'm exhausted but productivity drops to near zero when mentally tired. My experience is that people massively underestimate the toll of non-physical work rather than that they underestimate physical work.

I'm not understanding the level of emotion. Sorry if your friends & relatives are suffering from their jobs.
ES6 overview: iterators
Yea I mean, I wasn't disagreeing with the point that "Chrome makes them money". The huge leap in logic to "therefore, they make money by collecting data" is what I took exception to.
I have a similar view, but at the same time I still have a little bit of hope that even if the universe was a simulation, there would be some way to somehow go outside the simulation (e.g: by 'thinking', if that would make sense, about outside-the-simulation concepts; something like escaping the VM). But it's kind of an emotional reaction to the realization of the limits of one's mind/perception ;).
Here, meet a dictionary of the english language:

Literary [lemma 2]: in effect, virtually <will literally turn the world upside down to combat cruelty or injustice — Norman Cousins>

It's a use that predates Shakespeare.
How did they maintain the temperature of the LM and the astronauts suits for three days? With such extreme temperatures, that would require a lot of energy.
Reading your and similar comments made me think about it, and I came to the conclusion that the commonality between drugs and guns is superficial.

Starting with what they have in common, I would say the restriction of either creates a black market, so that either allows criminal organizations to make a profit selling them. I think there is a difference even there though, since you can argue that criminals still benefit from loosening of gun regulations, because they would have easier access to guns. The primary buyers of illegal firearms are gangs and similar organizations, so that market is mainly there to support criminals who would not be able to obtain them without it. I don't know if that would change with increased restrictions though - maybe some otherwise law-abiding people would be willing to buy illegal guns for self-defense. On the other hand, I can't see how legalizing drugs could benefit crime organizations, except that maybe they could use their existing infrastructure to pivot into a legal drug business. Maybe that is a significant boon, but it doesn't seem worse than any other "legitimate business" that funds criminal activity.

One of the main arguments in favor of drug legalization is quality control - street drugs often contain adulterants that are more debilitating than the drug itself. From what I know, this can't apply to guns since illegal guns are typically originally-legal guns from ordinary gun manufacturers, and don't have as many quality control issues.

And the way they generate harm is different too - drugs mainly harm the user, and guns mainly harm whoever the gun is used on (may sometimes be the same as the user). So drug legalization might be desirable so the harmful qualities of drugs could be reduced (as earlier), and not restricting guns could be desirable in that people will be able to defend themselves from other people with guns (criminals with guns, an oppressive government). This simplifies the issue a bit, and ignores other factors like drug research or hunting and other non-self-defense uses of guns, but I think it's clear that there is significant room to agree with restricting one but not the other.

My post may reek of bias toward drug legalization, but hopefully you agree that it's not as simple as "If you want to loosen drug/gun restrictions, you should also want to reduce gun/drug restrictions".
lol. I wish I could +1 this again.
We also bombed civilian targets because the destructive power of the bomb was still relatively unknown and Hiroshima and Nagasaki had not yet been bombed as they were non military targets. If we had bombed an area that had already been attacked it would have been more difficult to assess the damage that the bomb was capable of and those two cities were "clean slates" so to speak. I can search for citations on this if you like but it's been quite a while since I read up on this so it might require some digging through my notes.
Good. The more of this junk science gets shot down the better. Let's see more of these articles rather than the ones about miraculous new inventions to cure cancer/Alzheimers/diabetes/insert your favorite disease. The carelessness with which these findings are shot into the world and the amount of press they get before there is even a proper chance to evaluate the findings, to review the experimental setup and possible biases and to replicate the results is very annoying. Not a day goes by without an announcement of that kind, the number of times I've seen 'cure for X' in the headline of some article that then later gets retracted (usually very quietly) is depressing. Maybe I should get some deep-brain-stimulation to counteract that effect.
> Many hiring managers view that as fulfilling your initial obligations after being hired (hiring expense etc.).

Some do. I'd rather have somebody leave ASAP so I can bring somebody in that will stay, be happy, and excel at the job. Why have somebody work for 1 year just to walk away? Hiring costs are sunk; you shouldn't be computing value based on sunk costs.
Send Letters, Not Emails
TCL is dead)))
On Food and Zapping (2008)
I take you at your word that you weren't trying to make a political point, per se, nor do I mean to accuse you of that. However, my point (somewhat sarcastically made) is that your "too obvious to mention" point is necessarily a political position and statement. That outrageous rhetoric that's coming from the right is by-and-large not seen as outrageous by them; and of course their statements are completely and obviously outrageous to those that oppose them. Whether your intent is to make a political point or not, you invariably do so once you make a judgmental statement about one side or the other; even if your circle of friends finds such a fact as nothing more than a casual observation useful for demonstrating a point.

There... now we've both made non-political points by making use of inherently political statements.
You just sent me on a long detour searching for the book he references: "Ignition!: An informal history of liquid rocket propellants" by John D Clark

For any other people interested, it's out of print, but a PDF is available here: http://library.sciencemadness.org/library/books/ignition.pdf
We solve all of those use cases in our cluster management system of which Docker is a key enabling component, except for point 5, though we do have other components that require multiple steps to provision. I bet we could run Hadoop if we needed it.

It's easy to point at Docker and say it's a trivial wrapper around some technologies that have been around for years and call everyone crazy for buying into the 'Docker is going to change the (sysadmin) world' hype. Of course in essence it's pretty trivial, many things are.

Docker, and Docker-like systems really are changing the sysadmin world. Easily formalised software environments is what this hype is about, and the fact that the Docker community isn't really looking at the stateful service problem right, doesn't mean they're not enabled by Docker either.

To me, and to many 'devops' (i.e. developers rolling into sysadmin roles) Docker was eye-opening. We reduced our chef scripts by 80%, and thus our headaches by 95%. It's saving us months of ops work. If you were a seasoned sysadmin and rolling your eyes at the fact that we were rolling out application level services in the same chef codebase we were setting up our system environments with, then yeah you already were better than us. But as far as I could tell the way we used to do it really was the status quo, at least in the startup/small it business world.
I take issue with the use of past tense for the Couch ecosystem. Things in our neck of the woods indicate the hockey stick is kicking in for offline first, especially with the Internet of Things.

Example: http://www.couchbase.com/nosql-resources/presentations/offli...
> Here's one way you could do the clipping generically in Go[1]. This has a Clip function that uses a type assertion.

Well, sure. But the title of the article is "Avoiding Reflection in Go". :)
If we'd stayed with the British maybe we'd have universal healthcare already.
Wasn't it fast tracked into the release channel? That is, 38.0.5 would have been a patch release on top of 38.0.4.

On the bright side, that has lead to a more serious look at shipping parts of the browser as first-party extensions. I'm very much looking forward to that, even if I end up leaving all of them on.
Microsoft has about 120 times the number of employees that Mozilla has. That's an insane number. If they consider the browser remotely important, they can put much more resources behind it than Mozilla ever can.

Only things like the Mythical Man Month save Mozilla a bit here.
I guess I am more excited by the idea they have so many books that are not currently cataloged. There to be thousands of similar collections around the world. How much history do we miss out on simply because it now collects dust, the tech is there all we are missing is the need and money
"Those people will go to their graves, never knowing how miserable they are" :-)

See 5:30 into video (on ES6): https://www.youtube.com/watch?v=PSGEjv3Tqo0

I have been doing a fair amount of JS work in an app using Angular this year. I don't use much inheritance of any kind, mostly FP techniques and "objects" (associative arrays) as aggregates.

If you use "closure" variables instead of "this", it's pretty easy to graft functions from one aggregate to another for code reuse.
> I found manual labour hard but overall easier hours by a big margin.

The toll adds up if you do manual labor long enough. Bodies are machines and they wear out.

> I have physical issues from the non-physical work and I know people who've had (true) burn-out and stress-related illness.

Been there, done that. And these can be serious issues as well, but it's not the same as dropping dead 2 days after you finally receive your pension because your body is done with living.

> My personal experience is that I can keep going physically when I'm exhausted but productivity drops to near zero when mentally tired.

I think we all can relate to that. Which is why we - as a rule in the industry - estimate that people are productive in knowledge work for 4 to 6 hours per day.

> My experience is that people massively underestimate the toll of non-physical work rather than that they underestimate physical work.

My experience is the opposite, people find it very easy to relate to things they have personal experience with and find it hard to relate to things that happen to others.

> Sorry if your friends & relatives are suffering from their jobs.

Where did my relatives come in?
The whole point or insurance is exactly to do what you have described. To pool risk. Insurers are hoping to reduce risk to increase profit while basically destroying the concept of insurance itself.

This is exactly why insurance should by law be a non-for-profit enterprise. Making it a capitalist enterprise will always lead to these sorts of games.
Web tools club - The biggest free tools collection for the web industry
Sounds like something a monolingual would say/snark

Anecdotes are just that. I know plenty of people that can dominate two languages fluently.

Recently read a study where a stroke patient can recover faster if multilingual or that dementia can be kept at bay longer.
Many of the author's desires are handled in SmartOS (https://www.joyent.com/blog/triton-docker-and-the-best-of-al...)
Gorilla: A Fast, Scalable, In-Memory Time Series Database (Facebook)
Wonder no more. The American Sociological Association reports data from the National Science Foundation in the U.S. showing over 20 consecutive years of enrollment skewed about 2:1 in favor of women [1].

[1] http://www.asanet.org/research/stats/gender/graduate_enrollm...

BTW, this is a hell of an article. It describes an "intransigent masculinity," yet women are not supposed to let men define their femininity?

And it blames mass shootings on "masculinity." But take a look at this hocky-stick graph of the frequency of the history of mass-shootings in the U.S. [2]. There's something more than "masculinity" going on here:

[2] http://thesocietypages.org/feminist/files/2015/07/Mass-Shoot...
The cost of such a change also compares badly with being able to wrap anything you want so easily.
I’m just ‘bout that action, boss
None, One, Many – What's the Difference, Anyhow? [pdf]
Using little types is fine, but I prefer to not use them nor do I recommend them. I have dealt with several large C/C++ codebases which used them extensively. It often took too much time to find the declaration to see the real type. Then I would forget and repeat the process again and again and again. Overall they wasted more time than they saved.

Some of the fancy IDEs help with this problem, but not everyone likes using them so you can't count on that as a solution.
Well, more people flee Syria because of Assad than because of Da'esh.