Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Zas Editor

zeditor.app

Post reply on HN
Print view View original

91–100 of 362 posts

Re: Zas Editor

#91

Post by hajhatten »

hbbio wrote: post #38

Looks slick and well built. I would really like to try. However, there is no info about the team, company, etc. Even social accounts are brand new. To install a closed source binary with no provenance info is a bit harsh, the only way I could test would be on an offline spare Mac. Is any data collected? Given that it started out as a fork of xi-editor, I think you should consider switching to an open source + subscri…

They seem to be dodging the telemetry questions on HN.

No open source and completely anonymous developers behind it.

Not having a clear decision made about how their DRM is supposed to work, and ask people to delete their posts regarding it...

Huge red flags here.

Re: Zas Editor

#92

Post by divan »

sawaali wrote: post #21

There has been a resurgence of native editors these days (Helix, Nova, …). Every time I rush to check if there are vim keybindings. It's a dealbreaker otherwise!

I've tried Helix few days ago and was more than impressed – almost everything you want from code editor is there out of the box, and transition from neovim was super fast. The only thing the holds me from switching completely is lack of Copilot.

But yes, there seem to be a momentum of rethinking editors and frustration with popularity of a slow and heavy editors.

Re: Zas Editor

#94

Post by mwcampbell »

Annili wrote: post #22
raphlinus wrote: post #19

Earlier quoted context omitted.

For the rope, are you using xi-rope, ropey, or did you roll your own? Any thoughts on how you made that decision? Glad to see stuff like this, it brings back memories.

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

What do you think of the "no such thing as native GUI" section of the xi retrospective [1], particularly the surprisingly bad performance?

[1]: https://raphlinus.github.io/xi/2020/06/27/xi-retrospective.h...

Re: Zas Editor

#95

Post by lozenge »

jll29 wrote: post #78
_zzaw wrote: post #34

Earlier quoted context omitted.

What if JetBrains goes out of business?

I recommend companies add a clause to their licenses that if they go out of business or get acquired with the consequence that the product line gets discontinued, the product becomes open source automatically. That also takes out a lot of risk for bigger companies doing business with startups.

The end user doesn't have the copyright to the source therefore they are unable to relicense it. The only person that can make it open source is the acquiring company. The acquiring company might not have signed the EULA, or they could just negotiate an amendment with their new acquiree that removes the clause.

Re: Zas Editor

#96

Post by gbraad »

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 will be in the future. Note: I am NOT a mac user anymore. Still use sublime for time to time, but fully moved to VScode. If I look for speed or search functionality, I would use vi again. At the moment I care more about the presentation, refactoring and navigation. The extensions of vscode make this experience for me more powerful; remote ssh, marked mindmap, markdown rendering, etc plus it can run on a remote host and be accessible from a browser. Accessibility and the same experience across platforms are key to me.

Success with the editor. It does look promising! but not for me.

Re: Zas Editor

#98

Post by newlisp »

Annili wrote: 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…

How do you create a new file from Zas? seems like you can only open existing files

Re: Zas Editor

#99

Post by pjerem »

jll29 wrote: post #78
_zzaw wrote: post #34

Earlier quoted context omitted.

What if JetBrains goes out of business?

I recommend companies add a clause to their licenses that if they go out of business or get acquired with the consequence that the product line gets discontinued, the product becomes open source automatically. That also takes out a lot of risk for bigger companies doing business with startups.

I’m not sure a company can be liable about something written in a licence if they go out of business. At least it could be seen as a sign of goodwill.

Re: Zas Editor

#100

Post by nemothekid »

hbbio wrote: post #38

Looks slick and well built. I would really like to try. However, there is no info about the team, company, etc. Even social accounts are brand new. To install a closed source binary with no provenance info is a bit harsh, the only way I could test would be on an offline spare Mac. Is any data collected? Given that it started out as a fork of xi-editor, I think you should consider switching to an open source + subscri…

>With tiny bits of added value, many would be able to pay $20/y for convenience and you may end up with more revenue.

If you look at the landscape of editors, it's pretty much split between FOSS or Paid and closed source. I wouldn't recommend this route; OP would simple end up supporting a bunch of people who would never pay for this app. Going FOSS for a code editor only makes sense if you are already working for a huge tech company.

Post reply on HN