HomeAfter more fiddling with Vy, I gave up on that fourth (or is it fifth) attempt of a vi compatible editor.
Why did I gave up on that one ? Several reasosn :
1. Python is not right for this.
I only had a limited spare time to work on it, so I settled to use only python as the developing language, because python is quick to develop with. In this particular case however, python was too slow for dynamic rendering of the text. Or I was not good enough at making it quick.
2. Writing a rendering engine is quite difficult
Well, since I was starting from scratch, I had to do all the rendring myself (splitting the long lines, displaying the right portion of the text onscreen). It’s quite a daunting task and at some point, I found it too annoying. Not the kind of fun that I want.
3. Writing an abstract buffer engine is annoying
There are a few other places in Vy that were more annoying than I have expected to. Buffer management is one of them.
4. Not enough time for such a big task
All in all, I don’t have enough time and commitment to write a full-fledged editor compatible with Vi. So, time to recognise it :
Vy is a dead project.
But it kept me busy during my commute time, which is nice.
And I don’t give up on the idea of vi-compatible editors. Actually, I have just started yet another one, vi-Taste. This will be a topic for another blog post…
