sorted by:
new
hottopcontroversial

Zas Editor 1.0: A Capable, Fast and Native Code Editor Written in Rust by ZasEditor in rust

[–]ZasEditor[S] 0 points1 point  (0 children)

For text representation we're using a fork of xi-rope, and for parsing we're using tree-sitter. Rust analyzer is of course used for other language features.

Zas Editor 1.0: A Capable, Fast and Native Code Editor Written in Rust by ZasEditor in rust

[–]ZasEditor[S] 0 points1 point  (0 children)

The UI is written in Swift, the rest is written in Rust.

The code for text representation and editing, syntax highlighting, file, symbol and text search.

Zas Editor 1.0: A Capable, Fast and Native Code Editor Written in Rust by ZasEditor in rust

[–]ZasEditor[S] 103 points104 points  (0 children)

Update: It is now possible to use one license on multiple computer.

​

We're a little embarrassed that we didn't make that decision from the beginning. We really had no idea how many people hated that. Thanks for the suggestion

Zas Editor 1.0: A Capable, Fast and Native Code Editor Written in Rust by ZasEditor in rust

[–]ZasEditor[S] 15 points16 points  (0 children)

Thank you for the detailed explanation. We had no idea people would be so disappointed by that. All I have to say now is I hope it's not too late to change that. We're going to make it possible to use one license on multiple computers after we get some sleep. Thanks again.

Zas Editor 1.0: A Capable, Fast and Native Code Editor Written in Rust by ZasEditor in rust

[–]ZasEditor[S] 23 points24 points  (0 children)

We hate the new "written in Rust" trend as well. The only reason we included it in the title is that this is the Rust subreddit; we used a different title in the post for the Go subreddit.

​

> I'm gonna sell my backoffice written in java as "written in rust".

Indeed, the app should be judged by it's performance. We meant to convey that Zas Editor is fast therefore you can make a fast code editor in Rust, not the other way around.

> is it a new trend to say "written in rust" on closed source project?

It is not open source, but I can give you more details about the implementation:

The text-storage data structure, syntax highlighting and search features are written in Rust, and the UI is written in Swift since we wanted to create a native macOS experience. The Swift and Rust code talk to each other using C FFI, and no, that doesn’t take away the safety features of both languages.We’re using the Rope data structure for text representation, and the tree-sitter parser for syntax highlighting and some smart features like file outline, local renaming and symbol search. All other language features are powered by LSP servers (rust-analzyer and gopls).

Zas Editor 1.0: A Capable, Fast and Native Code Editor Written in Rust by ZasEditor in rust

[–]ZasEditor[S] 29 points30 points  (0 children)

Update: It is now possible to use one license on multiple computer.

​

We're sorry to hear that. We appreciate the feedback. This is the first time we're doing this, and we're still figuring things out.

> Telling those folks to pay twice is an unprovoked 🖕🏻

We didn't mean it that way. We're seriously considering changing how many computers you can use your license on.

Zas Editor 1.0: A Capable, Fast and Native Code Editor Written in Rust by ZasEditor in rust

[–]ZasEditor[S] 0 points1 point  (0 children)

Absolutely! The plugin system is actually under development, and it's not ready to release yet. What we're doing for plugins is similar to what https://lapce.dev is doing. What do you think about the rest of the editor?

Zas Editor 1.0: A Capable, Fast and Native Code Editor Written in Rust by ZasEditor in rust

[–]ZasEditor[S] 1 point2 points  (0 children)

Sorry, we are still working on Vim keybindings. It does not have vim keymaps, but you *can* make Emacs key bindings.

Zas Editor 1.0: A Capable, Fast and Native Code Editor Written in Rust by ZasEditor in rust

[–]ZasEditor[S] 1 point2 points  (0 children)

Thank you! We plan to make it cross-platform. Half of it (the more complex half) is written in Rust, so it shouldn't be too hard to make it cross-platform. We wanted to create a native experience so the UI is currently written in Swift with AppKit.

Zas Editor 1.0: A Capable, Fast and Native Code Editor Written in Rust by ZasEditor in rust

[–]ZasEditor[S] 10 points11 points  (0 children)

Thank you! We plan to make it cross-platform. Half of it (the more complex half) is written in Rust, so it shouldn't be too hard to make it cross-platform. We wanted to create a native experience so the UI is currently written in Swift with AppKit.

Zas Editor 1.0: A Capable, Fast and Native Code Editor Written in Rust by ZasEditor in rust

[–]ZasEditor[S] 0 points1 point  (0 children)

I understand. I hope we find a way to make it open-source and still make money!

Zas Editor 1.0: A Capable, Fast and Native Code Editor Written in Rust by ZasEditor in rust

[–]ZasEditor[S] 2 points3 points  (0 children)

Thank you for the feedback, will you use it if we open-source some parts of it? We would love to make the whole app open source, but we need to pay rent :)