skysight-inc/HackerNews huggingface dataset:
It's not even true that the US doesn't manufacture; manufacturing output (by value) is the highest it's ever been[1]; it's just that far fewer workers are employed to do so.

(Same as the pattern with farming; there's a difference between "the US doesn't produce many crops" and "the US doesn't have a big fraction of workers in farming": the former is false and the latter true.)

[1] https://fred.stlouisfed.org/series/OUTMS
Let me put it another way with a car analogy. Everyone loves car analogies.

Scenario: You want to test how far your car can go at its top speed on a full tank of gas. You're too lazy to actually sit in the car with your foot on the accelerator the entire time so you go and find a brick to lay across the pedal. Unfortunately, when you place the brick across the pedal, you accidentally, unbeknownst to you, deploy the drogue parachute[0]. You walk away, hit the remote start button in your pocket, and the car takes off. RACING RACING RACING, except, you know, parachuted. Actually you don't know. You didn't do it in purpose. You didn't know it deployed. You didn't even see it, because you were walking away. You only found out later when you got back to your car and saw, oh shit, you accidentally deployed the chute. What a boner. Why was the deploy button so close to the accelerator where a carelessly placed brick could bump into it anyway? What a stupid design mistake THAT was.

Now. Do you call your test valid?

[0] https://en.wikipedia.org/wiki/Drogue_parachute
>Aren't houses purchased for the intent of renting them out investments?

Those are investment properties which is a different thing than we are talking about. We are talking about a primary residence bought to live in.

Yes, some investments are illiquid, I have some personally, but its stupid to have your entire portfolio in illiquid assets.

>I buy plenty of VFINX that I don't intend to ever sell. I buy them for the dividends (incidentally, the same reason I would buy a house).

A house doesn't provide dividends. Unless you are talking about investment properties, which, again, isn't what we are talking about here.

>The carrying costs of a house are typically negative

Doubtful. Very, very, few people are going to spend as much on rent as they would a house. Houses have a way of eating away at your money in a way renting does not. The carrying cost of my house is certainly not negative.

Of course, "you have to live somewhere" muddles the water a little bit. But its designed to get you to think about your house as more "somewhere to live" rather than "something to build wealth."

>This is true of all investments.

Which is why we diversify, to minimize risk. The American mindset is "buy a house because your house will make you rich." So people overspend on houses neglecting any other investments or savings in the process. That's the real problem.
Using the unkeyed initializer syntax is discouraged anyhow: https://golang.org/cmd/vet/#hdr-Unkeyed_composite_literals

Unkeyed syntax also doesn't work for a struct in another package with at least one private field.

One common exception is a vector type that isn't expected to change--RGBA, XYZ, LatLon, etc.
> We can also implement a policy that any software developer who writes a bug gets a $100 fine, that should teach them!

I seriously doubt that this would help to reduce the bug rate. But let us for now assume that it really did reduce the error rate.

First: What does one consider as a bug? The interface of typical functions is not well-specified. So let's create a function that creates a C# IList from passed parameters. Now consider that IList<T>.Count returns an int. What is supposed to happen if the list that is generated will have more than Int.MaxValue elements? Is the not-consideration of this a bug in the code or something that a caller of this function should never do?

So one consequence would be that we additionally define a contract of pre and post invariants for each function so that it becomes clear whether something is a bug in the function or a bug of the user of the function.

Of course we would have to do the same for all libraries that we use, implying that we can hardly use any available library (at least not until libraries also begin to implement such a strict policy). So a lot more code to write.

I don't want to begin to talk about bugs in parts of the stack one has no control over (e.g. OS, compiler, browser) and code whose whole purpose is to circumvent these bugs one has no control over (how do you even detect in this kind of code parts what is to be considered as a "100$ bug"?).

Nearly every programmer will say: "if I really have to deliver such a low error rate because otherwise I lose money, at least I have to be allowed to use methods that enable generation of code with an error rate that is so low that it is affordable for me to submit to a 100$ per bug policy". So at least being allowed to create a giant test suite for the code or even better being allowed to use mathematical methods of formal verification.

So we get code with indeed an extraordinarily low bug rate - but on a pace that is so slow that few companies can afford it.

TLDR: Things that one would have to do to even implement such a policy would increase the quality of the code a lot. I personally believe if these were implemented a 100$ per bug policy would not be necessary anymore because the bug rate becomes so small. On the other hand these actions would increase the development time by a lot - thus increase the cost by a lot. So except for, say, software from avionics, medical devices or military this is probably not affordable.
Edit: nevermind
> He looks like a fool, but he's _wailing_ on the left.

In the real world, he secured less votes of actual people than the opponent to the left, and now is polling worse than recent past Presidents-elect, of either party (overall, among his own party, and among the opposing party and independents.)

Trump certainly leveraged anti-democratic factors in the electoral system for electoral success, but the idea that he is having unusual (or even usual) levels of rhetorical success against his ideological opponents (much less "wailing on" them) is at odds with the facts.
You've got good points, and you're right that I didn't explain "master of words" well.

I think that most people are about as bad with listening comprehension as they are in reading comprehension. It's why in ToastMasters you're told to structure your speech in the format of "Tell the audience what you're about to tell them. Tell them it. And then tell them what you just told them." The amount of _time_ he spends on a topic just shows that he's thinking about and that it's important to him. He's conveying that he cares and he takes it seriously. He's not trying to explain tactics or be especially witty.

And this is a style that we're not used it! Which is why it took everyone off-guard, and made people who are "classically" good-with-words underestimate him. But who knows, maybe this is just 20/20 hindsight.
The patch version is there for very minor things. Adding docs, adding tests, changing metadata, _maybe_ minor bug fixes. Hopefully no one has to depend on a patch version, and hopefully they're usually ".0". I've seen arguments that patch versions should go away, but revving minor versions for some things is often too much churn - people try to understand what's in the new release when it's not even worth their time.

Minor versions are things you reasonably might depend on like a new feature or significant bug fix. You _should_ be able to upgrade seamlessly though one person's bug fix is another's breaking change. I don't think it's reasonable to get rid of these and treat everything as a breaking change.

So I don't know what's simpler for libraries. Semver seems to have boiled it down pretty well.
It doesn't work that way. You reach out to funds, work the circuit, etc. Any investment requires time from both parties, and it takes weeks to close a transaction. Thiel-affiliated funds are automatically off my list. We've had a few cold outreach investors contact us, but not many. Most are referral-based.

Funds live and die on dealflow. There's a limited amount of time to talk to investors, so you have to prioritize. Funds that are de-prioritized don't get the opportunity.

In other words, I won't ever have to decide whether my convictions are that strong, because that scenario wouldn't happen. Ask an investor for their perspective, though. I'm sure it will corroborate my experience.
Not gonna speculate on the future, but for some historical perspective:

Behaviorly modern humans: ~60k years

Anatomically modern humans: ~200k years

Divergence from apes: ~6M years ago

Mammals: ~200M+ years

Dinosaurs: ~165M years

Dragonflies: ~325M+ years

Source: http://waitbutwhy.com/2013/08/putting-time-in-perspective.ht...
arXiv: https://arxiv.org/pdf/1606.08795.pdf

By the way, this group achieved ground-state cooling of a very similar mechanical oscillator back in 2011.

"Sideband cooling of micromechanical motion to the
quantum ground state" http://www.nature.com/nature/journal/v475/n7356/abs/nature10... arXiv: https://arxiv.org/abs/1103.2144

Both oscillators were of roughly the same frequency (10 MHz) and size (~15 nm diameter aluminum disc). In terms of phonon occupation number, things improved from 0.34 to 0.19.

They emphasize in this new paper that they were able to get colder by using a squeezed vacuum state of laser light. I'm no expert, but I think the use of this technique is much more important than the improvement in the mechanical state they were able to achieve.
I've been to Israel many times including during the time of the first Gaza conflict (Cast Lead).

There were elections in 2006 and Hamas was elected over Fatah. Hamas does not recognize Israel and is declared a terrorist state by the US, EU as well as Israel.

There were supposed to be elections in 2010 but Hamas will not allow them.

Hamas has spent large sums of money shooting missiles into Israel and using concrete meant for building homes and schools for and hiring labor for building tunnels into Israel. So serious was the missile problem that Israel created the Iron Dome missile system (see youtube or CBS 60 minutes) to protect its population. That technology is now being co-produced with a US arms manufacturer for sale to other countries. The Israelis have also had to develop tunnel locating technology.

While Israel has a program of encouraging venture capital and startups, it is truly a pity that the Palestinians did not elect Fatah over Hamas.
Yea this site is fantastic. I just discovered the site because of two threads that made it to the front of HN today. I've already spent a couple hours reading all the other articles, I think I'll likely become a member
If you define your config to be:

some-library>=1.0.0,<2.0.0

and your application breaks - then some-library's developer isn't following SemVer anyways, and you are in dependency hell. If some-library's developer doesn't care about compatibility, then it doesn't matter what versioning scheme you use as you will have to whip up that secret sauce anyways.

However, that your issue isn't a problem with SemVer, but a problem with NPM/node. SemVer is working as intended, but getting the "secret sauce" to get everything working can be confusing as you try and figure out the differences between "devDependencies" and "peerDependencies". If every module just managed their dependencies, it could be easier (on your development experience, but not on your hard disk and build times).
I agree with you but not till the headsets get lighter. I don't think I want to wear that thing for even a few hours a day when all I'm doing is email and coding.
Sounds like an excellent argument for not using node
>> somehow different from everything just being synchronous and using threads
> It IS different. In async code every single line of code must be async

I think you misread the gp. He was not saying that Go code is not different from async code (what you understood), he said it's not different from synchronous code using threads.
The problem is that the major web server apache has basically a broken ocsp stapling implementation. It does a bunch of unexpected things and you'll likely not want to enforce stapling with it.
This list makes no sense. Expected better from a site that's focused on tech stacks.
Actually, it's more rational to turn to crime than work a shitty minimum wage job in an economically disadvantaged area. That's why those areas have crime.

The choices are simple.

Work at McDonalds/Walmart

Max weekly earnings: ~$420 assuming CA minimum wage and a 40 hour workweek

Smuggle cocaine from Mexico to USA

85k - 200k per run depending on quantity.
Semantic versioning works great for software like Java. When you deliver an application with java, you want to ensure that the vast majority of your users have a compatible Java version. You also want to make sure that a new version of Java doesn't break your software. Semver encodes both these properties. Since the first number in Java's semantic version is always one, you know it is always backwards compatible. Whenever the second number increments, you know new features have been added that require a new VM. The last number changing is mostly irrelevant to most people, but it might signify a bug fix or optimization.

When both those pieces of information - backwards compatibility and the need to upgrade - are important, semantic versioning should be used. If you are comfortable removing features without leaving an out for users, and you can reliably upgrade all users at the same time, encoding this information is much less important.
> find anyone that most people who posit a monolithic "left" are typically consuming a strange brew

s/left/right. Is there any difference in how each perceives the other?

Is the assumption that any member of "the right" voted for Trump and believe what he espouses any more fair than the assumption that "the left" is anti-science, based only on the beliefs of a subset?

People and their beliefs are complex. We do each other a disservice when we make assumptions based on our own lack of understanding and willingness to actually learn about each other.
I think you're asking the right questions. I don't know how society dealt with these actions before the Internet, but I suspect the scale of the problem wasn't the same before the Internet. It probably wasn't so easy before to distribute morally-bankrupt content without catching the attention of law enforcement.

The long term solution has to revolve around education and re-examining societal values (the darker side of human behaviour has its roots in more socially accepted forms of human activity). The short to medium term solution is to target those producing and consuming the content, but this is fraught with its own difficulties. In any case, targetted surveillance and streamlining the related court cases is something we should probably be doing more of for now.
I'll just leave this here:

http://fair.org/take-action/action-alerts/why-were-governmen...
On top of that, I think a large crux of the suit here is mostly due to the fact that Microsoft refused to shell out for treatment after the fact, despite doing so for other departments with similar jobs. While the plaintiffs do seem to have a problem with how they were hired, the actual suit seems to be solely based on the fact that their compensation did not cover any medical expenses they have incurred due to their work related trauma with a token clause about warning people properly.
the wars in the North Caucasus, Georgia, Ukraine and Syria.

North Caucasus -- CIA trained terrorist "wanted" independence, been cutting Russian soldiers necks and film it. (its a typical form of report CIA uses)

Georgia -- CIA puppet Mikheil Saakashvili made a coup, attacked Ossetia with tanks, they were killing civillians. Russia saved Ossetians, and now that scumbag is considered a criminal in his own homeland.

Ukraine -- CIA controlled coup that was done in violation of the Ukraines constitution, Petro Poroshenko is a new CIA puppet. Mikheil Saakashvili is now a governor in the Ukraine city Odessa (wow, such surprise)

Syria -- US.

the enormous plunder of Russia's natural resources and the corruption/bribery of democratic governments.

Yes, exactly what happened when CIA controlled puppet Gorbatchev sellout USSR. Putin fixed it. (the best way possible in 17 years.)

the sponsoring of hateful ideologies and their export across the world.

CIA created Osama bin Laden and other terrorists. You need to learn, now figure out which country is a true sponsor.

the unscrupulous sale of weapons to warlords and dictators across the developing world

Exactly what US is doing, that's why there is still no order in Syria.

the war on truth - CNN and Co

the killing and intimidation of journalists - biased mass media propaganda sources.

the fake news on Russian channels - you starting to fall to the total bullshit here, oh well. (total == 100%, nice propaganda meme)

the spread of FUD on western media - CNN told you that RT is bad? Poor guy.

even the wave of Internet trolls. - I would call you one of them, but how is Russia related to that?

On the Russian side your have Putin and his vertical of power - every organization has a vertical of power.

I also don't understand the point - is any of these things I listed OK because the "US" does them - you listed lies, the guy mentioned US because of context.
If you're only seeing emotional manipulation from the left, you're only seeing half the story.
Relativity has almost no effect on GPS at it's worse it would have an accuracy degradation of less than 1cm, there are considerably bigger sources of errors in GPS than relativity and various corrections to those.
Shadows, echoes, atmospheric effects and the doppler effect have considerable effect on GPS accuracy, relativity will not.
It's not just P2P-CDNs it's all live streaming video, HLS and MPEG-DASH. Open source tools for these technologies are sparse.

Even good HTML5 players that match YouTube's feature set are few and far between.

Bitorrent Live is excellent btw. One of the best performing video apps on iOS.
> I wanted something agent-less [...]

Sorry to break it to you, but you have an agent anyway, except it's the same
fragile channel for debugging, administrative access, and running scripts, so
once you start to need to configure it, you can break all the things at the
same time.

Oh, and you just dropped proper configuration management. Now you need to add
a task queue (another thing that can break and overflow and what not) to
re-send configuration commands when some server is down, which would not be
a problem in the first place with appropriate architecture of the system.
> you have absolutely no idea what secret sauce is necessary to get a working application again

That's what .lock files are for.
Tangentially relatedly, this recent r/haskell thread [1] contains a lot of discussion on the differences between Haskell's Package Versioning Policy and SemVer, and particularly downsides of SemVer.

[1] https://www.reddit.com/r/haskell/comments/5iok3l/haskell_pac...
I don't know if this is true or not but...
I've heard that they limit the amount of time that you are allowed to serve on the "child services" team for some police departments. The idea is that, no matter how well adjusted you are, this messes with your head, and causes you to lose your cool. Anyone in a position to validate this?
My issue isn't necessarily with the fact that it's in English. It's that it's hopelessly imprecise English. Maybe you'd have less of an issue with the Java Language Spec? (Which, IIRC, even left out some memory model problems until recently.)
Apple never achieve a dominant market share position, but they have always maintained a dominant profit share position.

We haven't witnessed the end of Apple's golden era, we've witnessed the end of the smart-phone adoption curve. Everyone who has ever wanted a smart phone has got one. Or two. Or probably three or four by now. They're buying fewer phones because the differences from one generation to the next are more incremental.

If there's a fundamental shift in how phones are used that demands a new kind of hardware or some kind of vastly more powerful software there will be an impetus to upgrade again. Until then it's more steady-state.

There's still tons of opportunity to innovate in the watch space, and the tablet market, while having cooled off, might continue to nibble away at notebook sales.

We're in a bit of a lull technology wise. Consoles, phones, laptops, they're all "good enough" for now.
Or some people are very sensitive to the (white?) noise that noise that NC headphones still generate.
A very insightful (but needless rude) comment from a user called Memetic:

"No sh*t, it's called gentrification and has been around forever. Thanks for reinventing the wheel."
IME this problem is particular to NPM, due to JavaScript's historically-anemic standard library which made a culture of microlibraries inevitable. The lesson is that programming languages should provide rich operations on their standard types so that users can avoid having to transitively depend on ten different versions of left-pad.
That speaks more to the insanity of the Node ecosystem than anything else.
It wouldn't be the same. I could never match her savagery and gusto.

The more basic point is -- if I were running a major newspaper, I wouldn't invite fascist collaborators to do innocent puff pieces in the Fashion & Style section, or any other section of my paper to begin with. Other than as a ruse to lure them into a well-deserved public grilling, that is.
NIST CSRC Post-Quantum Cryptography Project
Well, since that time, we've moved away from slavery to labor saving machines.

Since we're at a point where many people are under-employed, and we expect many more to become so, we can probably re-institute something like this.

After all, the United States was a crazy experiment to revive 2,000-year-old Greek idea called 'Democracy'. While we did have slaves at the beginning, we have managed to enfranchise all adults politically. Maybe the Ecclesia could work, too.
So it has about 10 rust files so far?
>You can't compare fear of heights to watching child porn, murder, rape, and other horrific crimes all day

I wasn't. My point was that this can't exactly have been a surprise. It's a little like me (being afraid of heights) signing up for skyscraper cleaning and then somehow being surprised when I don't cope.

This job is going to involve review of horrible scaring stuff...it says so on the tin.

>MS should have provided support knowing what this role entails, they didn't. So here is the suit.

Oh yeah definitely. I realise that & said so...and you even quoted me saying so...???
Does cost matter? Tentatively, there may be a compelling case for jail time for something like this. "Intent to cause harm" isn't necessarily physical harm. The concept of legal assault is one that could be useful.

Though it opens up a very slippery slope, and I would hope it would have damn high standards for proving malicious intent.
US government: Help us protect computers from quantum hacking
This is punishingly stupid. If you are working on a large enough project (many libraries, many developers, many organizations, daily or nightly builds because it takes 4 hours to run all the unit tests even in parallel due to dependencies) you use semantic versioning.

If you're some pissant shop writing CRUD apps then yeah, don't bother. As soon as you outgrow that stage, there won't be any more questions.

Monolithic standalone apps or tiny projects don't need semver. Practically all collaborative software in between benefits massively from it.
Check your info again. It indeed seems to be statement balance from what I've gathered. though I quickly looked around on my phone.
This is very cool. Saves me a lot of time. Are you planning to support the Google Assistant as well?
Discussion: https://news.ycombinator.com/item?id=13375350