Annili

I’m not the only developer, but I’ve %90 of the work. Hopefully, we can get more support and expand

> How long did it take from first line of code to current state?

It started out as a part-time side project and after a while I started working full time on it. So, I’m not sure I can give an accurate answer to your question. The first commit was made in August 2020

Zas Editor developer here. I think it’s important to address a problem a few people have mentioned so far: no data is collected other than your Mac’s serial number, which used to be used for finding how many computers a license is used on (we no longer do that)

We’re going to add a privacy policy in the website. We haven’t already done that because we didn’t really expect this much attention within hours of releasing. Honestly, we were expecting few downloads and more technical feedback.

Hi, in the current and only version, your Mac’s serial number is collected, which used to be used to ensure one license can be used on only one computer (this is not the case anymore).

We’re going to add a privacy policy in the website. We haven’t already done that because we didn’t really expect this much attention within hours of releasing. We were expecting few downloads and more technical feedback.

No data is collected other than the serial number of your Mac for making sure you can only use your license on one computer, which we realized was a bad idea, and made changes.

We’re going to add a privacy policy in the website. We haven’t already done that because we didn’t really expect this much attention within hours of releasing. We were expecting few downloads and more technical feedback.

We’re currently working on VIM key bindings. If you’re interested, you can follow us on twitter @ZasEditor

The more complex half is written in Rust. But you’re right, making it available for Linux isn’t something we plan to do soon

Working on it.

Added my info on the contact page

Thanks for the hint. You can follow us on Twitter @ZasEditor for update announcements.

We’re definitely going to support more languages. You can follow us on Twitter @ZasEditor to see the update announcements.

We realized how big of a mistake that was. We updated the server and the website. It is now possible to use one license on multiple computers.

edit: We would appreciate if you could mention that your comment in case someones reads your's without reading this one.

Do you mean why we chose to make it native instead of making it cross-platform?

Zas Editor developer here. As far as I know, it’s a feature unique to Zas Editor.

> I can already tell I would be much more likely to refactor often with such a feature.

I’ve been working on Zas Editor in Zas editor for a while now, and can confirm the difference it makes

Thank you for the feedback. We made a change to the landing page, it should be more clear what languages are supported now. The first sentence now is "A new, capable, and fast code editor for Go and Rust, focused on both reading and writing code". A signup is missing, but you can follow us on Twitter @ZasEditor in the meanwhile.

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.

I believe Nova added support for vim keybindings recently. We're going to add vim keybindings soon. In fact, we're starting to regret not implementing the functionality for this release!

Hi Raph. It amazing to see you here and thank you for all the xi crates.

> Any thoughts on how you made that decision?

The reason behind that is Zas Editor started out as a fork of Xi Editor! We're also using a fork of xi-rope, though we haven't made many changes to it.

If you would like to discuss this more, DM me at twitter @ZasEditor

@dang our post was marked as [dup]. The title is too ambiguous. Can we update it to 'Zas Editor: Capable, Fast and Native CodeEditor Designed for Reading and Writing'.

Thank you for the feedback! We are on it. Just quick question, are you on a desktop?

Thank you! Fixed it

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.

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 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).

I’d be happy to answer any questions under this comment or anywhere else in this thread.

Sorry to hear that. At the moment only Go and Rust are supported. We are currently working on plugins. What did you think about the Rust & Go support? Would you use it for Python if we add support?

> One of the people on my team wrote a very “contrib directory” version of that for internal testing

If that is open-source, could you please share a link to it?

I'm curious what advantages this "stack-graphs LSP wrapper" has over existing language-specific LSP servers for an editor/IDE, maybe lower memory usage or better performance?

I'm curious to see if Tree-sitter can be used to provide fast and rich code navigation. I was able to implement simple goto definition/references [1], not sure if it can be used for more advanced navigation features in a language-agnostic way.

If you're interested, GitHub is already using it [2] for that purpose and Sourcegraph is experimenting it [3]

[1] https://github.com/alidn/lsif-os [2] https://github.com/github/semantic [3] https://github.com/sourcegraph/sourcegraph/issues/17378

> "Paredit for TypeScript"

Is there a list of ideas for Structural Editing in C-like languages?

I can think of `extend-selection, `move to parent block`, `add arg to function`

In the third paragraph:

> ... technical limitations meant it was impossible to know if this really was H2O (water) or hydroxyl molecules (consisting of one oxygen atom and one hydrogen atom) in minerals.