101–110 of 362 posts
You lost me at "Download for Mac. Buy for $24.99" Not that I am against paid software, but the added value is bound to a single platform. It must provide a lot of 'functionality' and specifics to make it worthy. Especially is it is just an editor with the idea to become an IDE, which will likely impact performance over time. I am merely guessing here. But since performance is a major selling point, I wonder how this…
Hi 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…
This looks pretty great, but I'm through paying for commercial programming tools that aren't portable to everything I might be developing on. Right now I'm developing on a Mac for work, but in a year that might be different, and the time and money I put into this editor will be wasted.
I love a new editor. But I long ago realized that a text editor was a massive long-term investment and after two editor companies abandoned me, I switched (back) to Vim and doubled down. Had I stuck with Vim in 1992, I could have saved a lot of time. That said, today it’s Neovim, with IntelliJ kept around for its power and the fact that I often have to open client projects. And VSC for specific plugins that save time…
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 better plugin than ST ever did.
And so, after a couple of decades, i appear to have come full circle, and now mostly use Vim again, unless a task requires "specific tools", i.e. writing Azure Functions, which is much easier to handle in Visual Studio or VS Code.
Hi 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…
Earlier quoted context omitted.
I'm wondering why no support for LSP and DAP? Is it missing feature you guys need?
We are using LSP under the hood, but you can't add more language servers yourself. AS for DAP, a debugger would be a huge feature to implement, we wanted to get it right before releasing it.
Hi 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…
Also as a hint, before you try to re-implement 30 years of VIM bindings and end up with something where everybody misses something, there's a great C library that could be of help:
1. Sublime Text
2. Jet Brains PHPStorm
3. Panic Nova
A quick Google search shows about a dozen others, plus at least ten free editors.
Is there any resource that allows me to compare these?
Earlier quoted context omitted.
This looks like a great start! There's one thing I couldn't find from this page, which I'm sure many developers would ask about: is there a Vim plugin, or Vim mode? And if not, are you planning to add one?
Hi, thanks for the tip, I will add that to the FAQ. There is no VIM key binding at the moment. We are planning to add one; we know how many developers (including us) would want that.