bastien/VimsCode
1
2
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity

correction readme

Browse source
This commit is contained in:
bastien 2023-05-22 10:26:26 +02:00
parent 4f33cf72e2
commit 34bdbe470f
1 changed files with 20 additions and 19 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

39
README.md
View file

@ -8,34 +8,35 @@
1. Why change 1. Why change
To write or edit computer code, program an arduino etc... we use IDE (integrated development environment) To write or edit computer code, program an arduino etc... we use IDE (integrated development environment)
Many very complete graphic software exist to do that like VScode from microsoft or Atom. Many very complete graphic software exist to do that like VScode from microsoft or Atom.
So why not use them ? They have drawbacks: So why not use them ? They have 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 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 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) * They don't work without a graphical system (through ssh, on a server or a Raspberry Pi)
* It is sometimes difficult to make them do something simple if it was not planned by the developers * It is sometimes difficult to make them do something simple if it was not planned by the developers
* Its frequent updates sometimes impose changes in working habits (new interfaces, new default configuration, new paths etc.) * Its frequent updates sometimes impose changes in working habits (new interfaces, new default configuration, new paths etc.)
So which solution? We suggest you use one of the historical command line text editors (vi, Vim) to make your own IDE :) So which solution? We suggest you use one of the historical command line text editors (vi, Vim) to make your own IDE :)
Advantages :
Advantages :
* Lightweight, ~15Kb which is 4.6 x less than Apollo 11 and 83000 times less than VSCODE!!! * 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 * 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...) * 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...)
* Usable through SSH on servers or very light computers (Raspberry Pi, etc.) * Usable through SSH on servers or very light computers (Raspberry Pi, etc.)
* Rock solid, crashes must exist, but I've never even heard of them * Rock solid, crashes must exist, but I've never even heard of them
2. Avantages of this solution 2. Avantages of this solution
VimsCode is an IDE with vim for beginner or expert VimsCode is an IDE with vim for beginner or expert
* VimsCode use arduino-cli, idf-esp and platform.io-cli for remplace VScode only in terminal * VimsCode use arduino-cli, idf-esp and platform.io-cli for remplace VScode only in terminal
* Very easy to use * Very easy to use
* Very easy to install * Very easy to install
![Example-picture](/pictures/image.png) ![Example-picture](/pictures/image.png)