skysight-inc/HackerNews huggingface dataset:
From those commits, it seems this issue was fixed in 1h12min. That should be a new record, specially considering this is all volunteer work on a Saturday. While it's bad that things break, the speed at which this was fixed is truly amazing. A big thank you to everyone involved here.
And everyone who just upgrades whenever possible gets to be victims of security exploits too.

Users of Debian Stable missed Heartbleed entirely. It simply never impacted them.
They do (otherwise your curve would never end without measures that reduce the reproduction number to below 1) and it's not (only) my calculations, these things (at least in Germany) have been published a short time after the lockdown was enacted (eg https://www.dgepi.de/assets/Stellungnahmen/Stellungnahme2020... - in German unfortunately, number of intensive care beds in Germany was around 30000 at that point so even in the "best case" scenario they look at - 2% of patients need intensive care for 10 days - a curve that does not bust this number extends well beyond the graph which is one year, and not every country has as many ICU beds per resident as Germany has). The "strict measures until we can get back to containment" was also stated recently as the goal by the Swiss authorities ...
That doesn't get around the fundamental problem here. Why did you make a mistake if you're arguing that you could have not made one? Either you didn't want to make zero mistakes, or you couldn't have made zero mistakes.

> yet here you seem unable to recognize it as the obvious answer to your question.

I'm the one who is insistent that it was a mistake and that people make mistakes. You're the one insisting there's some loophole where you can both get it wrong and feel good that you could have got it right, at the same time. I'm saying that it's your position which is utter nonsense, a meaningless double-think designed to make you feel good, which reflects nothing about the world.

Like a kid saying “I ate ten hot dogs and threw up, but I could have eaten fifteen!” - nobody believes it, you couldn’t, you’re trying to save face and get credit for eating fifteen hotdogs without actually doing it.

Now, whether you can do better in future is a different matter - I’m not saying you can’t do things to avoid that mistake happening again, or learn from experience, or get better.
I'll ask you like I've asked others: Are you personally willing to die for the sake of opening the economy?

If you knew that you were at risk and catching the coronavirus would result in your death, would you do so for the sake of the economy?
Please explain to me the risks of nebulized ethyl alcohol, which is what I am proposing? Ad hoc dismissals without the consideration of scientific literature reviews of alcohol inhalation - which there are several review papers published - demonstrates a serious lack of critical thought in medicine. Obviously to compare it to chloroquine is absurd.

Your point about supplying the safety data is exactly where the roadblock is found. I’ll update you when the device is approved by the FDA and voila these objections mysteriously disappear ;)
There are, rightly or wrongly, strong incentives to not be creative. To do the thing the medical consensus recommends, even if it is incredibly flawed, leaves the doctor personally safe. To try an experimental idea on your own could get you sued for medical malpractice. Which is I suppose to say, that MDs have been given a strong incentive by our system to suppress creativity.

(Personally, I think there’s a good reason for this in normal times. Medical research is hard and personal opinion will never compare to years of research, especially when lives are on the line. In times where years of research aren’t actually an option though...)
My productivity stack:

Zsh (with all the autocomplete plugins)

Oh-my-zsh
zsh-autosuggestions: https://github.com/zsh-users/zsh-autosuggestions

Tmux

Histdb: https://github.com/larkery/zsh-histdb

Zoxide (replace cd): https://github.com/ajeetdsouza/zoxide

Fzf

Rip (replace rm): https://github.com/nivekuil/rip

My personal dotfiles: https://github.com/xkortex/bashbox

Mosh (replaces/augments ssh)

What I'm currently looking for is a better multi-host logging solution.
Bored Russians Posted Silly Art Parodies. The World Has Joined In
I intentionally omitted that bit because I didn't want to prejudice the bit I did quite. If something is true, does it matter who stated it?
Maybe I missed it - but did the author list compiler options? I wonder if the handwritten assambler was slower than a compile with optimizations off, too.
You probably meant The Craft of Prolog by Richard O'Keefe. The preface of the Art of Prolog is about David H. D. Warren's recollections of his first encounters with Prolog.
So, I mind poorly implemented duck typing, I also mildly mind dynamic typing, but in principle I think static duck typing could be not bad.

With javascript promises in particular, the duck typing suffers from this unfortunate fact that you can't easily check if something can be awaited-upon or not. I don't think I really care if something is a promise, so long as I can do everything I want to to it. So I view the issues here as this function over-claiming what it can do, the limitation on the typesystem preventing us from checking the await-ability of an object, and the lack of static type checking. None of those are necessitated by duck typing.

I disagree that you're stuck with this best-effort function. It's perfectly possible to architect the system so you never need to query whether or not an object is a promise. Given the lack of ability to accurately answer that question, it seems like the correct thing to do. At the very least I'd prefer if this function was called "looks-vaguely-like-a-promise" instead of "is-promise".
The number of people that think they understand the scientific method is astoundingly higher than the number that actually do.
The Present State of Covid-19
You could try to use one of the c language reversers to get c source code and then ask gcc/clang.
I posted a comment[1] on here recently wishing more API gateways offer monetization features but Saasify looks like a nice way to get this, just signed up!

[1] https://news.ycombinator.com/item?id=22885263
Did the earliest victims of Covid19 also show similar levels of clots? Or are we only seeing elevated levels recently? Could help to plot this over time as the lockdown extends. If there's a correlation, would help to stress the importance of staying active in quarantine, ex: lifting, stationary bike, jump rope.
Actually there are valid arguments that one of the biggest problems with the German public health system is private insurance competing with the public ones. Essentially it's a licence for the private insurances to print money and siphon it from the system. They have the choice of only selecting the healthy and rich, so obviously they have much better risk distribution.

It also inflates health care cost, because the doctors use the private insurances to finance investments in expensive equipment. Talk to someone with private insurance, they essentially have fight off all sort of unnecessary tests even if they go in to get a flu vaccine. And no not every doctor needs an MRI in their practices. Also many other European countries have functioning health care without private insurances, which disproves the point they are necessary.
Do You Want to Die in an ICU? Pandemic Makes Question All Too Real
I came to the same result three years ago by writing the exact same problem into x86-64 asm, I guess I didn't think of it as something worth of sharing.

https://github.com/franciscouzo/nbody-asm
Same! I would love to read that
If you try to "predict the present" based on the past (and when you use previous points to calculate velocity and acceleration, that's what you're doing) it will overshoot when there's a change in direction, and how much depends on how aggressively you try to extrapolate. For the one-dimensional case in signal processing, doing this with a quickly-changing signal like a square wave will result in ringing.

It can smooth things a bit but it's not that good a substitute for actually improving latency.

(There are probably consequences for coronavirus charts as well, since they're based on lagging data.)
Instead of node_modules containing source code of the packages, yarn generates a pnp.js file which contains a map linking a package name and version to a location on the disk, and another map linking a package name and version to its set of dependencies.

All the installed packages are stored in zip form in .yarn/cache folder to provide a reproducible build whenever you install a package from anywhere. You can commit them to version control. Unlike node_modules, they are much more smaller in size due to compression. You will have offline, fully reproducible builds which you can test using a CI before deployment or pushing code to repository

https://yarnpkg.com/features/zero-installs
I do believe you'll need significantly more than that, but would be happy to be convinced otherwise.

As for the encouraged economic risk-taking: we'd see that in Europe, wouldn't we? We don't. Maybe putting a damper on how much of the reward for taking the risk you get to keep decreases the willingness to take it in the first place.

We're seeing pretty similar effects: multi-generational poverty, very low social mobility (lower than in the US according to some studies). We're just "keeping the social peace" by doing more redistribution, it does not appear to change anything beyond the immediate redistribution.
Okay, let's burn more karma. Maybe there is some hidden variable that makes these young people more susceptible to covid. Correlation without a model of action is, well, a correlation. Clots from damaged lungs maybe? But clotting without lung damage is unlikely. It's very weird.
They imagine to be living through a pandemic as well?

Amazing. What nerves these people have.
>I'd much rather mow my lawn with a mower than a pair of scissors.

I think you didn't go far enough with the implications of Carse's statement. It's not just that a machine mows your lawn quicker, it's that you have a homogenous lawn in the first place because it is a thing that can mechanically mowed.

For example, why instead of a lawn do more people not have a wild garden, with uneven terrain? Why did everyone feel compelled to put a green square, empty plot of land in front of their houses? is there anything interesting or alive in it, or does it exist because it can be mechanically operated? Given that mowing the lawn is something 'you want to get over with', is it not more accurate to say the lawnmower needs you shoving it around in a system that efficiently maximises lawn-mower production?

To understand the implication of what Carse is saying is to understand that machines don't just enter your environment, they shape your entire perception in a way that makes it conducive to be further operated by machines.

Is living in estranged suburbs with lawns really positive for human flourishing, or is it in a sense the logic of the car and the lawnmower operating on people rather than the other way around?

Is all the corn really part of a diverse diet and ecosystem, or have we adopted the diet because it is the thing that can be mass-produced?
Compute once when the window is created or resized is what happened, yes, but that doesn’t work when using them for buttons (unlike MS Windows, where every control is a ‘Window’, on Mac OS controls inside a window didn’t have their own drawing context), or when using them for window content (e.g. in a drawing program)

And remember: the original Mac had about 28 kilobytes of RAM free for applications. The system unloaded icons, code and fonts that were available on disk all the time. Few objects were ‘tiny’ at the time.
That might be referring to Yarn's "offline mirror" feature. When enabled, Yarn will cache package tarballs in the designated folder so that you can commit them to the repo. When someone else clones the repo and runs `yarn`, it will look in the offline mirror folder first, and assuming it finds packages matching the lockfile, use those.

This takes up _far_ less space than trying to commit your `node_modules` folder, and also works better cross-platform.

I wrote a blog post about setting up an offline mirror cache a couple years ago:

https://blog.isquaredsoftware.com/2017/07/practical-redux-pa...

Used it on my last couple projects at work, and it worked out quite well for us.
I have doubts about how this could possibly work. The idea is you pull a .ts file directly, right? Then your local ts-in-debo compiles that to extract typedefs for intellisense/etc and the JS. What happens when it was created for a different version of typescript than what you’re running? Or if it was created targeting different flags that what you’re using? This will cause lots of problems:

I’m running my project with ts 3.6. Library upgraded to 3.7 and adds null chaining operators. Now my package is broken. In node land, you compile the TS down to a common target before distributing so you don’t have this problem.

Similar, I’m using 3.8 and package upgrades to 3.9 and starts using some new builtin types that aren’t present in my TS. Now my package is broken. Previously you’d export a .d.ts targeting a specific version and again not have this problem.

Or, I want to upgrade to 3.9 but it adds some validations that cause my dependencies to not typecheck, now what?

Or, I’m using strictNullChecks. Dependent package isn’t. Trying to extract types now throws.

I’ve brought these all (And many other concerns) up to the deno folks on numerous occasions And never gotten a answer more concrete than “we’ll figure out what to do here eventually”. Now 1.0 is coming, and I’m not sure they’ve solved any of these problems.
South America displays a nice lesson: the less communist a country is, the better the tap water.
Don't know of anything that works on the source code level but static analysis in profilers does that for the object code (ones I use are proprietary but I imagine something like V-Tune does this as well).
Really? Because everything I've seen from the media has massively understated how dangerous the virus is, while medical professionals and people actively dealing with this on the front lines are horrified.
South Korea blocks test kits for Iran on Saudi-funded TV's request
Yeah, I want mine served right this moment, no later.
Digging requires depth.
1 line modules aren’t depth.
> the approaches of Sweden and the state of Georgia prove not to be disastrous.

Sweden has a strong well being systems. People stays at home every winter during the flu seasons. In any given meeting there are a couple of employees working from home because they may have the flu.

To compare the social protections of Sweden that allow citizens to stay home when sick ALWAYS, not just for the current pandemic, with the USA approach of come-to-work-or-you-are-fired is not reasonable.

The USA should pay more to their employees, have better healthcare coverage, give paid leave, and forbid free lay offs. And then, it would be in a position to postpone, lets see for how long, the shutdowns in a pandemic.

Sweden without lock down: Workplaces -32%
New York with lock downs: Workplaces -48%

I have the fear that the same Americans that want the "Swedish approach to CoVid19" are the ones against the social safety nets that has made it possible.

- https://www.gstatic.com/covid19/mobility/2020-04-17_SE_Mobil...

- https://www.gstatic.com/covid19/mobility/2020-04-11_US_New_Y...
Very unlikely. Web components and React are trying to solve different problems, and the React team has repeatedly said this isn't going to happen.
A nice one line argument for type safety.
Configuration, by definition, modifies the software.

How much it modifies the software is determined by the software author. If there aren't limits imposed in your example (json) you're still going to get unexpected results. You'll have to limit what's accepted.

Also, what if I allow a config.py file then translate that to .json then back to python? That is no better than just allowing the consumption of a python source file and simply ignoring any disallowed code (again, limiting what is accepted).

I know it's vogue to say configuration as code is bad; that simply has not been my experience.
>The UHH is a fun read, yes, but the biggest real-world problem with the Unix Wars was cross-compatibility. Your Sun code didn't run on Irix didn't run on BSD and god help you if a customer wanted Xenix. OK, you can draw some parallel here between React vs. Vue vs. Zeit vs. whatever

POSIX is a set of IEEE standards that have been around in one form or another since the 80s, maybe JavaScript could follow Unix's path there.
I think there's a bias in the data because a) lots of people die from the respiratory symptoms before they get a stroke, and b) young people who get a stroke might not know how to recognize it/what to do about it, so they may just stay at home and die there and never get recorded as a COVID death.
The issue is this dichotomy people keep fabricating between the “textual” and the “visual.” This makes it seem like one is “better” than the other for all time and we just need to get to the bottom of it. That distinction is made up and is itself part of the problem, and what we should be focusing attention to: https://dl.acm.org/doi/abs/10.1145/3313831.3376731

A related point this work makes is this association people make between “visual” and “flow diagram” coding. Not all “visual” coding is flow-based.
So much this. I just moved to Germany and the difference in civil servants and general infrastructure is palpable compared to the US
Space Photos of the Week: Polychromatic Views of the Earth
How Dangerous Is 5G?
What is the best book for learning the nuances of x86 assembly?
Waiting to decide isn't necessarily the same as deciding nothing. For instance, now we know that COVID causes substantial blod clotting issues and that these are possibly the cause of fatality rather than SARS. This is super useful to know when deciding to treat you; I'm no doctor (that kind anyway) and this seems obvious.

So the later any specific case happens, the better the likely outcome. Multiply that by the number of cases, and it absolutely starts to make a lot of sense to wait to decide until you know more. Certainly the number of patients who come down with it in the Fall will have a lower fatality rate than the very first patients who got it, barring mutation that makes it more lethal for some other reason.

Gathering information takes time so delaying until that information exists isn't the same as winging it.
Or the 25 people you work with across 4-8 different teams that finally settled on something that can allow people of different teams to move around without a lot of anguish.
Curious what you have stocked up, mind sharing?
Do you have the source? Sounds like an interesting talk.
I suspect that we'll also see a lot of different policies, different implementation effectiveness, and adherence to recommendations/policies that don't map very clearly to outcomes.
That's a very interesting fact. It makes the stroke being caused by covid more plausible.
Comment almost sounds like it's about PID.
The problem I saw was how quickly you need to open up the permissions floodgates. I saw them live-demo a simple http server, and to do something as basic as that you need to open up full file system and network access. So if you’re doing anything like setting up a server (i.e. one of the core things one does when using a server-side scripting language), you’re back to square 1.
The most commonly mentioned flaw was/is the root daemon. That can be worked around with other tools. The command line and docker files are a bit clumsy as well. Many images have security flaws. It didn’t clean up after itself for a looong time, etc.

It doesn’t “suck,” and many of the ideas are compelling. But, the design and implementations could be better. I was interested in rkt until it was acqui-abandoned.
Silver lining to this COVID tragedy
The realization that wage theft is the biggest economic "waste" as contrasted with the common belief that labor doesn't deserve much compared to capital was eye-opening for me.
> keep the rest of us fed, clothed, and healthy

The problem is that merely being locked down is quite unhealthy in many ways. As anecdote, I'm drinking about twice as much, not exercising at all, canceling dental cleanings, and wouldn't go into a medical setting short of something obviously life-threatening. (And indeed, many people with stroke symptoms aren't going to the ER right away, which can easily be life-changing.)

One essay I just saw made the likely-valid point that the risk here is almost entirely concentrated in the population that's 60+ (and a few younger people with unusual medical conditions).

If so, a better plan than shotgunning the entire economy for a year or two may well be to figure out how to specifically protect those who are vulnerable, and let things run their course with the rest.

In any case, if something cannot go on, it will not. No way we'll be locked down in a year, no matter what pie-in-the-sky handouts are distributed.
Before the deluge of "But wait two weeks" comments, I just want to ask at what point we accept that the potentially of totally asymptomatic cases is insanely high, far higher than anyone thought?
If you want a laptop that runs Linux great out of the box, buy a Linux laptop. There are plenty of known dealers that sell them. System 76 getting the most press recently.

If you want to stick with a specific brand (eg. I usually buy Lenovo) the trick has always been to buy one gen back. Laptops are all custom hardware by nature and if the manufacturer isn't spending the time to make sure Linux works on it then it is up to the community, and they can't do it until it is available. Once available it seems to take a year or so to get everything ironed out (assuming it is a major brand popular among Linux users). This really applies equally well to small, token lines, like Dell's, as they are really only a few steps ahead of the community due to limited resources.
I think the point of the comment is: you should not be testing for this at all.

If your API works with promises, call .then() on what is handed to you. That's it. Don't make up emergent, untestable behavior on the spot.
That's awesome. Thanks!!
Cryptoindex AI Daily Predictions and News for 04/25/2020
You can compile React to Webcomponents with community tooling, the core framework just doesn't support them:

https://github.com/adobe/react-webcomponent

By "aren't really there yet", what do you mean? If you mean in a sense of public adoption and awareness, totally agree.

If you mean that they don't work properly, heartily disagree. They function just as well as custom components in any framework, without the problem of being vendor-locked.

You may not be able to dig in to the internals of the component as well as you would a custom build one in your framework-of-choice, but that's largely the same as using any pre-built UI component. You get access to whatever API the author decides to surface for interacting with it.

A properly built Webcomponent is generally indistinguishable from consuming any other pre-built UI component in any other framework (Ionic built a multi-million dollar business of off this alone, and a purpose-built framework for it).
Covid-19 attacks the whole body, including brain, vessels, you name it. They've found Sars-Cov-2 in eyelids. This is exactly why you want governments to be responsible and take precautionairy actions first, because we know next to nothing about this virus and effects. Those who claim otherwise are simply ignorant, because we all are. The science will come later.
Kim Jong Un Dead
I completely agree with this. That anyone defends the current employee based health care system in the US is insane to me. The perverse incentives rife in such a system alone should eliminate it in any serious discussion as a viable way to provide healthcare to people.