xi-editor VS alacritty

Have a look at what Lapce uses. The editor is coming along nicely, and iirc, they use the Xi editor as a plug-in.

Raph Levien posted a retrospective about using CRDT’s for collaborative editing in xi-editor here [1]. His conclusion is

“I come to the conclusion that the CRDT is not pulling its (considerable) weight. When I think about a future evolution of xi-editor, I see a much brighter future with a simpler, largely synchronous model, that still of course has enough revision tracking to get good results with asynchronous peers like the language server.”

[1]https://github.com/xi-editor/xi-editor/issues/1187#issuecomm...

Maybe architect kernel as a microservice? There was some text editor developed as a microservice; I don't see why it couldn't work for a FX application or game engine.

A while ago there was a post about Zas Editor, an editor for mac that used parts of Xi as the backend. Since then, the website has been taken down and it's presumably abandoned. There was some apprehension about its licensing but it was cool.

I thought that after the failure of the https://github.com/xi-editor/xi-editor project (which Lapce seems to take inspiration from) people would stop trying it, but looks like it's doing the opposite.

Why not collaborate with developers of existing code editors such as Xi Editor (https://xi-editor.io) or Lapce (https://lapce.dev) instead of making yet another one?

As for lightweight alternatives to Atom, there is also Lite-XL (https://lite-xl.com).

My initial thoughts are using something like the xi-editor or parts from it for text manipulation, some rust GUI framework for rendering, like egui or iced, for more language contextual actions like autocomplete I think I'd have to look into the LSP.

Oh I didn't realize that it might have been a serious question, I'm too unfamiliar with the domain to not make stupid misinterpretations it seems, really sorry about that. Anyway no, that's a good suggestion, I think starting there makes the most sense but I'm having some decision-anxiety about where to start. I think xi-editor is likely to be the best place to start constructing an editor without making the project impossible to finish

Maybe a different terminal emulator like iterm2 for one with tons of features or something like kitty or alacritty for a lighter weight terminal.

More info on the main issue tracking this https://github.com/alacritty/alacritty/issues/62

https://github.com/alacritty/alacritty do you have any idea on how this could be useful?

https://github.com/alacritty/alacritty/issues/109

Maybe I'm a bit harsh, but you see a lot of programs require work arounds.

Alacritty is simple and fast[0] (it does have mouse support, but no tabs, sessions, or startup scripts as far as I know. Configuration is all via config file.).

Is that the kind of thing that you were looking for?

[0] https://github.com/alacritty/alacritty

I'm not sure how current that article is - in that article they state that the alacritty team had created an issue relating to latency[0] which was closed in favour of a different issue[1] which is still open.

The newer issue[1] appears to state that latency isn't an issue on Wayland as it already has frame scheduling support, but their proposed fix targets X11, MacOS and Windows.

I was quite surprised as I hadn't noticed any latency using alacritty, but I've been on Wayland for some time so that might be the reason.

[0] https://github.com/alacritty/alacritty/issues/673

[1] https://github.com/alacritty/alacritty/issues/3972