skysight-inc/HackerNews huggingface dataset:
> Pretty sure the fatality rate is based on the number of patients who present themselves to a doctor.

In an ideal world that would be true, however we know that in early Wuhan they were mostly only testing people who were already hospitalized with "pneumonia symptoms" due to having limited kits and staff. Pneumonia symptoms how the most serious cases advance after going through flu symptoms. I read one analysis of the Wuhan data that showed 91% of everyone they tested had pneumonia. This changed later but a lot of the stats we're looking at are from papers with data only through the end of Jan.

Almost every country has different criteria for testing a patient and you can't become a "case" until you have a positive test. The U.S. has changed testing policy three times in the last week.
Launch: “The Precipice: Existential Risk and the Future of Humanity” by Toby Ord
Bugs are not enjoyable. Squashing them is.
It's charged per-cluster. GKE encouraged (and was great for) running multiple clusters for all kinds of isolation and security reasons.

This cost increases rapidly for those scenarios.
Have you had look at DGraph?

Supports the kind of queries you're looking for: full text, kv/etc. Appropriately indexed cols will automatically have things like stemming, stop word removal, large variety of language support, etc

Definitely primary db capable. Apart from Neo4J it seems to be the only graph-database I've found that _actually_ uses graph data structures as opposed to putting a graph query language over the top of a relational database.

It's open source core (enterprise/paid for is hosting and a couple of extra features).

Deployment is super straightforward: comes with pre-built containers, just deploy them anywhere you run containers, or you can also just deploy the single binary. They also, super-handily provide a whole bunch of tools for deploying it in other ways (docker compose files, Terraform files, single and HA mode Kubernetes deployment yamls, etc).
I have to disagree. This is an improvement, but it still leaves Kotlin behind where languages like OCaml were 20+ years ago, because nullable types don't compose the way you'd expect. (If you write generic code that uses T?, your code will break when T is itself a nullable type).

> • Pleasant, concise syntax for handling optionality. Not bolted on with an option type.

Optionality is not special enough to be worth a special case in the type system, IMO. Maybe some syntactic sugar could be worthwhile, but not a magic type that behaves differently from other types (which is what Kotlin's ? is) - you need it to behave like a normal type so that you can write and reuse generic code. Arrow-kt can't implement functions that work with nullable values, and has to implement its own Option type instead.

> • Highly efficient translation to machine code. No boxing, no unnecessary branching in the unwrap/!! case.

Getting the semantics right is the important thing; it doesn't matter how fast the code runs if it's broken. It's still possible to compile a well-behaved option type into something unboxed in the cases where it can be represented that way (look at what Rust does, where the option is "packed" if 0 is not a valid value for the inner type, but still does the right thing for Option<Option<T>>, Option<Int> and so on).
That's assuming that there is anything going on on master at all. A gitflow master doesn't really count as a branch of it's just a permanent alias for the latest mainline release tag.
I can't tell whether you're being serious or sarcastic, but in case it's the former Google has proposed doing this (https://blog.chromium.org/search/label/manifest%20v3) and it's been very unpopular here.

(Disclosure: I work for Google, speaking only for myself)
Gadgets that refuse to die
>If you have a constraint that forces you to have multiple versions in development and maintenance simultaneously then Gitflow works well.

Because of the way App Store approval works, and the fact that it can take weeks from initial submission to full rollout, and that many users never upgrade their versions, strongly implies that using something like gitflow would work well for teams delivering appstore binaries.
Correct. Note that there were multiple waves of the Spanish Flu. First wave was fairly mild and hit the young and elderly. Second wave hit the middle aged and wiped out a chunk of the population.

The third wave was slightly worse than the first but much less deadly than the second - I couldn't find much detail about it when I last tried.

Several theories on why it turned out this way, none of them relevant to the current situation though.
International Business Machines

General Electric

General Motors

Advanced Micro Devices

To be fair, all were among the first companies to make the thing they are named for.
Continuous deployment triggered by a merge into develop is basically a degenerate case of gitflow where there is an automated release associated with every merge into develop.

So if you are doing full gitflow or if you are doing this degenerate case of gitflow you still shouldn't be getting merge conflicts when releasing develop (merging develop into master). This should basically be a fast-forward with perhaps a merge commit for record keeping. The only way to get conflicts in this case is if there is some other process that is changing master independent of the "releases" from develop.

In gitflow those other changes are managed through the hotfix branching rules, which ensures that you resolve the conflict when you close the hotfix and back merge it into develop.
The root of this problem is that copyright lawsuits in the US are solely handled in federal court, and it typically costs $100k+ to pursue this kind of lawsuit. As a result of this there are significant penalties for infringement, with statutory damages of up to $30k per work infringed, and up to $150k for willful infringement. This means that maintaining safe harbor protections is essential, and a platform has no choice but to err on the side of caution because of the damages at stake. If there was a small claims court, or some other venue where copyright cases could be heard the law around statutory damages could be changed, and it would be less risky for platforms to decide in favor of content creators more often.
Q&A on Covid-19 from WHO
Arguing about definitions is old and boring. https://en.m.wikipedia.org/wiki/Type_system
MS Paint Quick comparison

https://i.imgur.com/tGda2X9.jpg
IF we can't send kids into coal mines the economy will collapse.
> a social app that blurs your friends posts when you haven’t talked to them in real life for a few weeks

How will the app know that?
Corellium installs Android on older jailbreaked iPhone
Cartographers Have Been Hiding Covert Illustrations Inside Official Maps
Using the infection rate on a cruise ship (pretty close to a perfect petri dish) is not at all representative.
If Putin really wants to know what kind of core memory the F-15 uses, and it's still a highly classified state secret, he could just ask Trump to tell him.
"Indian being a nanny state is an understatement"

To a non-Indian who's never been there, that sounds odd, because "nanny" implies to me a level of control that I didn't think existed.
Ask HN: The Best Discovered Podcast in 2020?
Which podcast that you discovered in 2020 has the best signal vs. noise ratio?
you are not wrong..
However we have lost a lot of such knowledge from the vagaries of the Space programs, civilian nuclear reactors, Tech in many ways far more important. It seems wrong tanks and nuclear subs should get better treatment than space.
Well, General Electric predates many of the Supreme Court rulings that establish American trademark law.

https://en.wikipedia.org/wiki/List_of_United_States_Supreme_...
You meant the pictures right? Sorry for the bad experience. Will definitely improve our color palette for future posts.
DGraph is perfectly capable of doing these with a query language extremely similar to GraphQL (and as of v2 will natively support GraphQL):

https://docs.dgraph.io/master/query-language/#k-shortest-pat...
We use a rebase heavy workflow and I love it.
What, where is the source for that? I've read "2x" and "3x" but never "tens of times".
Good to know. Cypher is quite popular indeed.
I believe OP is referring to hauling lumber on unpaved roads ("forest tracks"), which is likely a very difficult task.
"It is a well-accepted fact that demonetization was a sham at best, a scam at worst."

Are you speaking as someone who experienced it firsthand and still lives there?
MetalLB looks fun, hadn't seen that one.

If you want something production-grade (i.e. doesn't say "beta" on the tin) then I think Calico should solve most of the same problems too (it does BGP peering to your ToR switch):

https://docs.projectcalico.org/networking/determine-best-net...

Does MetalLB do something extra I'm missing?
What a great title! Also, that Great Tit photo definitely reminds me of those old "Big Game Hunter" portraits.
I'm being serious. It's been a long time since I've developed a Chrome extension so I don't follow them, but it seems to be me that is a good start but there are many areas where Chrome (and other browsers) could go even more fine-grained.

I'm not sure why it's unpopular here (perhaps its implementation vs concept?), but it seems to me that with the realities of malware constantly being distributed through extensions in addition to the obvious privacy issues, that many reasonable people would wish to see this evolution.

Personally I use almost zero browser extensions because of these issues.
Thanks for the edits (and acknowledging our contributions). I wasn't sure if you were just trolling or not before, so I didn't want to engage.

Your concern is valid, and I agree with you that OKD is not supported enough. I have my own theories as to why, but I will keep my criticism "in the family" (but do know there are people that want to see OKD be a first-class citizen, and know we are falling short right now). We had some challenges supporting OKD 4.x because the masters in 4.x now require Red Hat CoreOS (and nodes it is highly recommended), but RHCOS was not yet freely available. This is obvoiusly a big problem. Now that Fedora CoreOS is out, there is a freely distributable host OS on which to build OKD, so it will be better supported and usable. FWIW I have a personal goal to have a production-ish OKD cluster running for myself by end of the year.

I'll admit I am a little offended at being called a "proprietary IBM K8s distribution," but I don't think you meant to be offensive. IBM has nothing to do with OpenShift, beyond the fact that they are becoming customers of it. Every bit of our OpenShift code is open source and available. You are right that it's not in a production-usable state (although there are people using it) but it's a lot better than you'll get from other vendors. We are at least trying to get it to a usable state, unlike many of them. We are strapped for resources like everyone else, and K8s runs a mile a minute and requires significant effort to stay ahead). This space is still really young and really hot, and I am confident we'll get the open source in a good, usable, state, much like Fedora and CentOS are. I also don't think OpenShift is really all that expensive considering the enormous value it provides. The value really does shine at scale, and may not be there for smaller shops.

I don't blame you for waiting, I probably would too. Our current offering is made for enterprise scale, so isn't tailored to everyone. I've heard OpenShift online has gotten better, but haven't tried it myself. Eventually I plan to run all my personal apps on OKD (I have maybe a dozen, mostly with the only users being me and my family), but until then I've been using podman pods with systemd, which will be trivial to port to OKD once it's in a good state.
And what exactly would a human driver do in this case? More than likely the company policy is already "do nothing, insurance will cover it".
Worst case, take a photo of your screen with another phone. The harder it is to scrape the content, the more vulnerable the content posted there will be, which will make it that much more desirable a target to scrape.
Namespaces handle most of these issues. A NetworkPolicy can prevent pods within a namespace from initiating or receiving connections from other namespaces, forcing all traffic through an egress gateway (which can have a well-known IP address, but you probably want mTLS which the ingress gateway on the other side can validate; Istio automates this and I believe comes set up for free in GKE.) Namespaces also isolate pods from the control plane; just run the pod with a service account that is missing the permissions that worry you, or prevent communication with the API server.

GKE has the ability to run pods with gVisor, which prevents the pod from communicating with the host kernel, even maliciously. (I think they call these sandboxes.)

The only reason to use multiple clusters is if you want CPU isolation without the drawbacks of cgroups limits (i.e., awful 99%-ile latency when an app is being throttled), or you suspect bugs in the Linux kernel, gVisor, or the CNI. (Remember that you're in the cloud, and someone can easily have a hypervisor 0-day, and then you have no isolation from untrusted workloads.)

Cluster-scoped (non-namespaced) resources are also a problem, though not too prevalent.

Overall, the biggest problem I see with using multiple clusters is that you end up wasting a lot of resources because you can't pack pods as efficiently.
Yeah -- as a result of them all being quarantined on the ship together for nearly a month.
I would love if this happened in the real world, but for every well-architected automated cluster management setup I’ve seen using Terraform, Ansible, or even shell scripts and bubble gum, there are five that were hand-configured in the console and poorly (or not at all) documented, and might not be able to re-create without a substantial multi-day effort.
The most basic example of the problem with null is: if you call Map.get(key) and get null back, you don't know whether that means the map doesn't contain a mapping for key, or it contains a mapping from key to null. Optional lets you solve this: if we added a Map.getOption(key) that returns an Optional then it will be None if the map doesn't contain a mapping for key, and Some(null) if the map contains a mapping from key to null. That way you don't have to rewrite the whole world to use optionals before you start getting the benefit: even if the code that's populating the map doesn't know about optional and is still using null, you've still solved your problem.

Instead, with the implementation that we got in Java, if you tried to write this Map.getOption then if your map was ever used with old code that used nulls then it would break. So there's no way to ever start migrating to using options.

There are other problems with null, but they mostly boil down to the same issue: different code uses null to represent two different things, and so gets confused about what it means. (The other problem is that you can't look at a value and know that it can't be null, but optional definitely can't solve that until the whole ecosystem migrates to it).
Microsoft recommends WA and CA employees work from home
Just got notice from Microsoft HR that we're to work from home when possible due to COVID-19, through 3/25.

Edit: official announcement https://news.microsoft.com/2020/03/04/kurt-delbenes-march-4-guidance-to-king-county-employees/
> what's the point of beating around the bush and inventing that one of the marks of employment is a "sometimes-lousy arrangement"?

I don't think anyone seeks to apply such a test; the lousiness of the arrangement is incidental. I had attempted to argue that the mere fact that workers knowingly take a questionable or even bad deal does not mean they are contractors. The legal status of employee vs. contractor does not hinge on that.
Full transparency, I'm neither of those things. I'm saying this out of nothing but my user experience.
> I don’t think GCP is fully aware of their position in the market as the second, inferior choice.

That's because they are aware of their position as a distant fourth place. They just (well last quarter) allocated an additional $2 billion to try and get a foothold in the enterprise, shook up the management team, and is on a spending spree as well.

Because google search is so shitty I couldn't find the $2B announcement (though it was on HN at the time) but here's a recent article on the general subject https://www.fool.com/investing/2020/02/27/google-buying-way-...
Certain types of large manufacturing equipment must be built in a crop-specific way or at least benefit significantly by being designed for a particular crop.

For example, all cannabis flower (non-extracted) is harvested by hand and then trimmed by hand. Recently machines were made to trim large amounts of cannabis efficiently with high quality. It used to take one person at least an hour to trim a pound of weed. Now a machine can do 10lbs a minute.

Throughout the supply-chain, there are machines that must be built to support the physical scale. This isn't unique to cannabis, vaping had the same problem. The cartridges used to all be filled by hand until someone invested in the machinery. That what causes standards and grades to be created. None of that really exists in cannabis/hemp right now.
What color is the shed? What is it made of?
Part of the reason few people said "think of the poor medallion owners" is because the whole medallion system was a deeply corrupt racket run by organized crime.
https://gist.github.com/nicowilliams/ea2fa2b445c2db50d2ee650...

(Viktor here is https://github.com/vdukhovni/, and I did heavily alter that code.)
These concerns are always overblown. The switch to autonomous vehicles isn't happening overnight. It'll be a generational change, and the current drivers will simply retire. If there's a young kid today who is dreaming of growing up and becoming a truck driver - yeah he's in trouble.
The difference is that in a normal customer/supplier relationship, both parties decide on the price and what will be delivered beforehand. Then the supplier does his job anyway he wants, and in the end, hopefully, the customer will leave with a product matching what they agreed upon, and the supplier with the money. The customer doesn't stick his nose in the supplier's business or decide how the job has to be done.

Of course, the line can be blurred a bit. You may expect the supplier to follow a certain process, provision for changes, etc... But if you start messing with your supplier's business a little too much, it becomes what is called in french "délit de marchandage", which means you are treating your supplier like an employee, and it is illegal.

In France, contracts are much more constrained than in the US. In some cases, like when you rent a house, the contract you signed means almost nothing: most of what is not already a legal obligation is unenforceable.
Google has begun OCRing text inside screenshots to show up in search. I've seen it happen first hand.
You have narrowed in on the exact point of the game:

Alice and Bob can pre-share arbitrary amounts of classical information and still not win more than 89% of the time.

What would your strategy be for sharing information before the game starts?
https://gist.github.com/nicowilliams/ea2fa2b445c2db50d2ee650...
Scientists are looking for the best strategy to avert incoming asteroids
Yes! I watched that video as well around the same time and read the book. (Admittedly I was in a "positive psychology" kick at the time and was consuming anything about happiness.)

I like your summary. An even more general way to look at is that we have less control over our minds (and moods) than we expect, so don't stress about it. :)
Even though UIs were always built on consensus and common experiences users might have from other platforms, I agree that deviating from the norm is a bad idea in most cases. That said, the specific component in question is so common now that for future generations it might become as intuitive as a checkbox.
Yes. Teamware with Casper Dik's "turbo" extensions. We used that at Sun, with a rebase workflow going back much earlier than 2002, but 2002 is when I joined Sun.
I didn’t say it’s right to do that... just that it is that way many places.
The correct answer of course is for a mass protest where a great many people flag Google's own content as violating copyright...and keep doing it month after month after month until this nonsense ends.

Here's the channel, get to flagging. https://www.youtube.com/user/Google
Kieswzvsfaf123
B-@€@hzkdhudysgwwudgiwtwiwhdbcbxxmbxndfvjdkdvdkzbznzbzznzzbzz
The worry and panic can be viewed as the social mass fever. Possibly a dangerous symptom if it gets out of hand, but actually a strategy to fight the virus.
We do not manage the setup of cloud native services just yet, but it's on our very near term roadmap. Seed data is something we're currently working on building now with a few of our early customers. We will tackle that first, then the cloud native services.
Frankly I'd be in favor of a piece of regulatory legislation requiring that all software which features an automatic update mechanism be required by law to inform their users of a change in ownership and obtain affirmative consent to begin receiving new versions from the new owner.
If it is possible for a human to do today, eventually a computer will be able to do it as well.
The answer to your last question is yes, with cases already of Chinese nationals returning from Italy with the virus.
https://classic.qz.com/machines-with-brains/1017379/these-ar...
> People living in single-family houses and driving everywhere consume much more resources per person than those living in high-rise apartments and taking public transportation or walking.

Neither of those fall into what I'd consider a rural "homesteading" scenario.

In my experience rural living conditions involve such an inconvenient drive to town that you make shopping lists and coalesce needs for the infrequent trip. It's necessarily a bulk-mode operation with substantially improved efficiency over what you're describing which strikes me as the typical suburban American home.

Of course if rural folks are commuting to a city by car every day for work, it's not great.
Now they will probably lock a driver to their service and then a new fight will ensue when courts try to rule that is not allowed and find a new class to these drivers in.
I think most businesses could crush their competitors if one of the worlds largest economies decided to be their bottomless patron. Framing it as "getting financing" makes it sound like some kind of venture capitalist affair when the reality is that China decided to kill foreign competitors with heavy state subsidies and all the California hippies cheered for it because they cheer for anything with the word solar attached.
Well, that's sort of the point most of us seem to be making here. We don't understand, and more importantly, the excerpt doesn't explain, how sharing an entangled particle pair (from which you can generate two infinite streams of identical information on both sides) is interestingly different than sharing a seed to an RNG (from which you can generate two infinite streams of identical information on both sides). They're apparently the same phenomenon, so asking people to think about the game without explaining what the difference is means you haven't really explained what's going on.
He asked why people spend so much time trying to work with git abstractions then claimed "works for me". It's not gatekeeping, when replying to strawmen. Try to keep track.
how long is it going to take someone to download 100,000 of these, hang them up on a bar wall somewhere and sell them for $20 apiece?
They don't have to be there the entire time. They can get on/off at a stop close to the city, for example.
That is why I am pissed when they said WebKit ( or even Chrome ) is the new IE when they have never lived or developed during the IE era, even jQuery came much later.