Live data from Hacker News

Zas Editor

zeditor.app

251–260 of 362 posts

Re: Zas Editor

#251
This looks really nice, especially the smart refactoring features and built in documentation search... but a Mac-only app disqualifies it for me. I need an editor that I can rely on no matter what OS I'm on. That's a bigger deal today than it was a decade ago. Having to switch my tools when I need to use a different OS is a massive productivity drain.

This is clearly a very niche product, being Mac-only and targeted at Rust/Go devs. I wish you luck with it though, because the world definitely needs more people making and innovating code editors (even if they're not all for me).

Re: Zas Editor

#252
post #229

Earlier quoted context omitted.

VSCode opens in 1s on my machine (macbook pro m1). Good enough for me.

What you say just underlines my point from above. People who are happy with performance of VS Code are not looking at performance graphs in a new editor. And those who seek performance are probably not using VS Code anyway. PS: > macbook pro m1 People were able to run IDEs and code editors 20 years ago. My 5 year old MB Pro is struggling with VS code. Not anything smart either, just UI, syntax highlighting, ... So wh…

My 7 years old MB Pro seems to handle VSCode fine

Re: Zas Editor

#253
post #25

This looks really good. I was a major fan of Coda, but I’ve been disappointed with Nova, so I’m looking for something else. The fact that this isn’t saddled with subscription pricing is a huge plus. I don’t even consider software I can’t own; $24.99 as a one-time payment with a year of updates is more than fair.

Why disappointed in Nova [maybe vs Coda]? I didn’t use Nova much myself so didn’t get to see enough of its issues

Re: Zas Editor

#254
post #152

Earlier quoted context omitted.

As it is written in Swift, I highly doubt linux support is in their roadmap.

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

Thought experiment: Rust half gets open-sourced and semi-stable-API-ified... and then out of several dozen community attempts to build a Linux UI, one of them eventually wins after 5 years :) (and a couple of stragglers build up small followings besides).

Realistically speaking, Linux (and Rust) UI is sufficiently incoherent at this point (heh shakes head "year of the desktop" for 3 decades at this point huh) I honestly don't think anything except "here's the code" would work because of the huge amount of keeping-up (unfortunately :/) necessary at this point.

Re: Zas Editor

#255
post #245

Been wanting something like this for a while now to switch from vscode. Considering not even terminals are safe from phoning home telemetry. You guys are charging for this, how much telemetry is the app sending home? Wish you guys all the luck.

Telemetry can be very easily turned off. It would take less time for you to Google "how to turn off VSCode telemetry" and finish it than writing this comment. This is ridiculous.

That's assuming you know that your editor is collecting your data and sending it to someone else. And since VS Code is a Microsoft product, they'll probably turn the telemetry back on after an update, only allow you to disable a subset of data collection, or simply ignore your preferences and send it anyways.

Re: Zas Editor

#256
post #4

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…

What editor were you using in the past? emacs, vim, vs?

Re: Zas Editor

#257
post #37
post #34

Earlier quoted context omitted.

What if JetBrains goes out of business?

For any software that has anything resembling DRM, which is a vast majority of software, once the company goes out of business, there’s no way to activate it. (Unless they address the conundrum before taking down the activation servers, of course.) This isn’t really a downside of the licensing scheme itself, though. If it was DRM free and on the honor system, it would not have this drawback. Of course, it’s currently…

On the other hand, no DRM is immune to being cracked.

> Of course, it’s currently unclear if a software development tool can remain relevant for many years after it is effectively unmaintained, so maybe this isn’t that interesting of a question.

I wonder if there has ever been a company that pledged to release the source code of their software in the case of bankruptcy, e.g. as part of the purchase/license agreement so that if the company is bought in a bankruptcy auction, the new owners can't change their minds.

Although I guess in that case, the incentive to pirate the software goes up lol

Re: Zas Editor

#258

I am an Apple MacBook user. However, personally I try to use only software that is available for Windows, macOS and Linux. This allows me to switch operating systems more quickly, should I choose to do so. Don't want to make myself dependent on one manufacturer.

Good for you. But now it's time for Zas Editor to make its case!

Re: Zas Editor

#259

Website looks sketchy, zero information on who is actually behind this project or what kinds of data are collected. Also, without proper plugin support (LSP!) I can’t see this going anywhere. Looks similar to Code Edit [1], an open source editor for macOS that’s currently in development. [1] https://github.com/CodeEditApp/CodeEdit

Won't it, though? People use JetBrains IDEs all the time as opposed to things with tons of plugins. It sounds like that's the style they're going for, just a little lest slow and bloated, based on their website.

Re: Zas Editor

#260

Earlier quoted context omitted.

You mentioned elsewhere that VIM bindings are upcoming. I think this product will be an insta-buy for me once there're (reasonably proper) vim bindings. Is there a newsletter or something to know once this feature has landed? 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: https://githu…

the curse of vim.

Once you've learn vim keybinds and combinations, nothing comes close for productivity.
Post reply on HN