That’s pretty low bar for calling something a “quirk”. The whole ML family, so OCaml, SML, Haskell, F# and perhaps a the new distant relative Rust call it also it None.

And it’s not even the same thing: null means pointer to nothing, while None means no value.

How is None a quirk?

In theory, yes. But if you follow the link and that leads to downloading the JS and running it, you’re already too late inspecting it.

And even if you review it once (and it wasn’t too large or obfuscated via minification), the next time you load a page, the JS can be different. I guess there could be a web browser extension for pinning the code?

The only practial alternative I know of is to have a local client you can review once (and after updates).

So the trick is to use the #fragment part of the URL, that is not sent to the server.

Of course the JS one downloads from the server could easily upload it to it, so you still need to trust the JS.

If you want to have multi-host redundant storage at home (via e.g. minio or ceph), S3 is a pretty good protocol to provide it.

S3 is nice in the way it’s not a file system so it can have relaxed semantics, while also providing secure access to individual files over HTTPS via URL signing.

Some people seem to be stuck in the idea that S3 means cloud hosting. Not sure if that was your view, but it’s worth spelling out sometimes.

Papermerge version 2.0, version 2.1 and version 3.0 are entirely different and incompatible applications.

That doesn’t exactly inspire confidence in the future versions of this application, given in particular the use case of long-term document archival :).

It doesn’t actually detect moved code, though, like git diff can? I gave it a shot and also there’s a couple issues open about it, e.g. https://github.com/Wilfred/difftastic/issues/520 .

Other than that, difftastic is quite nice.

Just keeping a single frame buffer image can take tens of megabytes nowadays, so 100MB isn’t all that much. Also 64-bit can easily double the memory consumption, given how pointer-happy the ELISP data structures can be (this is somewhat based on my assumptions, I don’t actually know the memory layouts of the different Emacs data structures ;)).

But I don’t truly know, though. If I start a terminal-only Emacs without any additional lisp code it takes “only” 59232 kilobytes of resident memory. Still more than I’d expect. I’d expect something like 2 MB. But I’ll survive.

It comes from the words “Eight Megs And Constantly Swapping”.

Yeah, the name hasn’t aged well…

^Zkill -9 %1 is the only way.

kill -9 -1 if that doesn’t work.

There is the DJVU format for this exact use case, but you’d need to convert them to, say, pdf for many use case. Its also a bit old and perhaps not maintained, soo…

HEIF and other modern video encoders (HEIF=H265) should fare a lot better than JPEG, though.

No always-on display and waterproof rating only to 1m instead of 30m, though 😞.

Nevertheless, quite interesting. Maybe at some point new more capable hardware will arrive.