skysight-inc/HackerNews huggingface dataset:
Why bother investing time and resources in Google techs when they keep on discontinuing them? they don't care about enterprise software, if they did, they wouldn't act like that. AMP? lol, think again before implementing this, it will not be worth the effort since Chrome will eventually drop that too.

A good reminder not to invest in any Google specific technology.

> We recognize that technology migrations can be challenging.

You recognize you wasted a lot of people's time.
I'm running btrfs in production with a very heavy workload with millions of files and all sorts of different access patterns. Regular deduplication runs, too. We're probably one of the largest btrfs users.

Had a LOT of unplanned downtime due to various issues with older kernel versions, but 4.10+ has been solid so far. You definitely need operational tooling (monitoring, maintenance like balance) and a good understanding of the internals (what happens when you run our of metadata space etc.).

Happy to answer questions!

On a related note: Never ever use the ext4 to btrfs conversion tool! It's horribly broken and causes issues weeks later.
https://en.wikipedia.org/wiki/Contingent_fee
Khorgos: The New Silk Road's Central Station Comes to Life
Also this one, below the definition of `nonet()` :)

> to obtain the desider result

Awesome post!
This is set similar to an idea I had been working on recently nice
That's literally what the article is claiming though. If you limit the statement to just the title here, it's not an article, it's just a headline, and headlines are not there to tell you the entire story.
Part of the problem for Uber is that, as is standard in acquisitions, Uber commissioned a due diligence report to try to determine the odds there was stolen IP involved when they were thinking of buying Levandowski's company.

Now that ought to be evidence that Uber could use in its defense. Instead, Uber is going to extrordinary lengths to try to keep it out of the trial.
https://nodejs.org/api/util.html#util_util_promisify_origina...
Ahahahahahahahahahahahahaha <takes a deep breath>. Ahahahahahahahahahahahah <wipes away a tear> http://lmgtfy.com/?q=nobel+prize+winning+physicians
$0, any direct fee is a barrier to a free and open process. And the local and state government already uses taxes collected to fund polling places and mail in ballots.
>request = util.promisify('superagent')

I don't think that's required. Superagent already returns promises.
the article headline kinda belies a bias before you even read it
Projection is often the source of hate.
I couldn't buy a Telsa for the total spent for my '03 Camry, currently pushing 380K miles, including fuel costs.

In the 12 years I've had it I've put on 350,000 miles. Even at a conservative 25 mpg and a generous average fuel cost of $3 that's:

$15,000 in car.
$42,000 in gas.

This excludes maintenance etc, but I fail to see how I'm saving money buying an electric car unless I'm already rocking solar.

Maybe it's cheaper by the mile but my assumption is any fuel savings will be quickly erased in additional insurance costs.
I think that's what parent commenter was implying.

(However, I don't agree. I remember the horrible Java applets and I am thankful that I pretty much never encounter any of them these days.)
And I'm sure Netscape is far from alone in that category ;-)

But (disclaimer) as someone who as advocated for big-bang-rewrite's before, I'm still under the impression that there are situations where they can be net-better.

Factors may include:

- there is no database involved, just code. Even more helpful if the existing code is "pure".

- a single developer can hold the functionality in their head.

- there are few bugs-as-features, tricky edge cases that must be backwards-compatibility, etc.

- as stated above, it's the primary author.

- much of the existing functionality is poor, and the path for building, launching, and shifting to a "replacement product" is relatively clear.

Advocating to never rewrite can be harmful, and make things harder for people for whom that actually would be the best approach.
WebAssembly is a medium for ASM.js apps, and ASM.js apps are mainly C and C++ . You have to learn C and C++ period.
We're a fan of CCC - they're one of the main resources we've drawn upon, and we agree with many of these recommendations under the heading of global health.

However, they focus on what will most help the global poor in the near term. We're interested in considering the full range of issues, especially those that are important from the perspective of the long-term future (for reasons explained in the article).
CVE-2017-1000367 in Sudo's get_process_ttyname() for Linux
Yep, consider x86_64. That's an AMD instruction set but it's very safe to say that Intel at the moment has won the desktop CPU market.
> Yet I'd be very hard-pressed to tell you how exactly CPU instructions work, and have never touched anything "closer to the metal" than C. Should this disqualify me from the profession?

No - it shouldn't. I feel that you should want to know this level and more about the internals (and history) of computers. I'm biased in that has been a driver for me personally...

...but to give you a hint:

A CPU (in the most basic sense) is nothing more than a very fast and very complex player piano, regulated by a clock. At each "tick" of that clock a row of "holes" (bits) representing a variety of information (address, data, instruction) is presented to the CPU. These bits are actually voltage levels. The CPU uses these voltage levels to change the state of logic gates in the system (which are wired for a variety of different tasks - but you only need one particular kind of gate to make any others - a NAND or NOR), which determine what happens, what to do next, etc.

I won't go further - and let me be clear that what I wrote above is nowhere near complete, and only describes the most basic level of an "ideal" CPU (or ALU or whatever) - because in the real world, you have things like voltage transients, timing issues (signals not arriving at the same times - hence things like wait states and such), noise, plus things like triggering on rising or falling edges of clock signals, multiple clocks staggered in time (for multiple triggerings per "cycle"), and a whole host of other things.

Yeah - it's pretty complex. But at the heart of it, it is pretty simple - a player piano, more or less, with a music reel spinning at mind-boggling speeds. If you need or want more information, there are (like everything else) plenty of resources on the internet about how all this stuff works. Check out some of the sites on people who have built computers from relays or logic gates; they typically have a lot of good information about the lower level stuff. Also look into some of the old books on building computers, and how they work (I'm talking the practical computing books from the 1950s and 1960s - difficult to find at times, check on used books online, in stores, plus on google books and archive.org; also, old back issues of Byte Magazine from the 70s and 80s are a good resource).
Escape3 – HTML5 game made in Construct 3
The way we regulate in a lot of Europe, may hit some issues as more electrics go on the road. Petrol taxes are a pretty important revenue source. Exempting electrics from that (by default) and all the other taxes help make them viable will eventually result in a meaningful revenue loss. It's also problematic to selectively benefit people who buy new cars and can afford to pay more upfront but less in running costs.

We'll have to tax them eventually.
The Preliminary Injunction order from earlier this month basically agreed with you and said many of Waymo's trade secret claims are probably overbroad and won't hold up.

But, the court said, it looks very much like Levandowski did take Waymo's files and use them at Uber, and the files "likely contain at least some trade secrets." So, basically, even if these are weak trade secrets claims and there aren't that many secrets, Uber and Levandowski have looked so bad on the question of whether they stole them that the Court was willing to say "fire him or else."

Here is that order if you're interested: https://www.plainsite.org/dockets/download.html?id=244394038... See pages 11-17.
'electric cars aren’t going to take over' there seem to be endless articles on line pro and con electric vehicles http://www.businessinsider.com/why-morgan-stanley-wrong-abou...
And that the floods lasted exactly 420 seconds and 666 seconds, those script kiddies are pretty creative when choosing numbers.
I left a sysadmin role to become a land surveyor and GPS/GIS technician. Loved the job but then in 2008 the commercial real estate market tanked, and took surveying down with it. So I went back into "IT", but instead of going back to sysadmin I started working in web dev.
Mixed-reality to prevent injuries and save lives
Wittgenstein's "problem on the irreducibility of rules" is brainfart at best. Any rule that can be actually _followed_ cannot be logically precise, and vice-versa. If you try to reduce anything from the real-world to pure logic you'll surely end up crazy.
A bunch of functions in core return multiple things to callback. A lot more in userland do the same. Spec or not, that is still something that needs to be accounted for.
I don't know if Underwood Dudley ever put it online, but at one point he did publish his collection under the title "The Trisectors" (978-0883855140). For every single failed trisection he provides a diagram, a brief description of the construction, and a measure of the error.
More info on the pros and cons of water:

http://www.copenhagenconsensus.com/publication/post-2015-con...

http://blog.givewell.org/2016/05/03/reservations-water-quali...
From what I have read elsewhere, he already has quite a lot of wealth. So "not going to the pokey" probably has a lot higher value than whatever millions he is leaving behind.
And stable on BSD. That's the crucial part for me.
Well, the calculation I made is to put 150% of my highest most recent daily usage - i.e., commute + pickup kids + store + random errand. Combined with wear/tear range reduction, I add a buffer of 50% so reduce advertise range by 1/3 for "usable range". So 200km*1/3 is somewhere around my comfortable range.

That might be higher for other folks...
It's an early prototype, stay tuned!
My general impression from playing a bit of Rugby and watching a fair but, with no statistical analysis at all..

I would say the most common injuries by far are related to muscle strains, tendons and ligaments etc like you could see in any sport. Cuts to the head are fairly common, as are the fabulous 'cauliflower ears' caused from bleeding inside your ear. But this is from being squashed and abraded, not hit. I haven't watched too much American football, but it seems a lot more stop-start, with considerably more changing of players. In Rugby you are running around for 80 minutes, so more athletic injuries rather than collision related. Perhaps having to pace yourself also lessens the hits? Spinal injuries seem very rare, and are much more likely due to some kind of contortion rather than impact.

Concussion does happen, but normally seems to be an accidental clash of heads or falling on a knee, perhaps. When it happened to me it was a result of me running to join a ruck (think lots of people pushing each other over a ball on the the floor after a player has been tackled), which kind of split in half and someones head slipped through to catch me in the face. In the top level, if the referee sees you suffer a head injury or get knocked out you are sent off to see the doctor for 10 minutes. If he suspects concussion you wont play again for two weeks. A Welsh international (George North, Wales is Rugby mad btw) got a concussion on his return from a concussion break and this resulted in him spending the best part of a year out of the game!

I don't think head on head hits are common at all. When you tackle in Rugby you have to attempt to wrap your arms around the player, and tackles are much more 'tacklers shoulder to midriff or legs'. I think being winded or hurting your stomach muscles is most likely. you certainly cannot tackle above shoulder high. Re: protective equipment, I wore non at all. Gum shields are common, as is electrical tape around your ears and some petroleum jelly on your eye-brows! Now a number of players where a 'scrum-cap' which is a close fitting lightly padded cloth device to help stop cuts and abrasion to your head. Professional players often wear a kind of shoulder pad designed to protect your collar bone, but it barely makes a dent in your shirt it is so small!
Well, I can't speak for anyone else, but - and I've said this before on HN, actually, to no more effect than I expect it to have this time - I voted for Trump precisely in order to scare the everloving bejesus out of the US progressive left. Because, from where I sit, either that happens, or something a hell of a lot worse.

Because if you guys don't get your shit together and start looking after even those people who don't agree with your politics, and believe things you think are contemptible, and live lives that you don't understand and don't want to - we're going to end up seeing the kind of enormities which will make history forget Hitler's genocide, just as Hitler made history forget what the Turks did to the Armenians.

A nation which once sought to be - which once was - a bastion of hope for a better world, a beacon for downtrodden people the world over, will instead collapse into the kind of ruin that poisons the world for decades to follow, that taints the very ideas in which it originated. Every hope that anyone has ever invested in this nation - uncounted millions of immigrants, including your ancestors and mine - will become worth less than nothing.

Also, you and everyone you care about will almost certainly suffer and die, and just as likely so will I and everyone I care about, and so will more millions than in any such atrocity before, because - as with so many things - every time we go this route of horror, we get that much better at it. So there's that.

Maybe I sound like I'm scared shitless. If so, it's only because I am, all the time now. If you're not, why in God's name aren't you? Because we're both sitting on the same pile of sweating dynamite and gunpowder. If it goes off, I doubt either of us will find much consolation in the fact that the other one's also just been blown sky high. I'm not asking for a bomb squad to swoop in and save us all like something out of the last act of an episode of 24. It's just that I sure think it'd be nice if people would stop playing with all these goddam matches and do something constructive for a change.
A depressed aristocrat finds himself yanked back from the US by his Marxist government and his friend asks her husband, the foreign minister, to let him go to Paris so he won't be depressed and he can write poetry? And he gets the Nobel Prize? The humanities are truly for the rich.
No, it means I think a human mathematician is capable of working within a formal structure by following the rules of that formalism. It's a way of saying that humans can do formal math.

Of course you are correct in suspecting I do assume the human mind is a machine, because we have seen zero evidence that it's not the case, but that's not in any way part of the sentence you quoted.
I don't see why they can't. Google spent 100,000 man hours studying why good teams are good teams.
I think for software companies to comply with the EU ruling they would need to have a mechanism for transferring registration keys from one user to another. After the original buyer transfers their key to a buyer on the secondary market, the original buyer would no longer have access to the software.

It's been awhile since I read that Oracle v UsedSoft ruling, but I think that the new owner is entitled to whatever updates are offered. If they were paid updates, (like upgrading from v7 to v8 for $20) the new owner would still have to pay the upgrade fee, of course. But if they were free updates, then they would be free to new owner just as they would be to the original owner.

From a software seller's perspective, I don't see the issue with this. If you sell one license of your software to a user, you have accepted that one user will consume one license of your software. If that license gets transferred to a different user then the original user has relinquished their license, which has resulted, still, in only one license getting consumed by one user. When you sold the software you committed to updating that one license of software that you sold, what does it matter who is using and getting the update for that single license? (Of course you don't have to give free updates to any users whether they bought your software on the secondary market or directly from the software developer.)

If you look at ProTools, they actually let user transfer licenses between each other. The licenses are stored on an iLok and users can transfer keys between one another. It's great because users can sell used audio plugins for protools or the actual protools software itself to each other. https://www.ilok.com/#!home
There's also real research progress being made. Here are some of the issues people are working on:

https://arxiv.org/abs/1606.06565
> but a party to a civil suit pleading the fifth can have that held against them

Isn't that untrue in California?
Being constantly under the gun is not healthy. Continuously working harder to compensate for understaffing is not healthy. But, on occasion, for sprints, overwork can compensate and allow you to get to your (immediate, intermediate, etc.) goals. Balance, or rather, knowing the limits of this option are key. One can't just give up when misfortune springs up, but also one can't keep on compensating indefinitely.
> first order logic is so powerful that it lets you describe everything you can in principle perform with a computer

Not quite sure what you're referring to here, but induction schemata seem to be a notable exception. There's a reason higher-order logic is often preferred for software verification.

I guess FOL is adequate if you're allowed to have an infinite number of axioms, but that doesn't seem very satisfying (pun intended).
Couldn't you say the same about JSX?
There really isn't a tradeoff.

Bad security: App requests all your contacts and shows you a list of people you can invite to play Candy Crush. The user clicks one, but the app already has access to all of them.

Good security: App requests a contact and the OS shows you a list of people you can invite to play Candy Crush. The user clicks one and the OS gives that contact info to the app.

The user experience is quite similar, but the security design is far better.
You've always been able to use real sockets on ChromeOS with plain JavaScript, no NaCl/wasm necessary.

https://developer.chrome.com/apps/sockets_tcp
Note that I said "I've tried explaining WHY", not "I've tried explaining what a TCP/IP stack is".

The explaining "why" in and of itself isn't particularly hard - refactoring and development tooling will speed up development in the future and reduce bugs. It's getting it prioritized that's hard - and that's because the business case of 'potentially reducing the likelihood of bugs in the future' and 'a story 3 months from now might take 3 days instead of 2' isn't a particularly compelling one - not because it's not important - but because it's not visceral and concrete enough.

In practice I've seen what this does. The process of introducing transaction costs (having to 'sell' the case of refactoring code is exactly that) simply stops it from happening.

If, as a business, you want to introduce this transaction code into your development process you will end up paying more dearly for it in the long run as you deal with the effects of compounding technical debt.
I couldn't be the only one worried about an "I Am Legend" type problem with this stuff. Obviously, that movie is an extreme, but the underlying problem of unintended mutation exists.
You can use .map to call await on every element in the array, or define a new function so you don't have to write that all the time:

const awaitAll = (futures) => futures.map(f => await f);

edit: this is wrong but I can't delete it. Haven't used async as much as promises.
We used to say that the fastest way to get a good answer is to post a wrong assertion on Usenet.
I've learned an enormous amount from fixing terrible bugs in terrible code.

One tip is that when you've finally found the actual line(s) with the bug, always try to understand why the programmer made that mistake.

This has taught me much about what constructs are error prone.
Nope, tech columnists pre-Mossberg were largely targeted at enthusiasts, he basically invented the everyman tech columnist gig.

https://daringfireball.net/linked/2017/04/12/mossberg-cjr
The down vote behavior is interesting. I simply mention that Intel has an early release of a previously constructed part. Monopolies behave in predictable ways.
I have a coworker who describes everything in a very anthropomorphic and casual way, and their code is excessively imperative: everything is accomplished through conditionals rather than by designing the code in such a way that functions only run on data structures that they support.

I would share this with him, but I imagine it would go completely over his head.

> The implied abstraction, in which time has disappeared from the picture, is however beyond the computing scientist imbued with the operational approach that the anthropomorphic metaphor induces. In a very real and tragic sense he has a mental block: his anthropomorphic thinking erects an insurmountable barrier between him and the only effective way in which his work can be done well.
Please stop talking about "valid contract" or "consideration" here. The EULA almost certainly contains a provision on mandatory binding arbitration.

The validity of the contract may be ignored.

Under "BUCKEYE CHECK CASHING, INC. v. JOHN CARDEGNA, ET AL." and "Rent-A-Center West v. Jackson" mandatory binding arbitration overrides a challenge to the validity of the contract. The arbiter will decide if the contract is valid.

Under "Hall Street Associates, L.L.C. v. Mattel, Inc." the arbiters "manifest disregard of the law" is not enough to overturn an arbitration award against you.

So, no, a valid contract is not required, so long as an otherwise invalid contract contains an mandatory arbitration provision, the "contract" will be decoded by mandatory binding arbitration. If you are a human vs a corporation, your win rate is 0.2% in the national arbitration forum.

A purchase is not required to be locked into a mandatory binding arbitration agreement, because a whether you'd made a purchase would be part of the validity of the contract.
We're going to work on the causes that we think our most pressing, so to be consistent, we're going to end up recommending the same things we work on.

At 80,000 Hours, our focus is also not on giving money. We're trying to help people find jobs in these areas, often in academia or policy and many other sectors.
Yes, that may be true but who cares. If you follow the news in any way you will read his twits. This is one case where even one follower means the whole world reads his message.

He doesn't even need twitter. He could just write a microblog on whitehouse.gov and that would be enough.
Who the fuck writes a fully costed business case on whether or not to spend a day setting up a CI server?

I'm trying to get some fucking work done, not convince investors I need a series A.
> digitally immortalizing his youth

I'm probably too socially awkward to understand this obsession with documenting ones offspring in minute detail. but then I have zero interest in having kids.
Don't you need to be in an async context to call await?
Disposal costs will likely be higher for electric cars. Huge battery packs with lots of lead-acid and/or lithium inside.

Seems like a good externalized cost to target.
Build numbers, internal accounting process, engineering.

Semver, outsiders view, marketing.

Two different things, conflating them causes heartache. Keep them separate.