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?

Alas my game PC is going to stick with Windows due to bad state of VR in Linux :/. And therefore one day it might need to update to Windows 11.

In particular if you have a headset that is not Valve Index, though apparently with Meta Quest one can use ALVR, as long as you get the actual games running.

Boox Tab Ultra

Looks pretty nice device! Even the camera makes a bit sense in the demo they give (though apparently in practice the scanning rarely works). And cheaper to boot as well. I might consider getting this one.

But is the display really better quality? Atleast the DPI is slightly higher at 219 on the Boox Tab Ultra vs 190 on the Daylight. And Boox weighs 70 grams less, and that’s the device some reviews call heavy (and some lightweight…).

These reviews mention the slow display speed:

• https://www.xda-developers.com/boox-tab-ultra-review/
• https://www.techradar.com/reviews/onyx-boox-tab-ultra-review-an-e-ink-peg-in-an-ipad-hole even goes to describe it “distracting” and “Performance can’t keep up with fast typing”
• https://www.trustedreviews.com/reviews/onyx-boox-tab-ultra “Tab Ultra does let you choose between several refresh modes” and https://www.makeuseof.com/onyx-boox-tab-ultra-review/ "The HD preset works fine for casual reading, whereas the balanced mode works better when thumbing through documents or typing. Meanwhile, the fast mode is suggested for general website browsing, and ultrafast is more useful for video playback. "—surely if the display was always fast and working, this fidgeting would be pointless?

So perhaps there is some room for improvement? That being said, some other reviews don’t mention it and one says it’s faster than typical e-ink display, though that doesn’t sound immediately purely praising.

In the end it probably comes to the software: how fast it is, it well it works, how nice it is to use. It seems both have customized the standard Android, so I suppose the difference is in which one has done it better and which one has better custom apps. Per the reviews Boox doesn’t fare too well in this aspect. Maybe someone will make a comparative review of the devices.

As opposed to buing a separate display for the computer?

I like to think this thing would be nice reading the news while having a breakfast or reading an e-book outside or at the bed, not near my computer. So it makes a lot of sense to build a tablet with this display technology.

Zooming and panning a pdf is arguably more comfortable with higher frame rate.

Would that kind of provision allow me to have my code removed from a git repository history, if that git repository is hosted by a company?

I suppose they could implement smooth panning in high fps even if actual updates would be slower… though it might look funky.

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.

I was under the impression cross-site cookies are a standard feature per the RFC, though? Or is Patreon using some kind of non-standard extension?

It still loses to HgBa2Ca2Cu3O8+6 with Tc = 133–138 K at normal air pressure, though. (I assume it’s normal air presure as the article doesn’t say the pressure for it, while it refers to some others as high-pressure ones.)

Maybe LK-99 still has other benefits, such as not using mercury.

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.