skysight-inc/HackerNews huggingface dataset:
BRUSSELS — European leaders agreed on Tuesday to close off their territory to almost all visitors, shutting the door to most travelers for at least 30 days as they struggled to arrest the rapid spread of the coronavirus on the continent.

The leaders, meeting by teleconference, agreed to close off a region encompassing at least 26 countries and more than 400 million people — setting out on a long stretch of isolation unlike almost anything seen in modern European history.

Exceptions will be made for European citizens and residents coming home, although some countries were asking them to self-isolate for two weeks, in some cases away from their families. Medical professionals and scientists will also be exempt.
In my experience, people mostly refer to him internally as "Mark". Just like at Google they refer to Larry and Sergey as, well, "Larry" and "Sergey".
Your prior should be that immunity works as it does with every other virus and you should require very strong evidence to the contrary (evidence, not anecdotes) to convince you otherwise. Throughout our evolutionary history we have come into contact with innumerable viruses and to a greater or lesser extent we have immunity to all of them post exposure. For many our immunity is long lived, on the order of years.
Not to refute your claim, but this is my 3-line bash script in order to build and upload a static bundle:

"""

#!/usr/bin/env bash

rm -rf public

hugo --verbose

aws s3 sync ./public s3://$BUCKET_NAME --profile s3_personal

"""

You can set custom TTL for CloudFront to 0 for instant refresh in production. Dev server is `hugo server`, `hugo` is a single Go binary you can Dockerize with --net=host and --volume=$(pwd):/app to use your own dev environment. If you don't maintain too many large static assets, your cost is like 5 cents a month, and I think that's a competitive price, not AWS being generous. $12 / year for a custom domain via ICANN, and Route 53 manages A/AAAA/CNAME/MX records for free.

Again, not to refute your claim. I'm a single author, who publishes as a hobby, with a single dev and a single prod environment, so if things break down (it hasn't for years), it's easy to fix. It's much different than content marketing and enterprise use cases. Even so, I would rather start here and add a static CMS like Forestry before considering a custom solution like Netlify (which is probably built on top of AWS anyways).
OP doesn't mean that the buybanks raise employee salaries because the stock they receive now has a higher price, they mean that the stocks the company is buying back are then given to the employees as RSUs.
My take is that most companies don't need a native app unless they're specifically targeting mobile users and doesn't have a need for desktop users.

So you're better off generally to make the app a web app. If that doesn't work yet, are you sure about that? With web assembly and some new browser apis it's really very few apps left that actually need the native experience.

Sure if you build apps for cars, planes or something like that I understand that you want the native experience. But there is also tons of "native with an asterisk" tools like Xamarin and React Native for example.

Sure the app may be a bit larger but do users really care? With those kind of technologies you can build native for all platforms easily.

The choice really is up to the developers and there is lots of choices nowadays, thankfully.
> Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith. [0]

Replace "maps" with the names of any competing products from both companies with a web presence that can be linked to in search results, if you want to genuinely rebut the point.

[0] https://news.ycombinator.com/newsguidelines.html
I agree wholeheartedly, investors really dislike raises and bonuses for line employees, and will punish companies for it. Shareholder primacy theory is insanity.

Speaking of insanity, Art Laffer is advising the current administration re: stimulus. How that guy isn’t immediately laughed out of any room he walks into is beyond me.
If memory is the only resource you have to worry about, then garbage collection is (usually) fine. If you have to worry about file handles, sockets, semaphores, and the like, then GC solves 90% of the problem (memory), but usually leaves you worse off for dealing with the other resources.

Why does it usually leave you worse off? Because, since it's garbage collected, the language usually doesn't see the need to also provide a good way for the programmer to manage lifetimes, because, hey, we've got garbage collection, so why would they need to? The result is that the programmer has no help at all with the other resources.

So that's where I think the line is. Do you just have memory to worry about? Or do you have other resources as well?

And, to be clear: Yes, if you only have memory to worry about, garbage collection is fabulous. A whole set of problems just... goes away. It's very freeing.
Well no, one upgrade path is to port to .NET Core 3.1 which supports WPF apps.
The mental gymnastics this must take. I would be impressed to see how you claim flying airplanes full of civilians into building full of civilians is “defense”.
The problem is not him losing access to his code. He actually probably wouldn't as he likely has a local copy. The problem is that much of the open source infrastructure now relies on github repos, npm repos (which are now owned by github btw), and so on corporate resources. And those can apparently be completely wiped off the internet because somebody made a random offhand comment somewhere. Avoiding github and similar repositories would require pretty much giving up all modern open source infrastructure - or taking extraordinary measures of keeping a local mirror of every single repository you've ever used and every dependency of those and of the software running those. This is not a normal situation.

I understand when a corporation needs some CYA policy to avoid charges of "hostile environment" or whatever. But for whole open source development world be the hostage of these policies is not a normal situation. We need separation of corporate PC and technology, otherwise it ends in a lot of trouble for everybody.
Maybe it's sort of survivor bias. Maybe antivirals don't weaken immunity but people who survived thanks to antivirals have innately such a weak immune response that they wouldn't have survived without them.
> in the area of cloud computing, we are seeing a resurgence of interest in extremely strong copyleft licensing, such as the AGPL

The problem with this statement is that NONE of the actual successful projects that are turning to the AGPL are making an open source play. Instead they are pursuing a dual licensing strategy.

I love the GPL2 but I think it's time for the FSF to accept that because v3 and Affero overreach so much they have made software less free.

I once began negotiating to pay for a dual licensed package and after several rounds of email, the lawyer finally revealed that the cost to my company would be $10,000 per host and 1/3 of our gross revenue. That is why where I work now, and everywhere I've ever worked, Affero and GPL3 is forbidden.
Get a blood test. If CRP raised and lymphopenic, likelihood of ARDS requiring ITU admission is higher. This can happen very quickly after the first week, so I'd put pressure on the doctor to keep me hospitalized.
In your world does intent matter?
I did the same thing, however I thought I knew the keys! Took a few weeks but now I'm typing far faster.
The Elders
unsafe is an escape hatch. You don't have to use unsafe to get performance, in the general case. Often, safe code is as fast or faster than unsafe code. But sometimes, it is needed. Even then, the point of using Rust is containment: you can write a safe abstraction over that unsafe code, and minimize the hunt for what you did wrong, if you've made a mistake and caused a problem.
Agreeing with your point: there is only one human virus thought to have been successfully totally eradicated: smallpox, which plagued humanity from ancient history until the late 1970s.

But herd immunity due to widespread (if imperfect) vaccination gets you much of the way there. Assuming flu vaccines continue to work, there probably can't be flu outbreaks that kill tens of millions of people as there have been in the past.
That's sensible, but there is a lot of fear right now. People are afraid that the recession will be strong enough to cause people to cut services. Similarly, Google is advertising driven. The value of advertising can drop during a recession.

I'm not necessarily saying that either of these will happen, but there is risk.
Bear in mind if you're a programmer that touted learning resources that don't include symbol keys are of limited use. There are many speedy human-language typists who have to peer at the keyboard every time they encounter a tilde or Fn key.

I'd also add: only make this a priority if you don't already touch type. If you do, your speed will be adequate, and you'll gain more by adding higher-level tools to your arsenal (refactoring, structural editing, etc). It's sad that in 2020 we're still largely 'editing text' when programming, but careful use of IntelliJ or emacs (amongst others) can often lift the mechanics up a conceptual notch or three.
That's why I mentioned it as a caveat.
We use this product on our company of ~150 during the COVID work-at-home thingy.

It's quite great ! It supports audio and video and is quite reactive for us.
Other than for DX, is there a reason to go with Netlify or Zeit? I personally don't care about this.
WiFi -> electric current rectennas announced a year ago[1] were in the range of 40 microwatts, and the blog post says this NFC system runs at 1.4 Watts, that feels a long way away. But years ago LCD calculators could run on a solar cell the size of a finger and powered by ambient room lighting - surely must be some close to crossover level available.

[1] http://news.mit.edu/2019/converting-wi-fi-signals-electricit...
...but I am an elected government official (for a hyper local government, though in a good position where I get to peak behind the curtain of the regional government above me) and the vast majority of my friends work in government; and when I present the argument about capacity expansion moving the line on that cute graph upward as a critical thing we should be doing in addition to moving the peak down and to the right using capacity expansion, the reaction was literally "huh, I hadn't thought about it that way before" :(.
Does cp support it (on a BSD)?
LTS version is like a checkpoint. Its support will be long term, i.e. security patches will be released on them. The versions in between don't get support.
This isn’t an opposing point. You want both.
I don’t think anyone’s arguing for speed over domain expertise. But all else being equal, iterating more quickly is an obvious advantage. You get more chances to correct mistakes and adjust to new information. Your decision may be to continue with the same strategy, but having the capacity to make that decision is important in itself.

Take fencing, for example. At low levels, people often try to make up for poor technique with speed and strength. Like you point out, this is a mistake. But at the highest levels, where everyone’s technique is basically flawless, the winner is the fencer whose thinking is a step or two ahead.

That said I’m really talking about situations where you have an active opponent. With more static problems yeah, being correct is more important than staying on your toes.
Have you seen jc[0] as an effort to wrap common utilities to output json?

[0]: https://github.com/kellyjonbrazil/jc
How do you mean that Firefox is struggling? It is not my experience this is so. Everyone around me is ditching Chrome for Firefox.

Firefox is also ahead in a few areas too: containerisation & privacy. It's also now the default browser on a few oses.

To me this does not indicate struggling at all.
Macros are extremely important to make rust productive. It sometimes feels as if you were writing in a higher level language.

One of the best examples is the serde crate. What a beautiful library!
Edit: This was incorrect. I blame the second largest Swedish newspaper for the disinformation.

A least wrt Sweden: Apart from the exceptions (including transports), travellers from other European countries will also be blocked to enter starting March 19. (It's not just a block from the rest of the world to EU.)
Anyone can easily verify this by downloading the binaries, and running checksec themselves.

Here's the output:

$ sha256sum palemoon-bin
0b7f4ad73fc671e20bfb2366aa9d9ad81e82a3c8f63acde7f37063e73fda2141 palemoon-bin

$ checksec --file=./palemoon-bin --output=json --extended | jq
{
"./palemoon-bin": {
"relro": "partial",
"canary": "no",
"nx": "yes",
"pie": "no",
"clangcfi": "no",
"safestack": "no",
"rpath": "no",
"runpath": "no",
"symbols": "no",
"fortify_source": "no",
"fortified": "0",
"fortify-able": "15"
}
}

Notably, the binary has not been compiled with -fPIE and -fstack-protector, which disables two very basic exploit mitigations - ASLR and stack canaries. Any self-respecting Linux distribution enables these compiler flags by default nowadays. -D_FORTIFY_SOURCE is also missing, unlike Chrome or Firefox. A modern browser uses dozens of custom binary exploitation mitigations in addition to this.

Mitigations and sandboxing are the difference between an exploit a CTF player can write on an afternoon, and a multi-month expert-level endeavour.
Let's design and deploy an open source ventilator to prevent COVID19 deaths
Sure, except that the article was talking about changing your OODA loop to somehow disorient an opponent. And while that might be useful the same can be achieved by having so many more OODA loops than your opponent that you can simply choose to drop packets in order to take advantage of some timing benefit. Generally, when you're doing sampling data, it's much better to sample at the highest frequency possible, and downsample as needed. Even with dumb linear interpolation you'll still generally have higher resolution with less uncertainty than if you try to reduce your sampling to match some kind of signal.

I do like you bringing up starcraft though. Clicks per second can largely be mapped to the frequency of the OODA loop. When I was following the broodwarAI bots a couple of years ago, usually the better bots tended to have a much higher meaningful clicks per second than worse bots. This of course, isn't necessarily causative, since the better algorithm may spend more time on analysis so that it clicks less, but each click is more valuable.

But I think you are right, in that the bigger idea OODA was that the reason the pilot who came up with the idea originally was using it to describe why his largely inferior plane was able out dogfight enemy planes. That the plane he was in had more responsive controls, which allowed him to react faster to his opponent, and also to keep forcing his opponent to get stuck reacting to his actions. His basic tenet was that because his plane was more responsive, he was able to keep forcing his opponent to have to go back the start of the opponent's OODA loop every time he changed course, thus wasting precious time observing and reorienting.
Can anyone explain how you are supposed to pick up food (or have it delivered) while still maintaining the 6-foot distance from other individuals?
Problem is, that rarely happened because govs are generally bad (not skilled / trained) at running businesses. Pretty much the opposite.

To expand a bit; an ideal system, IMHO, would be a hybrid "state-backed but citizen-controlled" entity (half-way between nationalized and publicly traded) wherein shareholders involve citizens but not govs official (who have their own agenda, etc.); this is to maintain a sane separation between "the things belonging to citizens" and "the affairs of the State as a government").

It also follows a fundamental (but long-forgotten) principle of democracy that citizens should be able to control (as in audit, not "run" executively) the public things. You'd expect such a hybrid entity to be run by good commanders of industry, typical board / CEO but vetted by some citizen-backed legitimacy, in the shareholder voting process (this is a mild / hybrid form of "election", which is too strong as it is for this hybrid entity, but worth the "backed by sovereignty consent" value).
It's mostly the layering that bothers me.

I don't mind Chrome OS and love my chromebook.

Some of this is aesthetic so I don't really expect to change minds, but if we lived in the world of "Life and Death of Javascript" and booted to some kind of Web OS I'd be annoyed at the loss of low level hackibility and get over it.

Booting to Linux, then booting a browser to get to a normal app that doesn't need network connectivity "feels" wrong.
A lot of this is legacy which is why making the argument for change is one about expense. Its about justifying the expense by selling the hot path of the use-case of using technical applications on a phone.
Everyone is sunk-cost fallacy here over the potential of mobile use-cases, they're dismissed as a use-case.

I vaguely bought into the idea for a while and now github are like:

> Review PRs and look at code on a mobile form factor

and now I'm like:

> oh, so that use-case is a thing?

I'm terrified some CTO in twenty years time of an org we want to sell it to will instantly shitcan our offering because it doesn't support mobile use-cases. Because mobile is their culture and the reason we don't value it today is _only_ because mobile isn't the culture we grew up with.
Not their fault. It’s in the name.
LOL, thanks a lot for sharing! Really made my day here, and I needed that :)
I guess you do not work in an enterprise environment. There are many reasons to use LTS releases, stability and security comes to my mind first. 3rd party requirements are also important in this topic.
Love seeing more Rust. It's good stuff.

extern crate rocket;

I thought "extern crate XYZ" was old-style? "use XYZ"?
Anyone know what tool the author used to make those nice animated SVGs?
So if I understand you correctly, they voted to extend these (existing) powers short term, and will have another vote later on whether to keep them long term.

The headline seems to imply congress is trying to sneak something by while everyone is distracted, rather than maintaining the status quo temporarily.

There's enough to be concerned with congress without being misleading. Framing everything Congress does as some conspiracy theory only dilutes the response when actually shady things are happening.
$70 for the larger one, I was really surprised at the low cost.
They're not major releases; in fact, the last major Java release ever was 9.

The way releases used to work for the past ten years or so was that after a major release, every couple of months there would be a bugfix/security patch, and every six months (for a year or more) there would be a feature release (that used to be called "limited update") with major new features (new GCs, new monitoring mechanisms etc.) but without spec changes to the language and libraries. This meant that all the changes that required changing the spec had to wait for the major release. This had several bad implications. Most if not all of the spec changes were no more disruptive than the changes in the feature releases, but they had to wait for the next major release -- a lot of changes delivered at once created an overall fairly large disruption. Also the major release had to wait for the large features, and people couldn't enjoy smaller ones. Finally, people wanted to get their changes into the next major release so they wouldn't have to wait another three years or more, so features were merged before they were fully tested, which meant that the .0 major release was noticeably less stable.

So, to make the upgrade process easier and cheaper, Java got rid of the major releases, allowed making spec changes in the feature releases, and, with the major releases gone, every feature release gets a new integer name. The result is a much more gradual process. Every feature release is about as big and only slightly more disruptive than the old feature releases. The releases are now much more stable because features are merged only when they're mature enough; there's no rush because if you miss a release, there's another in six months.

The ecosystem will take some years to adjust, but those who've made the transition to running in production on the current release (many still can't, as some tools haven't yet adjusted) report a smooth process.
Khronos Group Releases Vulkan Ray Tracing
I think I could manage this with alpha-numeric characters. How do you fare with programming symbols and such?
And when people talking about leaving, they mean that the mass transmission stops and it continues to transmit, and mutate, among some small subset population (e.g. remote island, etc). Eventually it recurs in the main population, whether hitting people who never got it, or because it has mutated enough that prior protections don't defend against it.

Which is exactly what happens with the flu and the cold. Lots of viruses, constantly mutating. So much so that when the next season comes around it's like an entirely new virus to your body.
US law does not require them to delete everything a person who once been in Crimea ever touched. Let's not shift the blame from stupid overreaction and corporate CYA to "follow the law". There are many ways of following the laws without being stupid.
I got into cooking because I was on a lower salary. I calculated my expenditure and realised I was spending between 150 to 300 per month on just lunch at the time.

One of the easiest ways I found is to simply follow a very basic recipe. To this day I read the recipe several times before I do the shopping and always always put all the ingredients in it's own bowl (or you can put multiple in a single bowl if the recipe asks for them to be into the pan together).

By the time I started reading the methods to do the actual cooking, I have all the ingredients chopped, separated and within reach. That way, as the recipe methods call for certain things, all you have to do is reach for it.

Lastly some general tips.

As you can imagine, putting all the ingredients in their bowls gives you more dirty dishes than you would have otherwise. So clean as you go. If your recipe asks for something to be in the oven, you're likely going to have 30 mins to clean. Think about the tools that can be reused and don't wash them yet.

YouTube, as always, is full of amazing YouTubers who teach you how to cook, and use your utensils properly. Joshua Weissman is one of my favourites and has some insane tips.

Learn to wield a knife. And learn to sharpen a knife. Seriously. This is one of the most dangerous things in the kitchen, and an dull knife is even more dangerous. Joshua Weissman has a video on both topics.

When you're starting out, it's okay to choose the easy path. Picking frozen veggies over fresh veggies and having to cut them yourself is not an issue. It'll set you back slightly more, but it's okay for the convenience. Once you're more comfortable with a knife, start cutting these things yourself.

At the end of it, I promise, you will feel a lot better. Every time I get out of habit and start eating out more than in, I feel terrible. Both physically and mentally. Once I go back to eating in, I just feel better.

Good luck.
I did the same, but the only thing that happened was that I couldn't type symbols (quick, type a $ without looking at the keyboard). I exchanged it with one with keycaps afterwards.
Right, and also SQS can have more than one consumer; I daresay N consumers is the most common scenario.
"The Act passed the House late last week, but with significant bipartisan opposition from civil-liberties champions in Congress and from leading privacy, racial-justice and constitutional-rights groups, including my group Free Press Action."

This is the second paragraph of the article.