[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-5406":3},{"id":4,"name":5,"fullName":6,"owner":5,"repo":5,"description":7,"homepage":8,"htmlUrl":9,"language":10,"languages":9,"totalLinesOfCode":9,"stars":11,"forks":12,"watchers":13,"openIssues":14,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":15,"stars7d":16,"stars30d":17,"stars90d":15,"forks30d":15,"starsTrendScore":16,"compositeScore":18,"rankGlobal":9,"rankLanguage":9,"license":19,"archived":20,"fork":20,"defaultBranch":21,"hasWiki":20,"hasPages":22,"topics":23,"createdAt":9,"pushedAt":9,"updatedAt":24,"readmeContent":25,"aiSummary":26,"trendingCount":15,"starSnapshotCount":15,"syncStatus":27,"lastSyncTime":28,"discoverSource":29},5406,"xi-editor","xi-editor\u002Fxi-editor","A modern editor with a backend written in Rust.","https:\u002F\u002Fxi-editor.io",null,"Rust",19821,706,391,135,0,1,11,70.15,"Apache License 2.0",false,"master",true,[],"2026-06-12 04:00:25","# Xi editor\n\n***Maintenance status:*** *The xi-editor project is currently discontinued. Although we will happily accept bug fixes, no new features are currently planned. You may be interested in [the Lapce editor](https:\u002F\u002Fgithub.com\u002Flapce\u002Flapce), which can be considered a spiritual successor to the xi-editor.\n— The Editors\n\n***Note:*** *This repo contains only the editor core, which is not usable on its own. For editors based on it, check out the list in [Frontends](#frontends).*\n\nThe xi-editor project is an attempt to build a high quality text editor,\nusing modern software engineering techniques. It is initially built for\nmacOS, using Cocoa for the user interface. There are also frontends for\nother operating systems available from third-party developers.\n\nGoals include:\n\n* ***Incredibly high performance***. All editing operations should commit and paint\n  in under 16ms. The editor should never make you wait for anything.\n\n* ***Beauty***. The editor should fit well on a modern desktop, and not look like a\n  throwback from the ’80s or ’90s. Text drawing should be done with the best\n  technology available (Core Text on Mac, DirectWrite on Windows, etc.), and\n  support Unicode fully.\n\n* ***Reliability***. Crashing, hanging, or losing work should never happen.\n\n* ***Developer friendliness***. It should be easy to customize xi editor, whether\n  by adding plug-ins or hacking on the core.\n\n**Learn more** with the creator of Xi, Raph Levien, in this [Recurse Center Localhost talk](https:\u002F\u002Fwww.recurse.com\u002Fevents\u002Flocalhost-raph-levien\n).\n\nScreenshot:\n\n![xi-mac screenshot](\u002Fdocs\u002Fdocs\u002Fimg\u002Fxi-mac-screenshot.png?raw=true)\n\n\n## Getting started\n\nThis repository is the core only. You'll also need a front-end, from the list\nbelow.\n\n\n### Building the core\n\nXi-editor targets 'recent stable Rust'. We recommend installing via [rustup](https:\u002F\u002Fwww.rustup.rs).\nThe current minimum supported version is 1.40.\n\nTo build the xi-editor core from the root directory of this repo:\n\n```\n> cd rust\n> cargo build\n```\n\n\n## Frontends\n\nHere are some front-ends in various stages of development:\n\n* [xi-mac](https:\u002F\u002Fgithub.com\u002Fxi-editor\u002Fxi-mac), the official macOS front-end.\n\n* [xi-gtk](https:\u002F\u002Fgithub.com\u002Feyelash\u002Fxi-gtk), a GTK+ front-end.\n\n* [xi-term](https:\u002F\u002Fgithub.com\u002Fxi-frontend\u002Fxi-term), a text UI.\n\n* [xi-electron](https:\u002F\u002Fgithub.com\u002Facheronfail\u002Fxi-electron), a cross-platform front-end based on web-technologies.\n\n* [Tau](https:\u002F\u002Fgitlab.gnome.org\u002FWorld\u002FTau), a GTK+ front-end written in Rust. Forked from https:\u002F\u002Fgithub.com\u002Fbvinc\u002Fgxi, which was abandoned.\n\n* [xi-win](https:\u002F\u002Fgithub.com\u002Fxi-editor\u002Fxi-win), an experimental Windows front-end written in Rust.\n\n* [kod](https:\u002F\u002Fgithub.com\u002Flinde12\u002Fkod), a terminal frontend written in Golang.\n\n* [xi-qt](https:\u002F\u002Fgithub.com\u002Fsw5cc\u002Fxi-qt), a Qt front-end.\n\n* [vixi](https:\u002F\u002Fgithub.com\u002FPeltoche\u002Fvixi), a Vim like front-end in Rust.\n\nThe following are currently inactive, based on earlier versions of the front-end\nprotocol, but perhaps could be revitalized:\n\n* [xi_glium](https:\u002F\u002Fgithub.com\u002Fpotocpav\u002Fxi_glium), an\nexperimental GL-based front-end in Rust.\n\n* [XiEditorVS2015](https:\u002F\u002Fgithub.com\u002FSineaggi\u002FXiEditorVS2015), C#.\n\n* [xi-android](https:\u002F\u002Fgithub.com\u002Fadrientetar\u002Fxi-android), an Android frontend.\n\nThere are notes (I wouldn’t call it\ndocumentation at this point) on the protocol at\n[frontend.md](https:\u002F\u002Fxi-editor.github.io\u002Fxi-editor\u002Fdocs\u002Ffrontend-protocol.html). If you're working on a front-end, feel free to\nsend a PR to add it to the above list.\n\n\n## Design decisions\n\nHere are some of the design decisions, and motivation why they should\ncontribute to the above goals:\n\n* ***Separation into front-end and back-end modules***. The front-end is responsible for presenting the user interface and\n  drawing a screen full of text. The back-end (also known as “core”) holds the file buffers and is\n  responsible for all potentially expensive editing operations.\n\n* ***Native UI***. Cross-platform UI toolkits never look and feel quite right. The\n  best technology for building a UI is the native framework of the platform.\n  On Mac, that’s Cocoa.\n\n* ***Rust***. The back-end needs to be extremely performant. In particular, it\n  should use little more memory than the buffers being edited. That level of\n  performance is possible in C++, but Rust offers a much more reliable, and\n  in many ways, higher level programming platform.\n\n* ***A persistent rope data structure***. Persistent ropes are efficient even for\n  very large files. In addition, they present a simple interface to their\n  clients - conceptually, they're a sequence of characters just like a string,\n  and the client need not be aware of any internal structure.\n\n* ***Asynchronous operations***. The editor should never, ever block and prevent the\n  user from getting their work done. For example, autosave will spawn a\n  thread with a snapshot of the current editor buffer (the persistent rope\n  data structure is copy-on-write so this operation is nearly free), which can\n  then proceed to write out to disk at its leisure, while the buffer is still\n  fully editable.\n\n* ***Plug-ins over scripting***. Most text editors have an associated scripting\n  language for extending functionality. However, these languages are usually\n  both more arcane and less powerful than “real” languages. The xi editor will\n  communicate with plugins through pipes, letting them be written in any\n  language, and making it easier to integrate with other systems such as\n  version control, deeper static analyzers of code, etc.\n\n* ***JSON***. The protocol for front-end \u002F back-end communication, as well as\n  between the back-end and plug-ins, is based on simple JSON messages. I\n  considered binary formats, but the actual improvement in performance would\n  be completely in the noise. Using JSON considerably lowers friction for\n  developing plug-ins, as it’s available out of the box for most modern\n  languages, and there are plenty of the libraries available for the other\n  ones.\n\n\n## Current status\n\nThis is still a project in its early stages. The Mac build has basic editing\nfunctionality (it was used to write this README), but looks very spare and\nis still missing essentials such as auto-indent. At the moment, it’s expected\nthat its main community will be developers interested in hacking on a text\neditor.\n\n\n## Authors\n\nThe xi-editor project was started by Raph Levien but has since received\ncontributions from a number of other people. See the [AUTHORS](AUTHORS)\nfile for details.\n\n\n## License\n\nThis project is licensed under the Apache 2 [license](LICENSE).\n\n\n## Contributions\n\nWe gladly accept contributions via GitHub pull requests. Please see\n[CONTRIBUTING.md](.github\u002FCONTRIBUTING.md) for more details.\n\nIf you are interested in contributing but not sure where to start, there is an\nactive Zulip channel at #xi-editor on https:\u002F\u002Fxi.zulipchat.com. There is also\na #xi channel on irc.mozilla.org. Finally, there is a subreddit at\n[\u002Fr\u002Fxi_editor](https:\u002F\u002Fwww.reddit.com\u002Fr\u002Fxi_editor\u002F).\n","xi-editor 是一个采用 Rust 语言编写的现代文本编辑器后端。该项目旨在通过先进的软件工程技术构建高质量的文本编辑工具，追求极致性能、美观界面、高可靠性和良好的开发者友好度。其核心功能包括快速响应的编辑操作（所有编辑操作均在16毫秒内完成）、利用最新技术进行文本渲染以支持Unicode全字符集展示，并且易于定制和扩展。尽管目前xi-editor项目已停止更新，但它为多种操作系统提供了前端实现，适合对编辑器性能有高要求同时又希望拥有良好用户体验的开发者使用。",2,"2026-06-11 03:03:07","top_language"]