From 0a2a823ef2e6e45376b17bd9ab9bdcbea74c6345 Mon Sep 17 00:00:00 2001 From: Brian McGee Date: Fri, 3 May 2024 16:05:47 +0100 Subject: [PATCH] doc: reduce use of anchors for Rust and Go in README Improves readability Signed-off-by: Brian McGee --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 967dc37..a09ec99 100644 --- a/README.md +++ b/README.md @@ -147,17 +147,17 @@ guidelines for more information. You may be familiar with [Version 1], which is written in [Rust]. So, why re-write it in [Go]? Ultimately, `treefmt` is spending most of it's time shelling out calls to the underlying formatters. This process is -just as fast/performant in [Go] as it is in [Rust]. +just as fast/performant in Go as it is in Rust. The remaining tasks are processing some cli args and parsing a config file. Do we really need something as _heavy duty_ -as [Rust] for that? +as Rust for that? -Despite all this, you can make good, sane arguments for continuing with [Version 1] in [Rust] instead of a re-write. +Despite all this, you can make good, sane arguments for continuing with [Version 1] in Rust instead of a re-write. So here's a _bad argument_. [Brian] wanted to improve performance by moving away from a [Toml] cache file, introduce pipelines for applying multiple -formatters against the same file set, and add an extensible approach for how `treefmt` walks file systems. He knows [Go] -much better than [Rust]. +formatters against the same file set, and add an extensible approach for how `treefmt` walks file systems. He knows Go +much better than Rust. [zimbatm] thought it was a good idea too.