From 00209a7dad1d2e88d522ba7218947ffb0c7d6ce4 Mon Sep 17 00:00:00 2001 From: bastien Date: Mon, 22 May 2023 11:15:01 +0200 Subject: [PATCH] test --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 2f79716..9313c8a 100644 --- a/README.md +++ b/README.md @@ -15,6 +15,7 @@ So why not use them ? **drawbacks :** + * They are resource intensive, lots of RAM (~1.3 GB, about 18,000 times more than the Apollo 11 mission that sent the first men to the moon :/ ) * They are quite difficult to debug because of the large abstraction layers that make them up * They don't work without a graphical system (through ssh, on a server or a Raspberry Pi) @@ -24,6 +25,7 @@ So which solution? We suggest you use one of the historical command line text editors (vi, Vim) to make your own IDE :) **Advantages :** + * Lightweight, ~15Kb which is 4.6 x less than Apollo 11 and 83000 times less than VSCODE!!! * Configurable, you can configure everything in text files from already shared and popular configurations * Stable, it only evolves without breaking the ergonomic continuity (always the same commands and shortcuts since 1991 for vim and 1976 for vi :) same for the configurations which remain valid since the beginning...)