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.
Zas Editor
241–250 of 362 posts
Re: Zas Editor
#242Earlier quoted context omitted.
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.
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.
Are you planning to add support for other languages in future, or are those two your main focus?
Re: Zas Editor
#243I 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.
Valid point. I know it's easier for the developers to support only one or two platforms, but I see full support of all major platforms as a sign of maturity.
If it doesn't, it's a sign of issues either with used libraries, programming language or tools.
Re: Zas Editor
#244Why don't you mention the fact that it is Mac-only before bottom of the page (download section)?
Well, why didn't you infer that from the page design? :)
Why should a user infer anything?
This is simply bad user experience. A person who uses Windows may be confused but they can only be sure after reaching the bottom of the page. Not to mention it is not rare that a multi-platform application use Mac screenshots, including (surprisingly) VSCode, from time to time
Re: Zas Editor
#245Been 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.
Re: Zas Editor
#246Wow that sounds like a really interesting editor for Golang! Only missing thing I absolutely need is the debugger+a test runner. Once those are here I think I'll buy a license!
Re: Zas Editor
#247Zas 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…
FYI typo on your faq page: "hunderds"
And "dependancies" on the landing page.
Re: Zas Editor
#248I 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.
As a counterpoint, I only exclusively work on macOS and vastly prefer native interfaces over Electron apps, which is what the majority of cross platform applications use.
Re: Zas Editor
#249Hi 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…
If the plan is to make a native UI for each platform, good approach. If it is to stay macOS only, also a possible decision not everything needs to be cross platform, why bring Rust into the picture?
Why would they not?
Integrating object code into Objective C or Swift is easy, commonplace, people do it all the time.
Rust can generate object code all day, you can insist on the C ABI anywhere you need to, and then you can bring in anything from cargo you want. CocoaPods is... not cargo.
Re: Zas Editor
#250Cool! I'm not on Mac so not for me, but always inspiring to see innvoation in editing.
One more typo, under "Exceptional Performance": "It can to generate symbols [...]", the "to" should not be there.