Today, mawww expressed a quick observation about https://github.com/xi-editor/xi-editor
“I think the Xi model is misguided, I think in a way it is too technology centric.”
As many of other Kakoune users out there, I have a deep relationship with my tools and I particularly enjoy investing time to survey what’s going on in the “text editor” world.
So while my main focus is obviously Kakoune I frequently have a look at cool features provided by other editors (old and new).
When Xi was announced a few years back, I had mix feelings. And today, by reading mawww’s quote above, I’m glad to see that he shares a similar point of view.
On one hand, I really appreciate that so much efforts/design/research was poured into trying to find the perfect data structures to hold a buffer, how to get the best butter smooth experience for beautiful GUIs on different platform. I truly believe that Xi is a fantastic opportunity to explore what Rust can do.
At the same time, while skimming through the docs, the blog posts and the Github issues about Xi, I’m disappointed about how few discussions are geared toward usability, towards the end-user experience about what this editor will do. It’s like that they are building a Formula1 engine, but how the steering wheel and the brakes will work is not (yet) fully envisioned. Almost as is “plugins author will figure these stuffs out”.
So in a way, I feel like Xi is in the “emacs end of the spectrum”. Providing a strong technological platform but without much choices about how the final editor will behave. Meanwhile, I love that Kakoune vision is first about strong text-editing model (operations on multi-selections) without losing the performance side of things at the same time.
I see an opposition between a theorical world vs a practical one.
What’s your opinion on this?