Zas Editor
121–130 of 362 posts
Re: Zas Editor
#122Hi everyone! I'm the lead developer of Zas Editor. I wanted to share some details about the editor you might be interested in. 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…
Can't you add some sort of impressum to the website where you give some information about you?
Re: Zas Editor
#123Earlier quoted context omitted.
I've certainly been down that rabbithole. Started with Vim, planned on eventually learning Emacs (still do), and then to whatever editor was "flavor of the month", including TextMate and Sublime Text. Sublime Text was great in it's day, and i still hold a license for the latest version, but it is caught in a death spiral it seems. Whenever i check if it "does X", it turns out it maybe does, but VS Code has a much bet…
I currently settle on Emacs (again) after three years of NeoVim. LSP is so much better integrated and works for my needs out of the box. I currently don't miss treesitter, expect for semantic selections at point. But I realized I could get rid of a massive and ever changing NeoVim configuration mess. Using Emacs 29 though.
Re: Zas Editor
#124Hi everyone! I'm the lead developer of Zas Editor. I wanted to share some details about the editor you might be interested in. 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…
Re: Zas Editor
#125Re: Zas Editor
#126Re: Zas Editor
#127From the domain name I confused this with the Zed editor[0] for a second. Despite both being editors written in Rust with zed* domain names, they are different. Really interested in both projects though. [0]: https://news.ycombinator.com/item?id=29566960
Re: Zas Editor
#128Earlier quoted context omitted.
Two language development stack, with the complexity it entails, when the product is mac only.
They mentioned elsewhere it started off as a fork of the Xi editor which is written in Rust. Xi separates the text-editor idea into backend and frontend, and Xi itself is primarily the Rust-based backend which concerns itself with making editing operations very fast, and then you can write a front-end client for whatever language/platform you want. In this case, they can use a fast Rust backend for multiple platforms…
Re: Zas Editor
#129Re: Zas Editor
#130Earlier quoted context omitted.
I've certainly been down that rabbithole. Started with Vim, planned on eventually learning Emacs (still do), and then to whatever editor was "flavor of the month", including TextMate and Sublime Text. Sublime Text was great in it's day, and i still hold a license for the latest version, but it is caught in a death spiral it seems. Whenever i check if it "does X", it turns out it maybe does, but VS Code has a much bet…
I currently settle on Emacs (again) after three years of NeoVim. LSP is so much better integrated and works for my needs out of the box. I currently don't miss treesitter, expect for semantic selections at point. But I realized I could get rid of a massive and ever changing NeoVim configuration mess. Using Emacs 29 though.
But I must admit that my rust/LSP experience with Emacs doesn't hold 5 seconds in front of what I've just seen on the Zas website...