We get the beauty of every file that’s modified
being scanned before the write “completes”. It’s an absolute joy starting a build and watching ~80% of the available compute be consumed by antivirus software.
Or, you know, normal filesystem caching as part of your tool’s workflow.
Oh, you get the benefit of explicit scanning?
We get the beauty of every file that’s modified being scanned before the write “completes”. It’s an absolute joy starting a build and watching ~80% of the available compute be consumed by antivirus software.
Or, you know, normal filesystem caching as part of your tool’s workflow.
Or dependency installing and unpacking…
Or anything actually that touches a lot of files.
Yeah was experiencing that for awhile, a couple of workarounds: