Optimizations and profiling (fix draw line numbers, coroutines)

src/backup/todo.txt

@@ -1,11 +1,13 @@
 - What precise workflow do I need for me to be viable to use this?
 - From a user (novice) point of view, how does it look like?
 
+- Optimization:
 - Show what process/coroutines are running and allow to kill (active process buffer?)
 - ctrl + p like in VSCode (without special buffers)
-    - I THINK WE NEED A SPECIAL VIEW, this is too slow
-    - Move to the top so that it can be progressively expanded using coroutines by appending at the end
     - Maybe 2 windows?
+- Database idea: use special buffers to store information
+    - Editing the buffer doesn't seem to be the slow part rather, accessing the data and putting it into the buffer (potentially hitting many different memory locations) I have a crazy idea to use buffers in order to store the names in a serialized format
+    - non editable buffers (raw ops ok, non-raw no op)
 - Guide on the first page for new users with links to configs, tutorials
 
 - Why constraint that name of buffer needs to be unique? For Open() and default behavior but is this required?