UPD: oh, heck, attested passkeys are actually already in the protocol. Why can't we just have nice things?

I disagree. It is just a wrong statement. Passkeys actually eliminate the flaky autofill part where password managers have to parse input fields. Ever since I learnt about KeePassXC and KeePassDx, I've tried to migrate as much of my accounts to passkeys. The experience is wonderful and KeePass allows me to see the private key behind the passkey - yes, yes, yes!

[1]: https://www.inkandswitch.com/essay/local-first/

Even better: they moved it from developer options to accessibility options, which means that they treat it as a normal use case now

What is bad is that it still disables the animations for progress bars (the only place where the animation makes sense)

Handwritten bash scripts using git-replace and git-filter-repo [1] did a much better job

[1]: https://github.com/newren/git-filter-repo

I get their motivation to remove the flag. In fact, it has always been better to run xattr in postinstall, this way the binary is free from quarantine even after updates.

But the way they communicate with people is unacceptable and just unnecessary.

One major thing I appreciate about the official Zig Language Reference is that it is no-pagination single html page that I can ctrl+f https://ziglang.org/documentation/master/ I wish more projects published their docs like that.

When I read, my mouse is busy selecting different parts of the text that I'm thinking about.

1. I don't want to move my mouse off the text to click the "next" button.

2. I don't want to move my mouse off the text to expand TOC items.

3. I don't want to waste my time on switching between pages back and forth.

I prefer the raw text on a long scrollable, non-interactive page with TOC on the side.

Otherwise, great to see more guides on the Zig topic.

Comments URL: https://news.ycombinator.com/item?id=41626562

Points: 1

# Comments: 0

Though you can use git branches, but I prefer not to

I rename .git directory to .dotfiles in my $HOME

Well, you can't have different configs for different hosts. Other than that, I can't quickly recall what other limitations are, I see none. I really like the simplicity of the "pure git" approach.

My dotfiles repo dates back to 2018, I'm happy user of this git one-liner for the past 6 years.

    git -c status.showUntrackedFiles=no --git-dir=$HOME/.dotfiles --work-tree=$HOME "$@"

I specifically don't like how painfull Apple does it. (Google for "notarization hell macos")

This is my pet project that I do for fun and for free. Bowing my head to Apple every time I want to release a new version is not fun. Waking up in the middle of the night, because Apple revoked the app (https://github.com/nikitabobko/AeroSpace/issues/167) is not fun.

AeroSpace is a tool for developers by developers. Developers can audit the code and install the app from sources

The complexity of the config has grown since then, with the bigest (and, actually, the only) problem being on-window-detected callback as you mentioned.

I've been thinking about using a scripting language like Lua, but I haven't made my mind yet whether it's worth it

Given this layout:

    h_tiles
    ├── window1 (focused)
    ├── window2
    └── window3

    h_tiles
    ├── window1 (focused)
    └── v_tiles
        ├── window2
        └── window3

2. I myself consider the virtual emulation of workspaces to be the strongest feature of the AeroSpace. If I could disable the workspace switching animation in yabai or Amethyst (with SIP enabled, of course), I'd probably not bother myself creating AeroSpace. That's what the "space" part in the app name means. It resembles the strongest feature of AeroSpace - workspaces