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

261–270 of 362 posts

Re: Zas Editor

#261

Post by sundarurfriend »

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!

Helix - or rather Kakoune† - has better-than-Vim keybindings though, in my view. It's what Vim keybindings would be if they were built from the ground up, without decades of cruft and bolted on bits, and instead had a coherent design to them that was easy to make sense of and intuit. Vim has that with its command grammar, a neat way of combining smaller comands into larger ones, but not with the individual command keybindings themselves.

† I'm still not sure what the difference between the two is, except that the Kakoune dev had to take a year-long break because of having a newborn child, and Helix development continued in that time.

Re: Zas Editor

#262

Post by seanw444 »

Annili wrote: post #41
andai wrote: post #39

Automatic renaming is amazing. Such slight reductions in friction make a big difference. I can already tell I would be much more likely to refactor often with such a feature. Unfortunately, I don't have a Mac at the moment. Are there any other editors with such a feature, or is it unique to Zas?

Zas Editor developer here. As far as I know, it’s a feature unique to Zas Editor. > I can already tell I would be much more likely to refactor often with such a feature. I’ve been working on Zas Editor in Zas editor for a while now, and can confirm the difference it makes

Dogfooding your editor! Nice.

Re: Zas Editor

#263

Post by vr46 »

nlnn wrote: post #157
vr46 wrote: post #82

I 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.

Very good point, actually - Vim keybindings are absolutely the thing to learn, we will forever discuss which editor/guitar is great, but as long as the muscle memory stays the same, you can compare...

Re: Zas Editor

#264

Post by deagle50 »

boundlessdreamz wrote: post #188

This looks great. Please consider adding support for Ruby. I know some of the smart features will not be possible/difficult in Ruby but if you can add some smarts around Rails support, you might attract a decent chunk of developers. Also almost all Rails development happens on Mac. Edit: The trial should ideally be 1 month. It takes a while to put the editor through its paces. Also support for running a command outsi…

Better yet, the trial should only count down when the app is being used. It will be long expired before the features we are waiting for before purchasing get implemented.

Re: Zas Editor

#265

Post by pjmlp »

samatman wrote: post #249
pjmlp wrote: post #54

Earlier quoted context omitted.

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.

Depends on the purpose, as I mention.

If the target is to be platform specific, then reducing the amount of compiler toolchains, IDE/editor plugins, and language knowledge required across team members is a good thing.

If the purpose is to go cross platform, then it is another matter.

Then again this is a matter of opinion, feel free to disagree, I am not here to change your mind.

Re: Zas Editor

#266

Post by leephillips »

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…

Mentioning that it’s Mac only, and that it’s not free software, would help keep plenty of people from wasting their time.

Re: Zas Editor

#268

Post by klibertp »

leephillips wrote: post #266
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…

Mentioning that it’s Mac only, and that it’s not free software, would help keep plenty of people from wasting their time.

Thank you - not sure about others, but I'd probably waste some time if not for your comment.

I would like to say a bit more, but basically anything of value I could add to the discussion would start a flame war, so I'll have to abstain :(

Re: Zas Editor

#269

Post by hasukimchi »

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…

In the preferences, the code analysis icon is missing.

And auto-updater tells me that I have version 1.0 and there is a new version 1.0.0 . And if I try to update, there is an update error.

It is also a bit confusing if you buy it, because you go to download and can then decide to download for trial or purchase. If you purchase, you just get a screen with the key. But no download. It is not nessasary clear, that the trial is also the main download.

And after purchasing, there is no invoice.

Re: Zas Editor

#270

Post by irishsultan »

pjmlp wrote: post #128
mindwok wrote: post #85

Earlier quoted context omitted.

They mentioned elsewhere it started off as a fork of the Xi editor which is written in Rust. Xi separates the text-editor idea into backend and frontend, and Xi itself is primarily the Rust-based backend which concerns itself with making editing operations very fast, and then you can write a front-end client for whatever language/platform you want. In this case, they can use a fast Rust backend for multiple platforms…

Which is why I made the point on my comment about what the cross platform goals were, but the RIR folks are too quick to jump the gun in any kind of critic and only read half of it.

But you're making the exact opposite mistake, it was already written in Rust, you're asking them to Rewrite in Swift.
Post reply on HN