“It can to generate symbols for projects” —> “It can generate symbols for projects”
Zas Editor
151–160 of 362 posts
Re: Zas Editor
#152Earlier quoted context omitted.
Hi! This looks really cool, great work! It seems to be Mac-only for now, is Linux support on your roadmap at all?
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
Re: Zas Editor
#153Earlier quoted context omitted.
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.
I'm locked in emacs (joke intended). But I must admit that my rust/LSP experience with Emacs doesn't hold 5 seconds in front of what I've just seen on the Zas website...
> my rust/LSP experience with Emacs doesn't hold 5 seconds in front of what I've just seen on the Zas website
My preferred way of working after 20+ years in the industry, is finding the "best tool" for the job.
Vim is my "goto" editor for everything that doesn't have a better tool, but any perceived performance gain from being familiar with an editor needs to be compared to the performance gains of using the specialized tool.
I.e. Writing Azure Functions, VS Code / Visual Studio makes this dead simple with integrated local Azure Storage emulation and more. It can be done in other editors, but i'd spend a lot of time on tooling instead of just writing code.
I guess i've just gotten more pragmatic with time :)
Re: Zas Editor
#154Does this have Vim key bindings? Can't find it anywhere on the landing page. I am very reluctant to give up my Neovim + Kitty setup. Most editors I have used consume a lot of RAM and end up becoming slow on big projects (especially when used in conjunction with LSPs). Operations aren't as smooth as I would like them to be. I have used Vim bindings with VSCode and even though it is manageable it still has a lot of quirks and performance issues that put me off. Eventually moved to Neovim and have never looked back. But if I get a better experience with Zas Editor (no compromise on performance though) I would definitely switch.
Re: Zas Editor
#155Earlier quoted context omitted.
Why would support for Rust be a problem here?
Two language development stack, with the complexity it entails, when the product is mac only.
Cross platform future aside, they want to use all the good libs Rust has for ropes and the like. The code is based on another editor earlier work, and that's in Rust.
They also know Rust so if they want to use Rust, what's the problem in using it? They don't seem to have any problem with building a UI on top, it's built and looks/works fine.
Re: Zas Editor
#156Does this have Vim key bindings? Can't find it anywhere on the landing page. I am very reluctant to give up my Neovim + Kitty setup. Most editors I have used consume a lot of RAM and end up becoming slow on big projects (especially when used in conjunction with LSPs). Operations aren't as smooth as I would like them to be. I have used Vim bindings with VSCode and even though it is manageable it still has a lot of qui…
We’re currently working on VIM key bindings. If you’re interested, you can follow us on twitter @ZasEditor
Re: Zas Editor
#157I 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…
Exactly the same here.
I've also gotten so used to vim keybinding support in almost everything I use (e.g. IntelliJ, VSCode, Obsidian) that I doubt I'd invest in anything without that.
It sounds like that's on the cards for Zas in future though, so looking forward to giving it another try then.
Re: Zas Editor
#158> Native. Fast. Lightweight. Comparison is missing editors that would compete with this. VS Code is huge and slow, but somehow people use it and love the extensibility and broad support. Goland is just a beast that does so much more it's not even in the same league. What would make sense in the comparison chart is something like ST3.
Fast and slow are relative.
VSCode opens within about 2 seconds on my machine which for me is fast. For some users they want it to open even faster than that so something like vim makes sense.
Visual studio 2019 on the other hand takes about a minute to a large project and with resharper even longer.
Re: Zas Editor
#159Hi 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
"Right click -> New file" in the sidebar
Re: Zas Editor
#160This 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.
Have you looked at code runner: https://coderunnerapp.com/ ? It has some Python support but not on the level of VSCode or PyCharm IMO.
Yeah, I've used it for a decade or more to run snippets. But I don't consider it an editor - more of a scratchpad, nor that it has any particular Python support to write home about.