skysight-inc/HackerNews huggingface dataset:
I think this may be an unfair metaphor, because we have a police force and laws that give us incentive to not murder our neighbours in their sleep and give us assurance that we will be protected while we sleep ourselves.

On the world scale, this doesn't exist. If there was no laws, police, or government and a serial murderer moves in beside you, you may very well try to murder him in his sleep.
You have to keep in mind that Canada has terrible population density compared to Europe/Asia. It's about the size of the US, but with 1/10th of the population.
Derek said FOOF!

http://blogs.sciencemag.org/pipeline/archives/2010/02/23/thi...
Seems pretty clear when you put it that way.
> Docker chooses to run containers without an init. The big problem here is most if not all apps you want to run in a container are not designed to work in an init less environment and require daemons, services, logging, cron and when run beyond a single host, ssh and agents.

Do this not confuse init with a process supervisor?
I'm not sure it is universally possible, because you never know where somebody might branch from.

I think checkpointing only can be effectively done with reliable consistency when you know everybody are onboard and stick to the same shared checkpoints, in your shared past (checkpoints you know they know), because otherwise they might themselves not know any checkpoint identical to one of yours when you'll merge.

It's bad in particular when you're merging files that your algorithm only can parse as bit strings, not data structures, as the entire structure can have been very drastically changed with no clear indication of what went where. If there's known structures in common, at least you can attempt some kind of logical reasoning.

Somebody forking in the middle of a full rewrite with no existing checkpoints that's coming back to a document now with a checkpoint before and after it would then have to have a history going back to the older checkpoint (the exact same version!), merge backwards, and merge then against the diffs to the new checkpoint, and forwards to the current version.

If your most similar stored versions (with diff history) of the same document in your separate histories are far apart, it WILL be painful to merge.
DNS verification is already in the ACME spec, but not yet supported by the live servers. So the answer is "soon".
I tried Inbox for about month, but I ended up turning it off.

It was slower than the standard gmail interface, both on my computer and my phone. There was a noticeable lag when trying to open each email.

Additionally, on the Android app, they inexplicably removed the ability to swipe left/right in order to move from one email thread to the next. Instead, they implemented a vertical swipe which returns the user to the inbox. So the pattern for reading a series of emails is swipe-tap-swipe-tap-swipe-tap instead of a series of swipes. Additionally the swipe only triggers if I drag my thumb vertically over about 90% of my phone screen, which is very uncomfortable.

Why mess with what works?
Very little oil is used in electricity generation, except in Hawaii and Puerto Rico.

The problem is everyone is racing to deploy renewables, driving the price of electricity down. This is good for consumers, bad for utilities. Traditional returns are going right out the window (or rather, are being transferred away from utilities to renewables manufacturers).
That thought literally (almost) keeps me up at night.
> Perhaps establishment science need to move the peer review from before publication to after.

The after publication 'peer review' is when colleagues attempt to replicate your findings. It's a series of gates to credibility and general acceptance, not a single door.
Introducing d3-shape
> 1. Well, there are people who serve web fonts and CSS sprite assets to about 10¹²³ people per hour

Those people have the problem that the delivery mechanisms are extremely limited and hardwired and a lot of the possible advances cannot be shoehorned into a DEFLATE-compatible bytestream or whatever it is IE6 supports...

> 2. "What's the incentive" is IMNSHO a terrible question for a research area.

Researchers are human too. It's demotivating to try to research fancier data compression techniques if you're certain that no one will ever use it.
It's nasty because everyone is sublimating the frustration of their autonomy. Their accumulated resentment inspires an "I'll get my turn" narrative. Eventually it's up or out. If it's up then their narrative crystalizes around an identity which is responsible for the output of their unit. They go into fearless commander mode. AKA: narcissism. Ownership sees them as obsequiously adaptable. Fuck the details. They have the best people. Trust them. Then they extract the costs from those beneath them. They just have to work 1% harder than their unit. Meanwhile work-ethic is attributed to character and not compensation. Thus, under-compensated workers can be shamed into over-working. This completes the cycle with another wave of narcissists and (d)ejected losers. Ownership promotes this because they've decided that labor is otherwise fundamentally unmotivated. They don't care about the externalities.
The Goethe Auction (2012)
Ricardo's Difficult Idea (1998)
A Practical Guide to Planning and Executing ML Projects in Industry [pdf]
Air Force cadet sentenced to 3 years after buying modafinil, molly, and LSD on SR2
I really like this one by Zack Rusin from 2007:

http://zrusin.blogspot.com/2007/09/git-cheat-sheet.html

In nice printable format with a sort of "state diagram" for commits (workspace <-> index <-> local commit <-> remote commit)
I tried to run this, and it ran so slowly that I gave up. Admittedly I have a 6 year old Mac, and while it's no speed demon it works well enough for all the tasks that make up my day, and when I bought it it was one of the fastest computers sold. It's just not cool that software, including HTML has gotten so bloated, and programmers have gotten so lazy that they feel it's more important to produce shit code fast than fast code in time it takes. I believe that quality, elegant code will save it's combined users more time by orders of magnitude than that one lazy programmer with the unreasonable deadline will save, including all the bug fixes they'll inevitable have to push out.
I think that's less about perception of time as it is cultural expectations. Plenty of people in Europe would consider a train that's 15 minutes late "late," it just happens often enough that society has to take the slop of inefficiency into account.

But, my point is that even conceding such a long view of history, the US probably didn't look more menacing than Europe. The US was a minor political and economic power, whereas Europe was much more powerful and had its own much longer history of imperialism and territorial expansion by divine right.

The implication seems like a bit of historical revisionism in hindsight, based on how threatening the US seems to a lot of people now.
Oh gosh what a cool idea, I'll definitely consider implementing something like this.
Interesting read, but there is something a little odd about an article that describes Emperor Hirohito as "merely a figurehead" but later casually mentions that Hirohito had the power to surprise General Tojo by naming him prime minister and spends a good deal of time talking about how Hirohito could have potentially prevented the war due to how much influence he had.
GCC 5.3 Released
The headline doesn't square with everything I've ever read about the attack. Embarrassment was at best a minor factor in the Japanese thinking. The major factor, IIRC, was that certain military officers -- many of them belonging to (or fearful of) a murderous ultranationalist faction -- had come to dominate the Japanese government [1]. These military men:

+ wanted to strike south to secure desperately-needed sources of oil, rubber, and other resources for their war machine (an alternative they debated was to invade Siberia);

+ felt that for a strike south to succeed, they had to neutralize both the U.S. Pacific Fleet and the American bases in the Philippines, from which the U.S. surface fleet, submarines, and air forces could have caused serious problems for Japan's maritime supply lines from Southeast Asia; and

+ perhaps most importantly, were out of their depth when it came to assessing a political risk, namely the extent to which a surprise attack would bring down on them the implacable fury of an enraged and industrially-powerful United States.

[1] https://en.wikipedia.org/wiki/Japanese_militarism
I don't know Mondragon, but from Wikipedia, they don't seem to be particularly different from the large coops I know: the majority of workers in their largest operations today are not owners but regular employees, and there is still large pay disparity (albeit smaller than elsewhere).
I don't understand the debate of the meaning of ignore vs reject.

The US made ultimatum without a specific deadline. The hawkish press spoke in behalf of the government, but without authority. The US continued its plan to attack until surrender was communicated. No doubt powerful in US govt wanted to see what the bomb could do. Dropping two a-bombs in a week wasn't an accidental race condition against communication lines. The US leadership had two bombs and wanted to use them.
Most nations have many reasons to fear their neighbors if you look far enough back.

The situation dictated policy. Either their war in China ground to a halt or they conquer SEA.
I don't think the "Manifest destiny" entered much into IJA/IJN thinking in 1941.
Shame that someone tossed out that old red rotary phone. Wasn't it Buckminster Fuller that said garbage was just an non utilized resource?
Finland Planning for National Basic Income
That's an interesting idea because right now it's somewhat non trivial to define the things and rules. If you could use a story to generate a world that would be really neat! I'll definitely add that to the TODOs.
I'm going to be a little imprecise here, but hopefully accurate:

1853: Commodore Perry shows up on the shores of Japan with shiny ships and cannons and says "You're gonna trade with the world." It worked, but Japan didn't like it. Japan spent its time buying ships from Great Britain and sending its young people to school in the United States to learn what it could about empire building.

Late 1800s: The United States, wanting to be seen as a world power, attacks and defeats the world's weakest "World Power" Spain, both in Cuba and in the Phillipines. Japan had been helping the Phillipines achieve independence and the United States basically stole the Phillipines out from under them.

Early 1900s: Japan fights and wins against Russia in the Pacific. They basically destroyed Russia at Port Arthur (using the same tactics as were used at Pearl Harbor). To retaliate the Russians had to send their Atlantic fleet the long way around the world. By then Japan had rebuilt from the battle at Port Arthur and defeated the Russians again. The lesson: Defeating a world power only requires you to be powerful within your sphere of influence.

Shortly before Pearl Harbor: U.S. cuts off oil supply to Japan. Japan needs the oil in the Phillipines and also wants to take the Phillipines back which they felt were stolen from them. Pearl Harbor was their attempt to recreate the Battle of Port Arthur and wipe out American presence in the Pacific, leaving Japan the most powerful entity in that sphere of influence.

The long view of Japan and the United States is that we kind of grew up together, but we were the bullying older brother. They grew up to emulate us and when they got big enough... they punched back.
UI sucks. This is how you do it: http://aqicn.org/city/france/limousin/limoges/aine/
Clever naming!
Study maps neural pathways in the mind of a fly
More than that, believe it or not, but synchronicity and blocking code is considered a feature: it's simple and straighforward.

Most code doesn't need to be non blocking. We only hear so much about non blocking because the Web is the big thing and Web programming benefits from it.

But there are hundreds of other fields in programming where IO is not the main issue, and hence don't need the additional complexity of being async.

Granted, asyncio does a good job at making async easier, but imperative code will always be easier to use, learn and teach. These qualities are very important, and made Python famous : easy to grow with, and yet powerful.

So the stdlib will remain as-is, the useful, easy and beautiful thing it has been.

We may see additions made to it so you can ALSO, when needed, do more stuff async. But really, I think we will see more and more external lib just doing that, so for when you DO need async, you will just pip install.

Things I do hope will have an additional async API though:

- urllib;
- sqlite3;
- subprocess.
I do my best to avoid generalisations about people, unless they consciously choose to label themselves (eg. KKK is racist, feminist is sexist, etc).

There is a difference between looking for patterns in people and stereotypes. For example, walking down a dark lane at night in Kings Cross (Australia) is dangerous with any person you meet. Seeing a black person in Pitt St is unlikely to be dangerous. A person wearing tracksuit pants and a backward cap walking in an agitated manner may represent a threat. A woman in a dress might or might not be a CEO. Now, how does a stereotype of skin colour, gender, sexuality, etc help anyone?

I agree that the US is particularly biased and that truth is the victim. I went to code.org with my young son who asked "are boys not welcome?" The link on the title page said "why girls should be in IT". Political Correctness - another word for prejudice. The idiot who approved it didn't give a crap about the message to young boys, they're just a casualty of war.
Memory overcommitment. Isn't supported for all VPS solutions.
Thank God. I can finally get started on my clone.
You seem to completely ignoring Japan's wars of invasion against China, Korea, Indochina, and basically every border other than "America" first. Or for that matter, the rest of World War II which had been going on for over a year.
It used to be possible to write Firefox extensions that used multi-threaded JS; however, like any other language, accessing the DOM was not threadsafe (so you can't have a window be your global object, and therefore they needed to live in separate source files). As JS lacked native support for threading, you also had to be very, very careful and often ended up with less obvious threading issues anyway.

In the last few years SpiderMonkey (Firefox's JS engine) has dropped support for this more and more, and these days you can't anymore. But that's a consequence of the engine implementation, and not the language.
Having to pass proper vetting as in the UK would weed out some bad apples at the start and moving to \ single police body for a state would both improve the police and remove a lot of wasted tax payers money.
I've set up a collaborative cheatsheet in github some time ago, if anyone wants to collaborate, you're more than welcome:

https://github.com/trufa/git-cheatsheet
What systemd?? OpenRC here. <:)
Running the same machine with Yosemite, no cpu upgrade but an SSD and video card upgrade. Thinking of putting new cpu's in as they are down to $35 for a pair, almost free at this point. Can't complain about the machine at all, going on 10 years now which is just awesome, and I do so love internal HD's on sleds.
Grammar is absolutely relevant in science, math and various other fields. Noone wants to have to parse ungrammatical documentation or scientific papers.

It's certainly possible to get by in STEM with poor grammar, but it is harder to excel that way. Grammar below a certain threshold impedes natural language communication, which is important even in technical fields.
There's no such thing as 'firefox alpha', its 'firefox nightly'

Kinda odd to see when they get the rest right and they're engineers. feels like they dont know firefox o.O
It works surprisingly well, but it has a very limited vertical extent (based on how wide your phone camera is) and that limits the scenes it is suited for.
WHY BOYS LIKE BAD GIRLS
The tone here is incredibly biased towards "nobody in Japan wanted war". Apparently nobody in Japan wanted war, but they somehow kept invading countries?

And the claim that "Japan had planned to declare war shortly before its planes bombed the US fleet at Pearl Harbor, but a series of errors by typists and translators prevented the Japanese embassy from giving Washington the declaration in time." is beyond absurd.
Imagine this article entitled "Women at work" and written by a man. As someone astutely wrote below, this is the female version of "manspaining."
This is a problem in all organizations, not just governments. Few things predict failure better than an environment where criticism and negative feedback are suppressed, often because it's seen as not nice, or uncivilized. I've seen startups fail because big problems were readily visible and understood by most of the staff, but people were terrified to talk about them. By the time people were aware of how widely shared the suppressed opinions had spread, the damage was done. Just this week, I talked with employees of another high profile startup that claim they are heading in the very same direction, because discussing the technical problems in their platform leads to social ostracism.

It's not as if there's only one way to et into an unsafe culture: I have seen situations where people were intimidated by using abusive, aggressive behavior, and others where the same things were accomplished through smiles and backstabbing.

If you are leading a startup and you don't see dissent in your organization, beware, because what it means is that it's been forced to go underground.

So yes, we should learn from imperial japan that every organization needs ways for people to safely and politely express unpopular, honest opinions.
You've got it.. The state help (we looked at it as well) involves making tech predictions about where your yields will be and your cost structure will be in 3-5 years... It's nearly impossible to get these projections right, and the companies are obviously optimistic so when the numbers come up short, it looks like they were lying. I highly doubt there was any actual fraud. It won't matter anyway, the whole point of running a business is to shield the investors from liability, none of our (smaller) incentives ever involved guarantees from investors.
> Did you know that even with all the advances with technology the amount of time that a housewife spends maintaining a household today is the exact same as it was in the 1950s!

Unrelated to the core of the article, I know. But it seemed odd to me. Is this true? Or was it a metaphor?

EDIT: did a bit of googling and found a couple[0][1] of not-extremely-academic references that claim that it's less than half... but couldn't find anything more authoritative.

[0] http://www.telegraph.co.uk/women/womens-life/9721147/Women-s...

[1] https://www.anglianhome.co.uk/50years
My understanding from talking to people working on MirageOS is that a lot of the unikernel users are still deploying inside containers. Just like containers aren't going to "kill" virtualization, unikernels aren't going to "kill" containers.

I'd particularly like to stress the part of the article that mentions containers that bring all of userland with them. I hope this will be fixed once people are using tools like Kubernetes and are forced to think of containers as pieces of a larger system rather than short-sightedly "porting" their applications into a container. At CoreOS, we introduced Clair[0] specifically to show people how much userland is still inside their containers and vulnernable to known CVEs. ~80% of tags (downloadable containers) on Quay.io still contain Heartbleed, for crying out loud.

[0]: https://github.com/coreos/clair
Oh absolutely, the issue is not solely store space. That's just the aspect that's most visible to me personally, since the Apple Store near me is quite small, and I'm not an employee.
So the expression "mad as a hatter"--mercury was used in part of the hat-making process.
Why do we still write insecure software?
The article appears to be of the belief that literally nothing the Japanese government could have said or done was a sign they wanted war.
Does MrDoob Approve Your Code Style?
S/4 HANA Simple Finance in Simple Terms
> And the claim that "Japan had planned to declare war shortly before its planes bombed the US fleet at Pearl Harbor, but a series of errors by typists and translators prevented the Japanese embassy from giving Washington the declaration in time." is beyond absurd.

It appears to be the truth, or pretty close to it: https://en.wikipedia.org/wiki/Attack_on_Pearl_Harbor#Japanes...
I definitely think it would be possible to create a hierarchical thing-graph from a story using some existing tools... I'm going to brainstorm and do a bit of research.

I'll have to think more about extracting rules. That could be tough.

Please keep working on this! I don't have much time on my hands, but I would love to contribute if I can.
Only because the system already allows for patents that shouldn't exist because they aren't novel enough.

See, for example:

http://www.let.rug.nl/usa/presidents/thomas-jefferson/letter...

Jefferson was clearly dead set against the situation you are describing -- granting patents with only incidental modifications to the system. But then again he would be rolling in his grave if he saw (and had the modern knowledge to understand) the completely inane, obvious (to practitioners of the art) shit we've been granting patents on since about the late 1980s.
I think that one of my father's USGS friends inadvertently got himself with some while using a pipette. It must have been thoroughly unpleasant, but the guy was alive and kicking 20 years later.
Well I think reading the book and evaluating its arguments and supporting evidence is the only way. I know that's unreasonable to expect in a forum discussion but I think it would be rather harsh to dismiss the book out of hand because of a slip-up in an interview. It's a failure of small degree, really. I've read other sociological works that talk about the skewed gender distribution in acts of mass violence in a similarly categorical way even though there are documented cases of mass violence committed by women. I think the difference between 100% and some slightly smaller proportion does not change the premises enough to invalidate the arguments.

I think toxic masculinity is under-examined and men are disadvantaged about talking about it and recasting their identities without it because, well, a lot of men in these comment trees demonstrate a resistance to entertaining the idea it seems on principle. That principle seems to be, and I have to guess here because it's usually left implicit, is that masculinity is somehow immutable, innate, apolitical and unideological, and I think that's a harmful attitude to take in the interest of society and one's own interest. It makes violence against men at the level of identity and gender unassailable, unexaminable.

But of course some guy in this comment tree found a way to blame it on feminists and women.

https://news.ycombinator.com/item?id=10683479

> And traditionally women were loath to marry down, for example, whereas for men it was pretty common. I guess to prevent mass shootings, more feminists should marry down instead of complain about male competitiveness (which is 99% driven by women's choices, as mates is part of what men compete over).

I think the reading I suggested is far more constructive than everything else being brought to the table here, really.
Could you please spellcheck your posts and your site? It kind of hurts to read.
I'm sometimes intrigued that humans have the time and energy to worry about breathing.
Well, i'll have to check if the syntax i used works under BSD sed, because that seems to differ slightly and I ran into problems in the past.