For the rope, are you using xi-rope, ropey, or did you roll your own? Any thoughts on how you made that decision?
Glad to see stuff like this, it brings back memories.
back
1 comments
Hi Raph. It amazing to see you here and thank you for all the xi crates.
> Any thoughts on how you made that decision?
The reason behind that is Zas Editor started out as a fork of Xi Editor! We're also using a fork of xi-rope, though we haven't made many changes to it.
If you would like to discuss this more, DM me at twitter @ZasEditor
What do you think of the "no such thing as native GUI" section of the xi retrospective [1], particularly the surprisingly bad performance?
[1]: https://raphlinus.github.io/xi/2020/06/27/xi-retrospective.h...
From a purely macOS perspective, the major issue (apart from JSON being slow in Swift) was that there's no good native editor control for source code. There's NSTextView but it doesn't scale to large, syntax highlighted documents and lacks the required facilities that a source code editor needs. Hence, all proper third party text editors for macOS write their own source code control. I, personally, would contest that a native GUI is very much possible, but only for the chrome of the editor (e.g. searching, menus). This is also where native GUIS can shine. I'd wager that a proper source code control is such a domain specific requirement that each cross platform editor has to implement them whether they use native UI or not (maybe Qt has a fantastic one, I don't know)