Search Results for "rust language"

A Kakoune / Neovim inspired editor, written in Rust. The editing model is very heavily based on Kakoune.

...Support for many languages via Tree-sitter, WebAssembly, and the Language Server Protocol. Fast native terminal tightly integrates with Zed's language-aware task runner and AI capabilities. First-class modal editing via Vim bindings, including features like text objects and marks. Zed is built by a global community of thousands of developers. Boost your Zed experience by choosing from hundreds of extensions that broaden language support, offer different themes, and more.

Helix is a modal (Kakoune/Vim‑inspired) terminal-based text editor written in Rust. It features modern modal editing, multiple selections, smart syntax highlighting, and built-in language server (LSP) integration leveraging tree‑sitter for fast, incremental parsing and code intelligence.

Markdown-Oxide is a Personal Knowledge Management System(PKM) that composes with your favorite text editor through the Language Server Protocol(LSP). While other PKMs implement their own text editors, markdown-oxide is unbundled: it leaves text editing to a dedicated text editor and focuses solely on robust, performant knowledge management.

Ferrite is a fast, lightweight desktop text editor built for people who spend a lot of time working in structured text formats and want a snappy, native-feeling app instead of a heavy IDE. It focuses on common “config and docs” formats like Markdown and popular structured data files, so it fits naturally into developer, DevOps, and technical writing workflows. The editor is designed around responsiveness and low overhead, prioritizing quick startup, smooth scrolling, and predictable editing...

...Writing zero-overhead, optimized WebAssembly is pretty tough to do. The syntax for .wat files is terse and difficult to work with directly. If you do not wish to use a systems language like C or Rust, then you're kind of out of luck. Your best bet (currently) is to write very plain C code, compile that to .wast and then optimize that result. Then you're ready to compile that into the final WebAssembly binary. Provide a thin layer of syntax sugar on top of .wat text format. Preferably porting as much of JavaScript syntax to WebAssembly as possible. ...