Learning up to 12x12 is commonplace in the U.S., and apparently in other English-speaking countries, too

https://en.wikipedia.org/wiki/Multiplication_table#Modern_ti...

Primary sources are not allowed on Wikipedia. Wikipedia is a tertiary source

https://en.wikipedia.org/wiki/Wikipedia:No_original_research...

I forgot Wikipedia has nothing to do with science.

> such as the fact that a safe subset exists, but depends on GC,

@safe works perfectly fine and exactly the same in @nogc code as in GC-enabled code.

My mistake - SafeD was introduced since I stopped using D, so I was going off this article:

https://dlang.org/articles/safed.html#safed-subset

> When you enter SafeD, you leave your pointers, unchecked casts and unions at the door. Memory management is provided to you courtesy of Garbage Collection.

Does D provide the necessary tooling to be able to expose a safe API for something which needs to allocate memory, without needing a GC?

You are stuck with dropping to @trusted and calling the appropriate allocator API.

Following that you will want to check for null ext. to make it actually @safe in practice and not just typed as such.

That's a bit disingenuous. Memory allocations in D require either GC or non-local unsafe code.

I'm aware that D has @live, a WIP attribute that mimics Rust semantics, but it's not remotely ready for production.

I use Refined Hacker News[0] to get a list of past threads at the bottom of the page. dang himself has said[1] it overlaps surprisingly with their internal extension, so it might prove useful

[0]: https://github.com/plibither8/refined-hacker-news

[1]: https://news.ycombinator.com/item?id=20176460

For me, this was caused by a buggy service worker; unregistering the service worker (from about:debugging > "This Firefox" > "Service Workers" on Firefox, dunno how on Chrome) should fix the issue

From further down in this thread: https://decrypt.co/62217/monty-pythons-john-cleese-mints-bro...

From what I understand, Firefox has a lower precision timer, which means you need to do more cache timer repetitions; try increasing it to 400,000, it should look more like the demo (though it still doesn't generate two entirely separate curves).

If Chrome suddenly stopped sending referrer headers, let's be real here, 99% of websites would be fixed within a couple of days at most.

Restoring the internet would be a pretty geeky and tinker-y mission on its own

Agreed! I had a recent experience with no internet and was running around my house yanking coax cables, checking my electrical cupboard and whacking the router.

Turns out, there was a line issue outside my house :P

Posix file names can be any sequence of bytes other than '/' and 0

I guess that's true. I suspect the support for non-UTF8 names in modern tooling is very, very spotty, given how many config files and file formats that refer to other files use UTF-8 themselves. E.g. can you refer to one of these names in an nginx config? (just an example; I have no idea if its config is UTF-8 or not)

I have a collection of non-utf8 and other problematic files to test such tools:

https://github.com/benibela/nasty-files

You probably cannot clone the repo on Windows. It works well on Linux. But in KDE you could not delete it after checkout

Also, filenames with one or more newlines bork a lot of Linux software.

And Windows file names can include unpaired surrogates, which are not allowed in UTF8 (that’s why WTF8 exists).