This looks promising. Downloaded it to try, was dissapointed to find no/little support for Python. It does work for Go and Rust though. If this can get a good plugin ecosystem, it would fly.
Zas Editor
31–40 of 362 posts
Re: Zas Editor
#32Good luck! It looks like an amazing product.
Re: Zas Editor
#33Hi 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…
You might want to put supported languages more front and center and not buried on a hard-to-find faq page. Might also want to allow folks to sign up to be alerted when their favorite language is supported, which will also let you gather data about where there's the most interest.
Re: Zas Editor
#34This 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.
This is one of the reasons I like JetBrains subscription service. Even if you stop paying, you get a fallback license that updates every year (I believe); so you have perpetual access to their product, even if slightly out of date.
Re: Zas Editor
#35Re: Zas Editor
#36Earlier quoted context omitted.
This is one of the reasons I like JetBrains subscription service. Even if you stop paying, you get a fallback license that updates every year (I believe); so you have perpetual access to their product, even if slightly out of date.
What if JetBrains goes out of business?
Re: Zas Editor
#37Earlier quoted context omitted.
This is one of the reasons I like JetBrains subscription service. Even if you stop paying, you get a fallback license that updates every year (I believe); so you have perpetual access to their product, even if slightly out of date.
What if JetBrains goes out of business?
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 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.
Re: Zas Editor
#38However, 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 + subscription business model: You may get a much larger userbase (as again you seem to have built a great product), you'd gain trust even if you prefer to remain anons, and you can bundle additional services (e.g. sync the configuration between multiple devices through iCloud can be a paid subscription-only service, additional themes, binding of Apple latest kits etc.).
With tiny bits of added value, many would be able to pay $20/y for convenience and you may end up with more revenue. Also, you may use the App Store to charge for the subscription, it is easier for many of us with payment info already in.
Re: Zas Editor
#39Unfortunately, I don't have a Mac at the moment. Are there any other editors with such a feature, or is it unique to Zas?
Re: Zas Editor
#40An editor that makes it easy to write more code can be counterproductive when the actual goal is to write less of it.