Hacker News Reader

IO bound compiler would be weird. Memory, perhaps, but newer CPUs also tend to be able to communicate with RAM faster, so...

I think just having LSP give you answers 2x faster would be great for staying in flow.

View on HN

Compiler is usually IO bound on windows due to NTFS and the small files in MFT and lock contention problem. If you put everything on a ReFS volume it goes a lot faster.

Applies to git operations as well.

by "IO bound" you mean "MS defender bound"

Dev Drive can help with that as well

I've seen gcc+ld use a large amount of disk (dozens of GB) during LTO.

Reply on news.ycombinator.com