nw.js VS xi-editor

> FUSE drivers are slow, but "wildly slow" is an overstatement.

I can confirm this, I've played RPGMaker M{V,Z} games natively by swapping out the copy of NWJS¹ it shipped with and running it through a CIOPFS² mount.

1: https://nwjs.io/

2: https://www.brain-dump.org/projects/ciopfs/ / https://github.com/martanne/ciopfs

Go to this page to download NW.js https://nwjs.io/.

(Step 7 will not be necessary once https://github.com/nwjs/nw.js/issues/5769 is completed)

The support for WebGL in NW.js on Linux has been broken since NW.js 0.72.0: https://github.com/nwjs/nw.js/issues/8043

In addition to the other options here you could look at nw.js

I don't think you can access it by default, but crosscode runs on [nw.js](https://nwjs.io). I know there is a way to get the chromium devtools to open, but I haven't been able to.

or browse the NWJS home page at https://nwjs.io/

If windows is your target, you can use .hta If Ubuntu is your target, you can use GJS If Mac is your target - well you are going to use something like QT if you need total control or nwjs.io

BrightSign has pretty good docs that explain this. There are a ton of similarities to running NW.js, so it might make sense to check that out as well (https://nwjs.io/). DM me if you have more questions. My team and I have built a few Node applications for BrightSign players.

Was confused until I realised I'd confused Zed, with Xi[1] which is also rust based, and which incidentally has a frontend called "Xim"..

Also there's a wiki-editor (like Tomboy[2]) called "Zim"[3].

[1] https://github.com/xi-editor/xi-editor

Project site linked from the GitHub[0] is https://xi-editor.io. Linked doc is a mirror of this[1], which was afaik originally written by Raph Linus.

[0]: https://github.com/xi-editor/xi-editor

[1]: https://xi-editor.io/docs/rope_science_01.html

> thing that gets deleted when you hit backspace

Is there a canonical source for this part, by the way? Xi copied the logic from Android[1] (as per the issue you linked downthread), and I vaguely remember that CLDR had something to say about this too, but I don’t know if there’s any sort of consensus here that’s actually written down anywhere.

[1] https://github.com/xi-editor/xi-editor/pull/837

This is pretty much how copy-on-write ropes work. Check out xi-rope, Ropey or crop, they're all built using B-trees and implement the behavior you described.

Helix is awesome, though once Lapce (spiritual successor to Xi editor) gets the Helix/Kakoune editing model, I may have to jump ship

Home (xi-editor.io)

Maybe take a look at the Xi editor (https://xi-editor.io/) (written in rust I think) that uses a client server architecture.

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...