Recent submissions

Comment · 4 years ago
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

Comment · 4 years ago
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.

Comment · 4 years ago
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.

Comment · 4 years ago
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.

Comment · 4 years ago
We’re currently working on VIM key bindings. If you’re interested, you can follow us on twitter @ZasEditor
Comment · 4 years ago
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
Comment · 4 years ago
Working on it.
Comment · 4 years ago
Added my info on the contact page
Comment · 4 years ago
Thanks for the hint. You can follow us on Twitter @ZasEditor for update announcements.
Comment · 4 years ago
We’re definitely going to support more languages. You can follow us on Twitter @ZasEditor to see the update announcements.
Comment · 4 years ago
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.

Comment · 4 years ago
Do you mean why we chose to make it native instead of making it cross-platform?
Comment · 4 years ago
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

Comment · 4 years ago
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.
Comment · 4 years ago
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.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton