describe is also the command you can use to edit the commit message of the change you're currently drafting. In jj there's no staging area, every modification to the working tree immediately gets integrated into the current commit. (This means if you have no diff in your working tree, you're actually on an empty commit.)

Depending on what NPU you have yes.

It was definitely a relatively well known problem with the 2019 MBP on the internet at some point. I found a Reddit thread linking to a news article about this. https://www.reddit.com/r/mac/comments/vi3grj/you_should_char...

It was so much of a problem that at work we added a check that you were charging from the right ports to our internal doctor script (think like `brew doctor`).

I help out with an emulation community. Any time anyone with a 2019 MBP comes in with issues, I stop them from giving any more details and just have them check this first.

99% of the time it works 100% of the time.

I think you may be confusing Agent Client Protocol with Agent Communication Protocol.

At the very least schools should be billed for the frivolous police callouts. Who knows, maybe then the school might change their tune.

I would've considered signing up if scrolling on your website didn't make my modern flagship phone drop frames.

Firefox haven't removed XSLT support yet.

I should've worded differently. By the narrative of this website, Google is "paying" Mozilla & Apple to remove XSLT, thus they are "controlled" by Google.

I personally don't quite believe it's all that black and white, just wanted to point out that the "open web" argument is questionable even if you accept this premise.

The problem is that the web is no longer really "open". Google kind of controls most of it right now. Just look at all the admoney influx.

Pale Moon still has XSLT support and has no plans to remove it: https://outerheaven.club/notice/AxFlFCfzzgRRpvubVw

It’s a joke.

git very much supports symlinks. Although depending on the system config it might not create actual symlinks on Windows.

IIRC that's actually a change in upstream pip.

> Indeed, while Chrome is displaying the dialog, it blocks all Chrome extension popup windows from appearing.

We discovered this one the hard way at work. I keep learning this the hard way myself because I've been working on browser extension dev lately. I don't understand how this could possibly be an intended feature.