Vitest may not be a good drop in replacement either. It uses Workers for multi-threading via Tinypool. For us, we use the AWS SDK and the binaries in it would cause Vitest to crash. After wasting a lot of time, we had to retreat back to Jest.
I really like Vitest, and it's a great fit for lots of projects. I'm a bit sad it wasn't for ours.
Big fan of vitest, I like typescript and esm support out of the box and without adding dependencies like types/jest or ts-jest. I've filed bugs and pull requests and the maintainers have been responsive
It is most definitely not drop in. I looked into this yesterday funnily enough and you can expect to have to make many syntax changes to your test files.
It's an _almost_ drop in replacement - when I tried migrating our tests recently (because of memory leak issues / slowness resulting from Jest + a Node upgrade) I found I had to manually finagle a lot of our mocks to get them working.
I keep on meaning to finish a redesign of the oeis site that I started a few months ago[0]. I've only spent a day on it so far, but I'm hoping it makes the site far more approachable to new comers.
Some feedback: it lacks a search button. I mean, you can type a sequence, but have to hit the enter key to search. I'd expect at least some mouse-pressable button to be there that searches too (either the magnifying glass that's already there, or a button labeled "search").
You may say that "it's good enough you can press enter", however the site starts out already showing you the digit sequence "1, 2, 3, 6, 11" so you don't need the keyboard, but no way to actually search for it using only the mouse.
Second feedback: it shows icons that look like a maple leaf in the top right without any explanation what it means, perhaps a tooltip could show what this maple leaf means? Idem for the other icons there.
Third feedback: you have to individually click a full expand and then in addition expand all the subsections to view them... at least a dedicated page to entries should show everything immediately.
Final most important feedback: it doesn't have individual URL's to the sequences anymore! That seems an important missing feature. It only shows results in ephemeral rendered boxes on the main page, no way to link to an individual entry! Clicking an entry should open its individual page. Middle mouse clicking should open it in a new tab like a real link does.
This was incredible feedback, thanks so much for taking the time to write it out. I've implemented 2, 3 and 4. You can now directly link to pages[0] and it'll auto-expand all boxes. The icons are intended to show whether the sequence has a code submission attached. There's now a popover attached to them to explain this.
1 will take some design work, and I've only got an hour or so to work on it now. I definitely agree however that a 'submit' button on a search is essential.
There's clearly the intention to self-host, they seem to be waiting for support to ingest data from a GitHub data export which seems pretty reasonable.
`/dev/urandom` isn't a real file / stream. It's part of the 'everything is a a file' *nix mantra. Even if two users are reading from /dev/urandom simultaneously, they'll each get unique values. The CSPRNG keeps track of a sequence number and so you'll end up with something like [process 0 requests sequence 0, process 1 requests sequence 1, process 1 requests sequence 2, proceess 0 requests sequence 3...].
Chrome can actually bypass HSTS if you enter the super secret code in the security warning screen. The code is changed regularly though, you'll have to check chromium source code to get the current bypass code. (e.g. https://chromium.googlesource.com/chromium/src/+/refs/tags/1... )
Very useful for testing but don't make a habit to use it on some random websites.
The number also appears to include 'upstream' energy usage, things like how much energy was used to transport food to you. How much energy to produce the items you consume. I imagine raw household electrical usage is only a small fragment of this.
1.0.0.1 is owned by Cloudflare and is used for their DNS offering. It's likely a reliable 'ping' candidate for checking that your machine has internet access
All those 'kazillion' images are processed into a single 'model'. Similar to how our brain cannot remember 100% of all our experiences, this model will not store precise copies of all images it is trained off of. However, it will understand concepts, such as what a unicorn looks like.
For StableDiffusion, the current model is ~4GB, which is downloaded the first time you run the model. These 4GB encode all the information that the model requires to derive your images.
[0] https://vitest.dev/