Hacker News new | ask | show | jobs
by psd1 2 days ago
A delay of two seconds in my commit hook pushes my blood to the hydraulic pressure of a 70-ton digger.
4 comments

Commit hooks just don't make that much sense. Push hooks are much better idea. Once you're done with all your work, linting, last minute adjustments and whatnot, push it and get the checks result. If something goes wrong, your push is blocked.
In user experience land, 2000ms is not tiny, it's catastrophic.

In interactive software, a single dropped frame is noticeable and irritating. Programming is an interactive experience.

> A delay of two seconds in my commit hook pushes my blood to the hydraulic pressure of a 70-ton digger.

Why though? Surely you have it set up to lint as you edit? I know my neovim installation does that and I see the results in the editor as I type.

If it's a rule that linting needs to be in the commit hook, maybe the linter should write a hash of the files linted somewhere. The commit hook script then only lints those files that have changed since the last lint took place.

Then have it run asynchronously when you save