Servo VS xi-editor

I pulled last changes to see the new tabs and surprised by RTL support because few weeks ago not supported

I see there PR merged: https://github.com/servo/servo/pull/33148

Don’t think this really fits in with HN guidelines.

Seriously, check out https://servo.org , they post monthly updates and the progress seems great. And their repo, too - too bad GitHub can’t display code frequency because there’s too many commits in the project.

Here's the (relatively small) commit: https://github.com/servo/servo/pull/32477/commits/d9b842ff6e...

It's using the par_iter() method from Rayon, a Rust data-parallelism library: https://docs.rs/rayon/latest/rayon/iter/index.html

Rust is definitely used in Firefox, but Servo[0], which was going to be the replacement browser engine (or at least the testbed for that), was abandoned by Mozilla, in a limbo for some time and now under new stewardship.

On a meta-level, I think the story that people like to tell is that Mozilla chose increasing executive compensation rather than using the same money to keep the Servo (and people working on Rust itself) employed.

[0]: https://servo.org

The following Mastodon toot is about https://servo.org that could become another alternative. Quote :

"Servo is faaaar from ready for general use yet, but it's picking up development speed. Definitely an option to keep an eye on for the future. "

Why is Ladybird getting so much attention. Has anyone herd of servo? They're trying to offload css rendering to the gpu. That could be a big deal in the long run.

https://servo.org/

Does anyone know, how it compares to Servo?

https://servo.org/

Check what is happening in Servo (https://servo.org). Some active members also want something very modular, and this is helped by work being actively done to use the engine in various contexts.

I use memory saver on Chrome and it helps substantially but Chrome just doesn't feel right. It might be the most secure browser out there but performance is lacking. Modern software should be more efficient than this. There is open-source Rust browser engine in the making called Servo (https://servo.org/), I hope they eventually come up with more efficient browser.

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