That looks great. It should be made into a package/npm module
I don’t really know where to start… I started reading the atom docs from the opposite direction, and so the beginner area is still very undiscovered–technically I am less than a newb in that department.
If you would like to
git init the repo and npm or the apn project, feel free to add me as collaborator to the atom pkg. I would be more than happy to assist on any code review
what people may or may not realize is neither here nor there, so let’s defer to the facts:
- one node binding dependency alone calling into kernel API opens threads (cores) and what have you, since the binding just converts function arguments into whatever lame C++ V8 type is trending or thankfully it’s just an UN-null terminated C string, A.K.A.node’s buffer class.
You won’t be able to see any load on the editor even if you do a ton of work in the other process.
my thought exactly.
I had a separate process with a mirrored text buffer for each loaded file. Every time any typing paused the change was sent to the process and the buffer updated.