Simon Žlender

When I'm scrolling in `Direct` mode the Metal HUD shows the min FPS exactly 60 and max FPS exactly 120. To me it seems like variable refresh rate doesn't work...

- The `display-link` branch in `Direct` mode feels much smoother now. However the `Composited` mode is now the laggy one. - In the Metal HUD I still see FPS alternating...

> Whoa, that's really interesting. On my M3 I get variable FPS, up to 120fps, but it's never really exact. I'm going to later try this on the M1 I...

> That does look like it's working as intended though, right? FPS is variable between 60 and 120hz here. No, the FPS shown is average FPS. If I have one...

> Ah, I see what you're saying. It's not really variable, but only flipping between 60 and 120hz? Yeah exactly. Afaik MacOS has an API for Adaptive Sync which is...

It's interesting to me that your `max` FPS is going up to 575FPS. Is that right? For me it never goes above exactly my refresh rate (120fps with ProDisplay, or...

Some thoughts: - From what I can tell, this only does plain http auth, but most services these days authenticate through headers. GitHub (`Authorization`), GitLab (`Private-Token`/`Job-Token`), etc. So ideally there...

Another issue with the current lock file is that it causes nix to needlessly re-evaluates equivalent inputs. For example if we have two inputs `A` and `B` that both depend...

I looked into fixing the performance implications of this (without touching the lock file format) in [#10218](https://github.com/NixOS/nix/pull/10218).

> Here is my take: It should be bundled but $PATH should be preferred. Otherwise `direnv exec /some/path command` will not work in case nix is not in $PATH. Also...