I would like them to have mercurial's awesome hg fa --deleted when it comes to history trawling, but apparently for it to work well, they also need to swap out git's diff format for mercurial's smarter one, so I'll be waiting on that for a while I suppose.

I don't use capslock for ctrl though. It's much too useful as the Compose key ;)

Of those choices, I prefer Ubuntu as being closer to the Debian/Devuan ones.

https://news.ycombinator.com/item?id=45274277 (Apple Photos corrupts images on import - images truncated)

At home, I run a mix of Devuan and Gentoo.

At work, primarily Devuan with some Ubuntu where COTS only officially supports Ubuntu or Redhat.

When GNOME 3 was first released, I gave it an honest try for several months but it just did not do what I wanted in a UI. MATE competes well with XFCE on memory usage, still has optional acceleration, and had a more consistent interface with more features (although XFCE has improved). And the fact that those in the family don't have to learn a new layout really helps.

These days she uses MATE which still offers that Gnome 2 layout. Awesome thing about Linux is that option to fork, so her desktop environment has remained consistent for over 20 years.

Given the great energy densities and stability in transport of hydrocarbons, there's already some plants out there synthesising them directly from green sources, so that could be a solution if we don't manage to increase battery densities by another order of magnitude.

If it was a random JS error, well, that reminds me of: https://www.kryogenix.org/code/browser/everyonehasjs.html

    UTF-8 always has the same byte order,[5] so its only use in UTF-8 is to signal at the start that the text stream is encoded in UTF-8...
    Not using a BOM allows text to be backwards-compatible with software designed for extended ASCII. For instance many programming languages permit non-ASCII bytes in string literals but not at the start of the file. ...
   A BOM is unnecessary for detecting UTF-8 encoding. UTF-8 is a sparse encoding: a large fraction of possible byte combinations do not result in valid UTF-8 text.

https://scoop.upworthy.com/when-mythbusters-tried-to-fold-a-...

The same issue hit the initial efforts (that I think were the inspiration for jj) when the mercurial folks, recognising git had kinda taken over the market, experimented in making a mercurial frontend backed by the git db. Limitations like the diff format (mercurial's weave one is one the jj folks also want to add at some point) and the lack of a method for tracking phases (mercurial relies on this for clean history without throwing out commits), and lack of file move/copy tracking.

He did find a pretty good substitute for the primary cocoa leaf ingredient though. Also, what he made was virtually indistinguishable in the taste tests. One person said that his tasted closer to the 2L of coke than the can of coke did, which suggests the final bit could just be carbonation level of the soda stream.

The Chrome PDF parser, originating from Foxit (now open-sourced as PDFium), has been the source of many exploits in Chrome itself over the years.

I grabbed the nightly firefox, flipped the jxl switch, and it does indeed render fine, so I guess the rust implementation is functioning, just not enabled in stable.

... also, I see no evidence that it was ever enabled in the stable builds, even for the C++ version, so I'm guessing Zen just turned it on. Which... is fine, but maybe not very cautious.