skysight-inc/HackerNews huggingface dataset:
Becuase age and pre-existing conditions have such a huge effect, the overall IFR is going to vary depending on things such how effective measures are at protecting younger people vs. older people. Spain is likely to be particularly bad in this regard - their lockdown was one of the strictest in Europe and their care homes an absolute horror show: https://www.bbc.co.uk/news/world-europe-52188820
Use the Ungoogled version from https://chromium.woolyss.com/ or https://github.com/Eloston/ungoogled-chromium/
You're right. I tend to assume people that use the word 'literally' are using it incorrectly - as parent did.

It's sad, but an ineluctable truth, that this word is almost always misunderstood and misused.

In the (again, regrettable) common usage use of the word -- ie. 'almost all' -- the claim is likely valid.
We are not eradicating the virus, we are flattening the curve.

The goalposts have moved, I support lockdown on the original basis, not your fantasy, because it's not only physically impossible - we are not doing it politically or socially, so it's irrelevant.
clickbait..
People should save even in a healthy economy. You should always have emergency fund + additional saving to reach your goals.

Investors do save as well. Much more than average consumers. The difference is that average consumer doesn’t have enough to buy assets or diversify their saving as much as investors can do.
> Which companies own which IP address blocks is public information.

People are working from home! That's the entire context of this thread! They aren't using corporate IP addresses! And they don't do it when travelling either!

> Conferences are announced; advertised, even.

People travel for other things beside conferences. For example to a meeting or client site.

> That's OK, companies do a fine job publishing employee information all on their own.

Many don't do this.

> What is a benefit you can gain from knowing someone at some IP address opened your email?

I've already listed all these things.

> Can you get that benefit some other way, such as by looking in a phone book or viewing the company's website?

Yes, people not listed in a phone book or the company website.

You're listing exceptions, but they don't apply to everyone. If they don't apply to everyone then you can catch some people.

Try this to help yourself understand - people do in fact use tracking images. Therefore, do you think that maybe there's a benefit to doing this? Otherwise why do you think they do it?
That's strangely reminiscent of the gameplay from Stunt Car Racer on the Amiga...

You should definitely keep going with this!
The memory consumption, especially the semi-non-determinism relating to lazy evaluation, was the first thing that popped into my mind. But, as I said in a comment below this, I think that Haskell as the common case language, with some FFI accessible code would probably fit the bill. I can not think of any large Haskell projects in the application space where browsers sit, but it doesn’t mean it couldn’t be done.
At some point, you do have to update the interface to move things forward. In the early days of programming, you had to manually punch cards. Then someone invented teletypes and you could program with ed. Then someone invented screens and you could use vi. No doubt each of these changes were incredibly jarring on the first day, but the change was worthwhile overall -- using a visual editor is much more productive than managing stacks of punched cards.

If everyone took the approach of never making anything that would have to be learned, our field probably wouldn't even exist.
This doesn't actually address either of the points I raised. You still have to ration infection. You still create a government imposed class system. You still have your liberty dependant on whether or not you allow the government to infect you with a deadly virus. Even putting aside the myriad of ethical reasons that this is a bad idea. Your solution still doesn't have a way to deal with your non-immune class members seeking out infection because they can't/don't want to wait for their government virus ration.
So they're the best a man can get. I don't see a problem.
It's called "journalism", nowadays.
Why is storing all data normalized in a database important to you? Whenever I see an exceedingly complicated database schema, I know I'm most likely in for unfixable legacy DB warts and incessant schema updates for every little feature.

Hyperbole aside, the best option often is somewhere in between. I find that a relational database with columns for primary keys/relations/anything used in WHERE statements in the normal application path, and a json blob for everything else that's just attributes for the current row/object/document, makes for a very flexible and successful DB schema. You get all the strong relational consistency benefits of traditional schemas, plus the flexibility to add and modify features that don't require relation changes without touching the schema, and the ability to represent complex structures while still allowing ad-hoc and admin path queries to peek into them where necessary.

In fact, most "fully normalized" databases end up reimplementing a key/value store or twelve in there anyway (e.g. config settings, user attributes, and the like). Might as well just use JSON at that point.
Improve Elasticsearch Search Relevance by 80% with Bert
The front page of The New York Times for May 24, 2020
"You are allergic to xyz." is what you'll hear. And that's it. It doesn't actually fix the problem. They might prescribe a medication that helps in severe cases, but they generally don't give you advice like other comments here about fixing your mattress etc.
I'm not certain I buy that argument. Yes, the actual code of each test would be slower than usual, but the things around it, test harness, factories etc should get plenty of execution. And at least in our not so very good test code base, that is where most of the time is spent.
Why so shy? The site by itself is a gem. Bookmarked!
Python3 flask-restufl web back end
Idk why you were downvoted, this is totally true.
> In fact, it's possible you haven't realized what really went wrong yet.

Not only is it possible, I think it is very likely, although your explanation is something I can follow along with and very much appreciated.

> There are a few things that went wrong here, but the final red flag to notice is that you should never call a constructor directly with 1 argument directly, because it's just a different syntax for a C-style cast, which we know is dangerous due to its bypassing of safety checks—and this is true regardless of whether we're dealing with C++ constructs (like classes and constructors and such), which I think might be what you're realizing now.

Huh, interesting, I actually did not realize this. Is there a way to do this safely without creating an extra lvalue? I take it that there is no “extra explicit” keyword I can add to prevent this kind of accidental call, is there?

> I'm going to go out on a limb here and say that was another mistake, even though it "solved" your problem here: despite the widespread use, brace initializers are, in my experience, not a good thing

Yeah, I am not really a fan of them either :( Even I know of a bunch of caveats about them and C++ initialization is an extremely complicated topic…

> If you're reading this, you're probably noticing that you ended up with Instruction&& in the first place—that's probably not what you wanted, or at least not what you should've wanted.

No, but as you observed that it “works out” at some point in the pipeline so I obviously did not care to really figure out if this was what I wanted or not.

> And that's where we get to the heart of the issue: your real problem is that you used decltype. If I saw that during code review, I would force you to change it—and using it on declval is just adding more fuel to the ember.

Somewhat strangely, C++ seems like the only language where I would even consider to use such a construct. I think every other language just erases their types or simplifies them so you can be comfortable writing something like “Iterator i = collection.start” or “int size = collection.count” whereas in C++ you have some generic distance_type and it feels dirty to just work with a size_t or whatever you know the thing to be.

> IMHO you should only use the newer features if they solve an actual semantic problem for you, not merely because they minimize your typing.

A good point, but I would like to just mention that this was clearly an experiment in trying out the “latest and greatest” ;)

> Not to mention the slow compilation speed and lack of independent compilability.

Wait, you’re telling me my 100 line program shouldn’t take a dozen seconds to compile?!
"For example, maybe you want to improve your Thought Leadership."

Lol. We really have peaked.
Yeah, there’s a couple of them, but none of them seem to catch everything :(
> Since immutable values can't create cycles, no memory will be leaked.

this is not generally true. in a lazy language, you can certainly say:

main = mdo
y <- f x
x <- g y
return y

the requirement is simply that you don't inspect the value of x until later (f makes something, y, to use later; when you use y, it inspects x). x and y now have references to each other.
Yeah, your right => I did take this into consideration in the past and now you woke up once more those thoughts.

Still not optimal, as I have another PC/server involved which needs from time to time as well a lot of data (but more rarely).
There is Vivaldi, but I haven't checked whether they removed most google services.
I think it's incredible that a website and desktop computer can generate the kind of graphics in real-time that were state-of-the-art (and not real-time) "only" 38 years ago. I would show this to my friends, but none of them are technical so they'd just think it was a video that's playing.

Great work, thanks for sharing.

(And please fix the back button!)
Sony Vaio laptops used to have a 'jog dial': a combination dial and button (basically the same as a mouse scrollwheel/button). This provided a very convenient method of navigation, and this looks like a perfect use case for it!
the idea would be routine by routine you could turn on features.

So make this function functional with no side effects.

This function doesn't (overtly) use pointers.

etc...

At various jobs, we've done things like this with warnings.

Get a source file to compile warning free, then turn on -Werror
(this is done via compile flags, a different mechanism)
I've never found programming so relaxing as when working in languages where almost everything is immutable. I think we're living beneath our privileges here.
It’s not clear yet how reliable the antibody tests are. Antibodies fade over time, and we don’t know how long Covid-19 antibodies remain detectable in your blood. It’s quite possible that after 6 weeks or so, you’ll no longer have easily detectable levels of antibodies.
No, I'm just saying that what memory is allocated (as in the language) is not necessarily the same as the memory that is allocated as in your intentions.
It's possible to allocate (as in language) an array that is longer than what you really need,
and when you are done using some of the memory in that array you might not want to call any free/realloc functions in order to make the program faster.
So instead you might want to just remember that the memory is unallocated (as in intentions) even if it's still allocated (as in language).
And now there is a disagreement between you and the language on what memory is allocated.
No "memory-safe" language can make sure you don't accidently use memory unintentionally.
With that said, languages like Rust really give you helpful tools to minimize the unintentional memory accesses.
>> The original poster wanted to test something.

> The license for those VMs:
"b. You may use the software for testing purposes only.

Basically you (and Microsoft) agree?
Sadly just because a language has a quality implementation and lots of libraries available and so is suitable for application development from an engineering point of view doesn't mean that PHBs are going to allow it to happen at the workplace, for various business reasons.
Developers go where the money goes. The money goes where the users go. The users don't know the difference between a walled garden and a free ecosystem.
It’s available with another URL in YouTube, maybe it was re-uploaded:

“Code Break 9.0: Events with Macklemore & Scott Forstall”
https://www.youtube.com/watch?v=-bcO-X9thds

Forstall’s part (living in a tent in a park with his parents and brother, being able to afford only 2 minutes of warm shower per week):
https://www.youtube.com/watch?v=-bcO-X9thds&t=31m51s

Fish story specifically:
https://www.youtube.com/watch?v=-bcO-X9thds&t=35m54s
Ripcord is a Qt client for slack and discord which uses much less cpu and ram though.
Most of the time when people think they need NoSQL they don’t. But if you really do, and value your data, FoundationDB
Sometimes you just have to look at the hardware product. A company which solders in batteries, for example, is probably not big on maintainability. Likewise, it it takes a special tool to gain access, it's likely not been designed by maintainability motivated engineers. For software it's a little harder. I think having fewer options, fewer knobs, and a simpler intuitive structure is an indicator of a bias towards maintainability. Also, not having source is a definite barrier to maintainability.

BTW, I find it hard to believe that "_faster_delivery" and maintainability are in opposition. Most of us would agree that maintainable systems have fewer bugs at every stage. And experience has taught us that bugs, particularly subtle bugs, take a long time to find and correct.
> Disallowing opt-out hurts some of the people whose organs will be donated, while those people are still alive. If they have a strong objection which doesn't qualify for an exclusion, they have to spend their life feeling this lack of control and disrespect of their after-death wishes.

Doesn't opt-out also hurt people while they are alive, who are now pressured to remain vigilant about having to make sure they're not missing any forms, or their forms not being processed correctly, etc., spending their life feeling a lack of control where a single misstep results in disrespecting their after-death wishes?

And again, what's the problem with making the box-ticking obligatory e.g. when picking up a driver's licence, rather than making it opt-out?
I'll believe blogging isn't dead when more small blogs make the HN front page.
Citation for the shot police officer's name?

People seem to have chosen bad faith attack media and elected bad faith leaders. That's why the US, UK, and Brazil are doing particularly badly.
Let's build more (software) libraries
Chrome-first is a fancy way of saying not compliant with standards. Much like UE back in the day.
Sorry, no. High speed rail's main benefit is to increase capacity on existing lines by removing fast trains from the mix. Currently big gaps have to be left in front of the fast trains to allow them to run. The reduction in travel time is a secondary benefit.

I was unaware of this until I recently discovered Gareth Dennis on twitter, who is doing a fantastic job of making up for HS2 ltd's appallingly lacking public engagement "strategy".
Some years ago, I tried to replicate the ACM paper style in LaTeX: http://beza1e1.tuxen.de/acm_html/test.html

The biggest problem is floating figures. ACM papers have a copyright notice on the first page at the bottom of the left column. I have no clue how to do that with CSS.
DuckDB: An embeddable analytical SQL database
Yes but the point is that it's just a back of an envelope estimate. I'm amazed that it's been downvoted as it's actually a technique that's used in this way all the time, or at least was anyway. I don't know about now when everyone has a smartphone.
What is the “smart programmer” language in 2020?
Thinking about Python Paradox [1], which language has interesting design and seems to have a bright future because it is drawing a community of "smart pepole" now?

My background is data analysis and Julia seems very enticing (I also think there is a lot of good design in R's tidyverse).

While python in 2004 was great, when I was thinking about it now, the adjective that I come up with is "tedious". It is my main lang at the moment though.

[1] http://www.paulgraham.com/pypar.html
HSR was never about commuting, capacity is too low, the journey time improvements are modest and tickets will always be priced to discourage commuting. It's a bone to throw to those people who currently travel longer distances to London, who are currently using slower rail, driving or flying. This group includes all the MPs from north of Birmingham, as well lots of rich Tory voters, and it was thought that it would carry the same appeal as the channel tunnel does for Londoners - reduced journey time and hassle for very occasional trips. They missed several real opportunities with it though - proper connection with the existing HSR to Europe would have played into the eco / flight shaming crowd, but it didn't fit the Brexit message. Linking it to a program of speed improvements on connecting commuter rail would have been a cheaper vote winner that would have boosted the value of HSR2 too. The whole project was a giant misguided waste of our money even before covid19 made public transit irrelevant, and with the rise of self-driving and environmentally friendlier cars only a crazy stubborn government would place a multi-billion pound on continuing HSR2.
with my "use strict" perl example, the warnings had some carveouts.

For example it had a carveout so that "$a" and "$b" didn't have to be declared (I think they are known variable names for sort?)

Why not allow:

printf("Hello world\n");

but turn off:

acpi_ut_repair_name(&(*converted_name)[j]);

or

if (atomic_read(&(*per_cpu_ptr(sdd->sds, cpu))->ref))
> At 2% a day cases double every 5 weeks. Would anyone apply this reasoning to any other disease?

I don't know but maybe the flu [1]? I don't think focusing just on the infection rate is useful.

> Classic psychological denial is clearly operating in force.

I think the denial is in thinking that we can beat the virus by extending the lock down for years (you say "might take two or more years"). It is likely that all we are doing is slowing down the spread, and that it will eventually infect most of the population, stopping only when we reach herd immunity. I say this is likely because this is where we are headed unless we come up with a vaccine or treatment at an unprecedented speed -- not something I would bet on.

If this is indeed where we are headed, it may be better to open up as much as possible short of overwhelming the healthcare system. Note that in many places, the healthcare systems are significantly below capacity (e.g. [2]).

[1] https://www.who.int/docs/default-source/coronaviruse/situati...

[2] https://www.sccgov.org/sites/covid19/Pages/dashboard.aspx
Thank you - looks interesting, but they don't write in the specs if it has an active fan or not, right? (e.g. I see in the pics that this random model has fans https://mikrotik.com/product/crs328_4c_20s_4s_rm#fndtn-downl... but they're not mentioned in the specs)
No, you sort of walked past their point.

A thing can happen zero times (never). An example might be 1+1 =0. You could get really unlucky with cosmic rays or something, but really adding two registers, both containing 1, that result isn't going to be zero unless there's some sort of hardware failure.

A thing can happen once. an example might be, you can delete a file once. There are ways to get unlucky, of corse, but once it's unlinked it's gone.

if it happens more than once, you really should probably think about an unbounded number of times. now days, that sorta means 2^64 times. There will be bugs when something overflows int64, but I hope you get the gist.

The parent comment is talking about invariants you can use in an algorithm.

I think you might be worried about python vs C or something along those lines. Really, it should all work with a pencil and paper. Which is obviously going to be slower than pushing around electrons. But if you can find those invariants, 0-1-many, you can make a better algorithm. If you're stuck with a pencil it'll still make that faster.
Run-Length Encoding
Maybe the details of suffering they want to write are more graphic, but standards and the need to prevent public anxiety means that they write in a measured clinical-technical detail.
Non-paywalled syndicated version here:

https://stockshours.com/2020/05/24/a-lost-struggle-to-mine-a...
I got an iPad last summer and that made me dare to switch to iPhone last fall. I like both a lot.

Recently I found out that iMusic is available outside of the Apple ecosystem as well.

I wonder if Apple will - sooner or later - start targeting Windows and Linux with the rest of their software as well? (I know I can read and edit iCloud files online but I am thinking of native apps.)
For a lean mobile view add ".compact" to the end: https://old.reddit.com/r/hnblogs/.compact
I came across Ainu culture while driving through Kuchiro in Hokkaido. We stayed one night in the city, unbeknown to us it was the night of their yearly Marimo festival [1].

Marimo is an extremely odd moss ball that only grows in their lake [2]. Once to the brink of extinction, the Ainu celebrates every year by strolling around the city with the prettiest marimo. They celebrate through the night with traditional dances. It was a unique experience.

[1] https://ohmatsuri.com/en/articles/hokkaido-marimo-matsuri

[2] https://en.wikipedia.org/wiki/Marimo
There is an proposal for a GC-library: https://docs.google.com/document/d/1Cv2IcsiokkGc2K_5FBTDKekN...

That is just like programming in D with extra steps.
Banning visits to the elderly in care homes in late March is better than Singapore, which amazingly didn't ban them until the start of April: https://www.straitstimes.com/singapore/no-visitors-allowed-a... (This was back when the press elsewhere were still pointing to Singapore as the coronavirus success story everyone else should follow. The first foreign news story noticing the warning signs was literally that day, and the existing narrative carried on for a while elsewhere.)
D has been steadily focusing on solving memory safety problems. It now has a prototype ownership/borrowing system incorporated into the language.
Neither automatic bounds checking nor GC really add slowness. Any reasonably safe program will check the bounds explicitly, so there is no speed gained vs. guaranteed bounds checking via the compiler. Actually any good compiler can remove most bounds checks, if it can proove that the access is in bounds. Also GC can be quite faster than manual dynamic memory management.
Sounds like delay line memory.
Sticky blood, thrombosis, brain inflammation... not hard to read past the clinical language.
"Mao was long dead when the relevant treaties were negotiated"

We're discussing the option communist China had to take HK back by force. The point is thus why that did not occur in 1949 or the 50s.
Nitpick but could have adopted the kv-storage API instead: https://github.com/WICG/kv-storage
I remember the Rockbox firmware for MP3 players having something similar. I was (and am still) amazed how efficient the UI/navigation was in relation to how limiting the (hardward) controls were on some of those players. It took a little while to understand how it works, but that tiny bit of learning curve was well worth it.
Throttled background tabs and the case for elevator music
Sure, all we need to do is rewrite billions of lines of code in some of the most popular software on the planet.

And then replace it with... a language that is exactly as performant, is available on every known platform and has replacements for all the existing libraries (including all the ones written in C!).