Closed vvirtues closed 11 months ago
might be just me, but at default settings, fastfetch destroys the competition
That was because the powershell interpreter was started and stoped in every run.
winfetch is pretty fast if you run it inside powershell interpreter. Try (Measure-Command { ./winfetch.ps1 }).TotalMilliseconds
Winfetch will be slower if you run it outside of PowerShell. It needs to initialize the .NET runtime during startup. The benchmarks assume this cost to be absent.
I did 5 different benchmarks using hyperfine to compare them, and each time neofetch was faster. Both are at their defaults and i used
-w 3
to warm them up. Is this true?