test
This commit is contained in:
parent
8d96e0c750
commit
bd21c0ffb9
|
@ -14,7 +14,7 @@
|
|||
|
||||
So why not use them ?
|
||||
|
||||
##### drawbacks :
|
||||
**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)
|
||||
|
@ -23,7 +23,7 @@
|
|||
|
||||
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!!!
|
||||
* 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...)
|
||||
|
|
Loading…
Reference in a new issue