iota
xi-editor
Our great sponsors
iota | xi-editor | |
---|---|---|
3 | 42 | |
1,608 | 19,805 | |
- | 0.1% | |
0.0 | 2.6 | |
over 1 year ago | about 1 month ago | |
Rust | Rust | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
iota
- Micro – A Modern Alternative to Nano
- Iota: un editor de código escrito en rust
-
CPU May Have Slowed Down on Wednesday
> but I'm sure it won't be able to open a 1KB text file instantaneously in 5 years
Unless you decide to switch to a modern console-based text editor. It doesn't have to be vim or emacs. There are many other alternatives. One new such editor written-in-Rust being Iota: https://github.com/gchp/iota
xi-editor
-
Zed is now open source
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].
-
Text Editor: Data Structures
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.
-
The Absolute Minimum Every Software Developer Must Know About Unicode in 2023
> 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.
- Google abandons work to move Assistant smart speakers to Fuchsia
-
What's is a rusty way to implement sharable trees?
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 (a Kakoune / Neovim inspired editor) 23.03
Helix is awesome, though once Lapce (spiritual successor to Xi editor) gets the Helix/Kakoune editing model, I may have to jump ship
-
Editors written in rust
Home (xi-editor.io)
-
How to share resources between instances of program?
Maybe take a look at the Xi editor (https://xi-editor.io/) (written in rust I think) that uses a client server architecture.
-
Suitable Rust GUI Library for Code Editor?
Have a look at what Lapce uses. The editor is coming along nicely, and iirc, they use the Xi editor as a plug-in.
-
CRDTs make multiplayer text editing part of Zed's DNA
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...
What are some alternatives?
rust-doom - A Doom Renderer written in Rust.
helix - A post-modern modal text editor.
mdBook - Create book from markdown files. Like Gitbook but implemented in Rust
alacritty - A cross-platform, OpenGL terminal emulator.
rim - Aspiring vim-like text editor
lapce - Lightning-fast and Powerful Code Editor written in Rust
oso - Oso is a batteries-included framework for building authorization in your application.
Servo - Servo, the embeddable, independent, memory-safe, modular, parallel web rendering engine
parity-bitcoin - The Parity Bitcoin client
kakoune.el - A very simple simulation of the kakoune editor inside of emacs.
xsv - A fast CSV command line toolkit written in Rust.
rust-genetic-algorithm - A genetic algorithm for bechmark problems, written to learn Rust.