commit af6f3a7430867df0127be6e1d059a5477495a20e parent fdab2c5ff30947c640c70023e5b8b9dac6758b3d Author: Simon Gardling <Titaniumtown@gmail.com> Date: Fri, 1 May 2020 18:56:03 -0400 Update README.md with performance information Title's self explanatory. I timed paleofetch and neofetch, and though it is a good idea to put that in the readme. Diffstat:
| M | README.md | | | 8 | ++++++++ |
1 file changed, 8 insertions(+), 0 deletions(-)
diff --git a/README.md b/README.md @@ -4,6 +4,14 @@ paleofetch A rewrite of [neofetch](https://github.com/dylanaraps/neofetch) in C. Currently only supports Linux and Xorg. + +Why use paleofetch over neofetch? +----------------------------------------- +One major reason is the performance improvement. For example: neofetch finishes running after about 222 milliseconds where as paleofetch can finish running in a blazing fast 3 milliseconds. + +Note: this testing occured on only 1 computer, it's not a good representation on the performance benefit you may gain. + + Example output: 