There's also the problem that not every window in Tahoe has the same corner radius. Some people thought this was laziness/lack of polish or a bug, but Alan Dye confirmed on a podcast that it was intentional.

So then they're left with a conundrum: do they adjust the 19x19 region on a per-window basis, depending on the per-window corner radius, or do they stick with one standard drag region? Probably it should be the former, but that comes with its own set of issues.

Do you recall what podcast? I know hearing him say this was intentional is only gonna make me frustrated, but I’m dying to hear the justification for such a bad decision.

That's like asking, "if the title bar can have different sizes, should we make the hot area for moving the window also of different sizes?" The answer to both questions is "obviously yes!" The shape of the thing and how it responds to user input do not match by coincidence.

>What could be simpler than that?

At risk of being tongue-in-cheek, a monad is just a monoid in the category of endofunctors, what's the problem?

I'm not criticizing the content of this post, but the author is likely wrong about this specific initiative being called "Going Dark".

"Going Dark" has been the umbrella term various worldwide intelligence orgs have been using since the mid-2010s to describe their lack of access to encrypted communications. For example, here's FBI Director James Comey using the term in 2014: https://www.brookings.edu/articles/watch-fbi-director-james-... It's a coordinated broad branding effort by intelligence agencies across the west, but I doubt that this specific EU initiative itself has ever been called "Going Dark" even internally.

Maybe I'm weird, but one of the first things I've always done when setting up emacs is to enable Typo mode (or Typopunct) for writing modes, which handles typing en and em dashes and "smart" quotation marks in a fairly natural way.

I think there is room for non-gamified learning apps depending on the field and how it's intended to be used. A good example is the field of early reading instruction. The best two apps right now IMHO are Reading.com and Mentava, and they take radically different approaches. Mentava is pretty gamified and kids can use it on its own, whereas Reading.com is basically a computer implementation of Siegfried Engelmann's instructional approach. Has to be used with a parent accompaniment, and most of the onscreen widgets are just there to facilitate co-teaching. Both apps are good and seem to be landing with their target markets, obviously the simpler one is aiming at a lower price point.

Poor gamification is a bigger risk than non-gamification done well IMHO. That's where a lot of children's learning apps have failed in the past.

The EL backlight adds to the slightly unearthly vibe too. The eMate was one of the last mainstream laptop-size devices made with an EL backlight. I miss those.

This is my view as well. That being said, Time New Roman is marginally better because there are several good, modern open source alternatives with the same metrics that can be substituted. And there's good tool support virtually everywhere for those alternatives, like in TeX.

There is a metric-compatible open alternative to Calibri (Carlito) but it seems more vulnerable to lawyer shenanigans and doesn't have extensive tool support.

Which Times New Roman alternatives would you recommend?

I know a few people who use Quantrix for financial modelling. It is an exceptionally nice piece of software, basically the successor of Lotus Improv, with Improv's more robust and auditable separation of data and formulas.

This is what I recommend too, but for those who want something prepackaged, there's also XigmaNAS, basically a lightweight UI layer and basic configuration on top of FreeBSD. Some of the original FreeNAS developers have been working on the project for almost 20 years.

It's great for people who just want storage and don't want the heavy features that came with TrueNAS' move to Linux (Kubernetes, etc.) or who want full control over vfs_fruit options for serving Macs.

Are you sure it's not called LigmaNAS?

That might be a better name :) The project doesn't have as much visibility as it should because it's gone through several names over the last 20 years: FreeNAS (prior to the TrueNAS split), NAS4free, and now XigmaNAS.

There are a couple recent developments in ZFS dedup that help to partially mitigate the memory issue: fast dedup and the ability to use a special vdev to hold the dedup table if it spills out of RAM.

But yes, there's almost no instance where home users should enable it. Even the traditional 5gb/1tb rule can fall over completely on systems with a lot of small files.

Nice. I was hoping a vdev for the dedup table would come along. I've wanted to use optane for the dedup table and see how it performs.

I think the asterisk there is that the special vdev requires redundancy and becomes a mandatory part of your pool.

Some ZFS discussions suggest that an L2ARC vdev can cache the DDT. Do you know if this is correct?

Yes, that's the reason why a dedup vdev that has lower redundancy than your main pool will fail with "mismatched replication level" unless you use the -f (force) flag.

I'm not sure about whether an L2ARC vdev can offload the DDT, but my guess is no given the built-in logic warning against mismatched replication levels.

Well, the warning makes sense with respect to the dedup vdev since the DDT would actually be stored there. On the other hand, the L2ARC would simply serve as a read cache, similar to the DDT residing in RAM.