Hey @theintercept! Yes, it is a paywall. Just because I’m paying with access to my inbox instead of money doesn’t mean I’m not paying.
| Blog | https://withbugs.blog/ |
| Blog Comments | https://mastodon.social/@withbugs |
@CtrlZvi
- 5 Followers
- 17 Following
- 31 Posts
@nikitonsky “I’ve been mentioning HIG a lot, and you might be wondering: is an interface manual from 1992 still relevant today?”
Manual from 1992? What about the manual from 2025? https://developer.apple.com/design/human-interface-guidelines/icons
Sure, they’ve relaxed the guidance about text in icons and made some other changes, but most of what you said is covered and is against the guidelines.
They even provided which icons to use for which purposes for some of the specifically problematic situations you found!
@roguelazer When did you get them? I thought AB 144 (went into effect September 17) required California insurance to cover COVID vaccines?
@0xabad1dea My head cannon is they have a really weird bug that somehow makes pointer values count as “places” to prevent reverse engineering of their… WebASM?
@0xabad1dea This one gives me very much boss fight against Beelzebub vibes.
@b0rk Given this new mental model, I can now say that I will be using (but have not yet) `git reset <commit> <file>` to stage a partial revert. This seems like it will be much nicer than my current processes of either using `git revert` followed by more commands to drop the commit but keep the changes I want (usually at least an interactive rebase) or `git restore` followed by `git add`.
@b0rk This new knowledge made me curious about the difference between git-reset, git-checkout, and git-restore. Why do we have all three?
A quick search led me to https://yanbo.wang/2022/04/24/git-checkout-reset-restore/. That coupled with a (slightly) more thorough read of the documentation leads me to following (simplified) conclusion:
• git-reset is for editing the state of the index
• git-restore is for editing the state of the working tree
• git-checkout is for editing/synchronizing the state of both
A quick search led me to https://yanbo.wang/2022/04/24/git-checkout-reset-restore/. That coupled with a (slightly) more thorough read of the documentation leads me to following (simplified) conclusion:
• git-reset is for editing the state of the index
• git-restore is for editing the state of the working tree
• git-checkout is for editing/synchronizing the state of both
@b0rk I try to give each git subcommand a single conceptual purpose in my brain. I’ve assigned “undo git add” to git reset. So I use git reset <file> quite a bit to unstage a specific file without losing its changes. (I especially do this quite frequently in the middle of interactive rebases.)
Because I think of git reset as “undo git add”, I’ve never used it with a commit argument, though.
(In fact, I didn’t even know that was possible, so TIL.)
Because I think of git reset as “undo git add”, I’ve never used it with a commit argument, though.
(In fact, I didn’t even know that was possible, so TIL.)
@crash If an assertion/testing/logging library shipped with Kvetch as a level below Warning I would switch to it so fast!
@roguelazer I installed the Xcode beta (Xcode 26 beta 5) to try to play with some new SwiftUI stuff. I noticed a new Game Playground template in the New File from Template… dialog, so I added one to my project. Poked around for a few seconds, then was done with it, so I secondary clicked it, selected Delete, then selected Move to Trash.
Xcode crashed. Reopened, thinking I’d gotten into a bad state, saw it hadn’t been deleted, tried again, crashed.
The quality bar is gone now. 😔
Xcode crashed. Reopened, thinking I’d gotten into a bad state, saw it hadn’t been deleted, tried again, crashed.
The quality bar is gone now. 😔