skysight-inc/HackerNews huggingface dataset:
Total Number of Coronavirus Cases in the U.S. (official)
My prediction is that this backlash won't happen. At least not in France.
It doesn't have to be malicious.
File Descriptors aren't part of the isolation offered by cgroups, a misconfigured pod can exhaust FDs on the entire underlying Node and severely impact all other pods running on that node.
Network isn't isolated either. You can saturate the network on a node by downloading large amount of data from maybe GCS/S3 and impact all pods on the node.

I agree with most things you’ve said around gVisor providing sufficient security, but it's not just about security, noisy neighbors are a big issue in large clusters.
I wonder if he missed out on his earn out because he was fired from Uber. I’m not sure how that all works legally. Anyone know?
Not exactly. Rust has panics, which are arguably exceptions stripped down to their most practical forms.
> verbalizing this kind of thing can help show that often the extreme worst case thinking seems a little more ridiculous out loud.

None of those examples you've mentioned sound in any way ridiculous to me. I've had two of those happen and one very close to.

An approach that seems to be working for me lately is to simply try and accept the (realistic )worst case outcomes as a very real possibility, try to accept it as-is, but without piling on further mental agony with value judgements.

"Yes, XYZ can and probably will happen, but I will survive it. If I don't, I wouldn't need to worry about it anymore anyway."
I used to think that but then I realized that you would also have some parts of the world where the date switches over in the middle of the day. I mean it is certainly odd that different parts of the world are on a different day than other parts, but I think switching the date in the middle of the day is a bigger issue.
This is definitely my biggest worry, too, especially since we rarely have merge conflicts on our 6 person team.

Merge conflicts are rare for two major reasons:

1. We plan our changes to avoid the likelihood of merge conflicts. Specifically, we try to avoid two people working on similar areas of code at the same time.
2. We have functionality split into a fair number of different repos (though I probably wouldn’t call them microservices), which not only makes 1. easier, but simply reduces the chance of two people pushing commits to the same repo.

Part of 1. also involves giving slightly bigger pieces of work to a single developer, so that person can see it all the way through from the start. That way, there may not be as many short PRs that are quickly merged, but that developer can really wrap their mind around the complexity of the problem and hopefully have a higher quality functioning product at the end.

Of course, we also have our use cases reasonably solidified when we start building, since our company is over 8 years old and we take the time to know our customers’ desires fairly well (and are always learning more, or course!).
A very basic truth that AWS understands is that you introduce a product at price X, and then either keep it at X or reduce the price moving forward. You never, ever, EVER increase prices on established products. You also basically never discontinue products, even if there's only a handful of customers still using it (ex: SimpleDB).

Apparently it's just too tempting to Google management to juice revenue in the short term, but screw their customer trust and adoption in the longer term.
If that's a moon then so's the ISS.
Sharks Are Evolving to Walk on Land
Those youngings probably don't remember what the Germans and Japanese did in the 40's either.

Or the good old day's when Ultrix ran like a racehorse on 4MB of ram (it did BTW!).

We don't do our credibility any favor when we live in the past and don't update our worldview based upon current facts.

Jeffrey Snover [MSFT]
Take-it-or-leave-it is good enough. That's how eg groceries are priced.

Competition does the rest.
People accept the risk of driving because they feel like they're in control and can prevent a bad outcome. The same is not even remotely true about a drug.
Top 7 payment gateway for your eCommerce business.

Here we discuss the most usable Top 7 payment gateway for your eCommerce business, we hope this article will help you much. Take time and read this full article it will give you a proper net and clean experience. When you read this (Top payment gateway for eCommerce business) full article then you know how they work and what is the pricing, and which company will provide you the best solution for your business!

https://www.electronthemes.com/top-7-payment-gateway-for-you...
This shouldn't be a big surprise. Just 150 years ago, tens of thousands of people simply walked across the continental US.
Assuming that you are on friendly or at least cordial terms with the owner, then why don't you actually have a chat with him. What has changed? How many other stock holders are there? Is he planning a big change in structure, investors? Is your stock holding simply a book keeping inconvenience?

In any negotiations, you first need to gather your facts. Once you have the facts, you might be in a position to ask for more, etc.

BTW if by your calculations it has taken 5 years for your stake to grow in value to $3200, then perhaps you could counter with a sell bid of $9500?
Top 7 payment gateway for your eCommerce business.
Here we discuss the most usable Top 7 payment gateway for your eCommerce business, we hope this article will help you much. Take time and read this full article it will give you a proper net and clean experience. When you read this (Top payment gateway for eCommerce business) full article then you know how they work and what is the pricing, and which company will provide you the best solution for your business!

https://www.electronthemes.com/top-7-payment-gateway-for-you...
Also the $120M they gave Levandowski as bonus.

https://thehill.com/policy/transportation/327093-google-paid...
I believe the alternative to driving Uber is serving at McDonald's, not becoming a homeless street urchin, so vivid imagery of this strawman notwithstanding, the argument for regulation isn't nearly as convincing.
Nigeria's Floating Slum in Lagos
It's nice to see such mutual respect between people operating in such seemingly different styles.
Node v13.10.1 (Current)
his contract to sell w uber had a significant earn out, the 680m was based on hitting different tech milestones. He hit none of them before he was fired.
Is it a bigger issue than signing and dating a document while in a different time zone from the one the document needs to be dated in? E.g. signing a contract on the west coast when the contract needs to be dated on eastern time because of regulation X by agency Y. What if there are multiple regulatory agencies that want you to date the document in different time zones? e.g. the SEC and the ECB.
That's a rationalization though, not the reason. FreeBSD's GPL "exorcism" efforts had been going on long before FSF started floating ideas about GPL 3.0.
This is completely misleading. Even if his first company was the first self driving vehicle project ever (which was not) or the only piece in the puzzle (which it wasn't either), there were other cofounders of that startup. This is glorifying one person using other people's work.
I've seen the point you make about trademarks often repeated but it is infact not true.
https://www.eff.org/deeplinks/2013/11/trademark-law-does-not...
Step by step we've been doing more and more focused on Linux users. If you take a look at our telemetry - it is clear something is working because Linux usage is through the roof!!!

https://aka.ms/psgithubbi

I don't want to make any news here but in a bit, the team will publish a blog articulating where we'll be focusing our next release. I think you'll like the direction we are taking.

Jeffrey Snover [MSFT]
Interesting and somewhat counter intuitive to me. I imagine that depends on where one lives in a particular timezone.

Personally, I prefer DST. During standard time in California, I have to shift my sleep cycle earlier relative to the clock time as I am unable to sleep once the sun is up which is typically before 7 am.
You could be very correct! I think Linus might not be an experienced "git for Windows" user
Have you ever tried tilting your head back farther into the water & swimming with your feet slightly?

These 2 things are the difference for me between sinking & floating. Mostly tilting my head further back though.

Of course this fails miserably with even the smallest waves.
What I most frequently heard was "There are two solutions: the deprecated one, and the one that doesn't work yet."
Or maybe he off-shored the rest of his money? This < $100mil are the assets that are under his name and the rest are in tax havens/under different shell companies? Not sure whether that is possible. But it seems like rich people always have multiple ways of hiding their money.
As much as I think HN is blowing the coronavirus risk out of all proportion, I must say that it is incredibly unlikely that the numbers reported here represent even a meaningful fraction of cases in the U.S.

Which makes sense, as they are only considering folks actually tested, and there hasn't been a meaningful plan to test people that weren't already almost certainly infected.

Of course, virtually every country is likely missing the majority of cases from their official numbers.
Point 1) matches my lay understanding of quantum entanglement; information is transferred somehow between the entangled particles but not in a way that we can use. So if this new thing IS communication via entanglement (and I can't see how it's not, given the description) then that's huge, and opens the door to all sorts of interesting things.
> 1). CEO with delusions of grandeur who thought that Amazon was a direct competitor to their business and should not be given money.

I mean, look at Netflix.
Wasn't it so that in France Ryanair pilots are not allowed to be self-employed subcontractors either? (A model that Ryanair prefers.) Both makes sense to me, neighter of them can really set their own prices, schedules or work-conditions.
I like how you phrased this. Wild how recent the continental migration was.
That's no moon. It's a space station.
That’s the rule for MIP: Alice and Bob can’t communicate once the game starts, and their messages to the verifier depend on challenges from the verifier (which they can’t predict).

Like imagine the 3x3 grid suddenly changes after Alice and Bob write down their first message.
I think that the costs of liquidating and reforming would cost far more than $4500. A 1.5% stake can be easily diluted in value by issuing more stock.
This is why I wrote a "digital sundial" that calculates:

* the current quadrant (early morning, morning, afternoon, evening)

* the progress through the quadrant as a two digit hexadecimal number

I later stumbled across XKCD 2050, "6/6 Time".

https://xkcd.com/2050/

https://gitlab.com/cameronnemo/sundial
We use this work flow and it works masterfully. I have no need to save all my small commit - partly because I commit often to run tests in parallel on a CI server.

Does anyone know of a layer that you can use on top of git to make the occasional squash and rebase easier?

I know gitless is a helpful layer on top of git but not sure it support this specifically.
Agree with the thoughts on atomic and meaningful commits (though would drop the merge commit entirely), and I will rebase my commit history extensively at times to get it into a presentable state along the lines listed here.

Bottom line: the history, content, and message of each commit, in addition to the resultant repo state, are all artifacts of your work and are worth shaping and crafting in order to optimize for communicating to yourself and your fellow developers in the future.
Those show why I called it a heuristic. With some code similar to yours, I would probably use parentheses unless they are frequent enough to deserve some brain cells.
For what its worth, ALB is a fantastic product. As a full L7 load balancer it can stand in the place of nginx, provide OIDC auth, replace API gateway especially for high volume Lambdas, and has lots of tunable logic for running diverse auto-scaled workloads. AWS is good about not breaking APIs and contracts, so the "strangler" strategy is really about accommodating existing customers. I'm not going to say Classic Load Balancers are a dog of a product or anything, its just that they pre-date VPC, and the web stack has moved on since then.

Having ALB be such a robust, turn-key product does tempt one into giving it a lot of responsibilities which definitely lends itself towards lock-in. I guess its the same with marriage: there are always tradeoffs.

I do wish it was better integrated with ECS + AppMesh + API Gateway, so it could be like a managed GetAmbassador.io. Envoy proxies are a hell of a good idea, and I think are going to be something like the React of the backend. While one can dream about a grand unified request router for the cloud, ALB continues to innovate with things like canary deployments and awesome routing rules, all well continuing to 'just work' at web scale. Is there anything else you can throw up to 50K RPS at and not have to think about it that much?
Good link. It looks like half of the purchase price was supposed to go to Anthony, but under a vesting schedule.
I have mixed feelings about this. In a language with proper enums like Rust this is certainly the way to go, because your entire data structure can be tied to which state you're in (Success would only contain the position, Rejected would only (and always) contain an error, Loading would never contain redundant data). In Rust you would also get the benefit of having match { } make sure you always take care of every possible variant.

In JavaScript, on the other hand, code could just as easily set an error and forget to set the status as set an error and forget to clear the position. There's still some overlap between state info and there's not a singular, clear winner between the two patterns.

Here's what I would do for this case: first, move the error rendering clause above the position one. Erroring, like loading, is an exceptional status above the "normal" status. Therefore the position should be the "fallthrough" branch. This change alone would fix the actual problem demonstrated.

Then, to help avoid inconsistencies, I like to put my "isLoading: false" in a "finally" clause (if it's on a Promise), or some equivalent. Unfortunately watchPosition is a bespoke function with regular callbacks instead of a promise, but you could still centralize the loading flag clearing in some way. Or maybe "promisify" that function with a new Promise((res, rej) => {}).

Certainly if you have more than just these three statuses you start getting into territory where a status string makes more and more sense. However, these three (success, error, loading) are special, and in a large number of cases they're all you have, so they can be afforded some special treatment.
Yes less than $100m. Probably closer to $4.89 and some long time ago there was a trust in Singapore bulging with much more than $4.89.
Pretty much.

Throwing [0] to chrome and firefox has made made them hang for 5 minutes so far. Generating the HTML took under a second and 13MB, large, but not larger than the fatter webpages out there.

In terms of input browsers don't see but should be able to parse you can't get much simpler than this.

[0] In Guile2.x:

(define print
(lambda (x)
(display x)
(newline)))

(define div-hell
(lambda (n)
(cond
((eq? n 0) (print "TEXT"))
(else
(print "<div>")
(div-hell (- n 1))
(print "</div>")))))

(print "<html><header><title>DIV HELL</title></header><body>")
(div-hell 1000000)
(print "</body></html>")
> Why not just imagine Alice tells Bob how she's going to choose what to write in the boxes? That works 100% of the time too.

No, it does not. Let’s suppose Alice’s pre-negotiated (or predetermined by a seeded PRNG) choices for rows 1..3 are:

(A11 A12 A13)

(A21 A22 A23)

(A31 A32 A33)

And Bob’s choices for columns 1..3 are:

(B11) (B21) (B13)

(B21) (B22) (B23)

(B31) (B32) (B33)

If they are given row 1 and column 1, the intersect should match, i.e. A11 == B11. The same goes for any row and column selection: Aij == Bij.
That is not, however, consistent with the requirement that the sum of all numbers for Alice must be an odd number (each row must add up to an odd number and there are 3 rows), and the sum of all numbers for Bob must be an even number (each column must add up to an even number and the sum of three even numbers is even).
So, that’s the real catch for the classical setup. And yes, quantum correlation can beat it.
> people use local time to decide when to go to bed, and when to get up. Aligning that to the sun is the most important bit.

And yet, this is what DST gets so damn wrong.
The original blog post is a pretty fantastic piece in support of teaching humanities in CS, I'd say!
T-Mobile says that no financial data or social security numbers were accessed in this data breach, but account info like name, billing address, and phone number was accessed.
Indeed. I can see your marketplace view,
But if you see 3 ads in a row that you know are a bad deal for you or are just not great in term of timing.
You could still read the ads on the handyman site.

In Uber world, you get banned of the site.

> In addition, if the driver has declined more than three rides, Uber may temporarily disconnect the
driver from its application

I think you missed the part about subordination. Yes, you could have a service like Uber where you are still your own boss. ( Curb, for instance, is the response from the traditional taxi drivers )

But in the case of Uber, I tends to agree that they get away with a lot of subordination, without giving away work contract.
I see what you are saying now. Wasn't clear from your earlier comment.

I hope that the mortality rate turns out to be lower than it appears at the moment (i.e. an undercount of infected people).
Facebook Employee in Seattle Diagnosed with Coronavirus
I found it interesting to note how viscerally uncomfortable I felt while looking at some (or, most) of these pieces.

Of course not all art has to be pleasing to the viewer, but confronting/challenging art is made deliberately that way by the artist, and the process of experiencing the art involves understanding the feeling and learning something from it.

It's a different feeling altogether to be discomforted by art, but for no purpose.
The article claims that "gitflow abandons rebasing", but this is simply not true!

In my team we use gitflow with rebasing. In fact, the original gitflow implementation comes with rebasing support built-in (as a flag for the "git flow feature finish" command). We just modified the script to enable it by default.

Another thing we changed is dropping the "master" branch, since it didn't provide anything useful.

Now, you could claim that this means we're not really using gitflow, due to all these modifications. But the fact is, I still give this article as mandatory reading for new developers in our team, and it's still a great introduction for working with feature branches. I'll continue to recommend gitflow.
Cases in China are growing at a sublinear rate according to the Chinese government.
Master should always be in a deployable state.

Isn't that what the develop branch in Git Flow is for? Your project might need some additional steps as part of its release process, and those can take place using the corresponding release branch, but the idea is that you can start a new release off develop whenever you want.

I like squash commits: build a feature iteratively in a branch + pull requests, squash to master once it has the tests and documentation bundled together with the implementation. This gives you linear history.

Indeed. We're talking about using Git. Even if you're using a Git Flow style of workflow, why wouldn't you regularly rebase any feature branches back onto develop if they're lasting more than a short time, so you are keeping up-to-date, and why wouldn't you squash the finished feature down to a single commit that can be fast forwarded onto develop when it's ready, to maintain a linear history with one commit for one significant feature or fix?

The only time I've seen non-FF merges in a Git Flow style project is for bug fixes on release branches, but those tend to be characterised by two key properties: they are relatively simple and relatively important. If it's not simple, you probably need to abort that release and go back to your main development line to do whatever more substantial work is required before continuing, then make a new release. If it's not important, you probably ship that release with the known bug, and the fix gets made on the "develop" branch via the usual process for incorporation in future releases. So the effort involved in merging bug fixes from release branches back to develop is typically both relatively small and well justified, and if you do need any manual conflict resolution, that implies divergence since the point when the release branch was started and then it probably is a good idea for someone to take a more careful look and make sure the bug is properly fixed on develop as well.
These cases were first identified through the test kits, so apparently the tests do catch both strains. Since the difference is only a single nucleotide the tests can not distinguish between the two. This study uses results from full genome sequencing, which is much more laborious and less frequently done.
If the truck is manned, it's robbery.

If the truck is unmanned, it's burglary (or theft, since a truck isn't a building).

They typically carry different penalties, and the difference is even more stark if you happen to have anything that could be considered a weapon on you when you do it.
People would steal from trucks significantly more frequently if there was no risk of harm like there is with the shotgun scenario.

I had two bikes stolen that had locks at them (at different times) from my apartment in Mountain View. Theft is rampant and removing the threat of a real driver pushing back completely changes the calculus for trucks.
A tiny asteroid captures the attention of astronomers that may have been around for a year, but will be gone in the spring.
> the quick witty repartee of his brother Groucho

That's what I enjoyed. Not the harp and piano playing, nor the physical gags.
A getaway car isn’t needed, you just amble away and walk two miles the other direction.
A really well done fly through video of a very large image, with some incredible detail within.
It's not just that it's easy, but that the theft is legal and profitable. You don't even need to be rich to do this, you just need stuff you can claim; see How to Break YouTube (Copyright Claim your own video).

https://www.youtube.com/watch?v=ieErnZAN5Eo
Managing .NET Dependencies in Unity3D
And none of that will matter because they will just have a video of someone in a ski mask robbing a truck and walking away.
Startup Funding: February 2020
> In Australia, in Queensland, we've been trying to get this outdated state to start using daylight savings for years.

Speak for yourself. I live in the south east and don't want DST.

> 95% of the population is in the south east.

That's not accurate - where did you get that figure? Regardless, Western Australia has an even greater percentage of its population in the southern part of the state than Queensland, and it voted against DST four times over the last 40 years.

> it's so bloody hot here in summer.

Not to mention by the time you go to bed the temperature is cooler without DST.
Twit large.
Probably, it is not uncommon for people to dump large sums of money into renovations to their property before a bankruptcy.

Although I would imagine if it was very egregious, like $1m toilets when essentially no one else has anything reasonably close to that, that a judge would probably strike that down and require you to liquidate it.