Wish I could use this. Add F# support and I’ll shower you in money.
Zas Editor
111–120 of 362 posts
Re: Zas Editor
#112Hi 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 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…
Thanks for the hint. You can follow us on Twitter @ZasEditor for update announcements.
Re: Zas Editor
#113I think the title would better if it is "Zas Editor, only for Mac".
It only mentions this at the very bottom of the page. Either other platforms are considered at some point, or be clear about this.
The screenshots suggest macOS use, but you can't be for sure as any program can be rendered like this on a mac.
Re: Zas Editor
#114Earlier quoted context omitted.
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...
From a purely macOS perspective, the major issue (apart from JSON being slow in Swift) was that there's no good native editor control for source code. There's NSTextView but it doesn't scale to large, syntax highlighted documents and lacks the required facilities that a source code editor needs. Hence, all proper third party text editors for macOS write their own source code control. I, personally, would contest that a native GUI is very much possible, but only for the chrome of the editor (e.g. searching, menus). This is also where native GUIS can shine. I'd wager that a proper source code control is such a domain specific requirement that each cross platform editor has to implement them whether they use native UI or not (maybe Qt has a fantastic one, I don't know)
Re: Zas Editor
#115@dang our post was marked as [dup]. The title is too ambiguous. Can we update it to 'Zas Editor: Capable, Fast and Native CodeEditor Designed for Reading and Writing'.
"Zas Editor: mac-only editor for Reading and Writing"
Re: Zas Editor
#116Hi 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…
Can't you add some sort of impressum to the website where you give some information about you?
Re: Zas Editor
#117Been 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.
You should try vscodium, it's vscode minus all the Microsoft bs
Re: Zas Editor
#118[deleted]
Re: Zas Editor
#119Hi 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…
looks wonderful!
Re: Zas Editor
#120I love a new editor. But I long ago realized that a text editor was a massive long-term investment and after two editor companies abandoned me, I switched (back) to Vim and doubled down. Had I stuck with Vim in 1992, I could have saved a lot of time. That said, today it’s Neovim, with IntelliJ kept around for its power and the fact that I often have to open client projects. And VSC for specific plugins that save time…
I've certainly been down that rabbithole. Started with Vim, planned on eventually learning Emacs (still do), and then to whatever editor was "flavor of the month", including TextMate and Sublime Text. Sublime Text was great in it's day, and i still hold a license for the latest version, but it is caught in a death spiral it seems. Whenever i check if it "does X", it turns out it maybe does, but VS Code has a much bet…
I currently settle on Emacs (again) after three years of NeoVim. LSP is so much better integrated and works for my needs out of the box. I currently don't miss treesitter, expect for semantic selections at point.
But I realized I could get rid of a massive and ever changing NeoVim configuration mess. Using Emacs 29 though.