Live data from Hacker News

Zas Editor

zeditor.app

221–230 of 362 posts

Re: Zas Editor

#221
post #205

Earlier quoted context omitted.

My 35+ years experience (ah ah!) tells me that emacs is the best :-) Just kidding... I code small stuff nowadays, so emacs is just fine. But if I had to get into something big, I'd certainly use a tool with powerful and fast code navigation, and something that works out of the box. LSP mode on emacs is not easy to set up. I mean, you can get it 90% working in 15 minutes, sure, but then come the little things such as:…

Org mode was my main "excuse" for keeping Emacs around, but these days i've more or less given up using it due to lack of decent mobile clients. Instead i've more or less settled on Obsidian for my notes, which does 99% of what i used org-mode for, and i use other tools for the last 1%. The only thing i'm missing is a good (integrated) solution for task and time tracking/reporting. I'm aware that PlainOrg ( https://p…

Did you try Beorg on mobile?

Re: Zas Editor

#223
post #218

> Zas Editor reparses your code on every keystroke without compromising performance. Having a maintained AST at all times brings many intelligent features to the editor. How does this work in the presence of syntax errors? 95% of the time you're writing code, your code is syntactically invalid, because you've started some new construct but not finished it yet, so you need syntax highlighting, code completion, etc to…

you still have the previously valid tree because the parsing is incremental

i suspect it's tree sitter under the hood

Re: Zas Editor

#224
I see only a download for mac, I am on Linux. My current setup is actually ok, use vim and sometimes vscode. 24 usd isn't that expensive but what would I get that vim doesn't do?

Re: Zas Editor

#225
post #218

> Zas Editor reparses your code on every keystroke without compromising performance. Having a maintained AST at all times brings many intelligent features to the editor. How does this work in the presence of syntax errors? 95% of the time you're writing code, your code is syntactically invalid, because you've started some new construct but not finished it yet, so you need syntax highlighting, code completion, etc to…

They use tree-sitter https://tree-sitter.github.io/tree-sitter/ It's ok with errors in AST and just marks such nodes as invalid. There is a long (42 minutes) but worth to watch talk about tree-sitter https://www.youtube.com/watch?v=a1rC79DHpmY Or the shorter version (20 minutes) https://www.youtube.com/watch?v=0CGzC_iss-8

Re: Zas Editor

#226
This would be an instant buy if it matched some Goland features/plugins:

-Ideavim (.vimrc support, custom mappings to editor actions)

-AceJump/EasyMotion

-Color scheme customization

Re: Zas Editor

#227
post #169

Earlier quoted context omitted.

Yeah, people in this thread are praising the one time purchase but I'm almost seeing it as a red flag - how do we know a niche product like this will stick around without recurring revenue? I don't know if that's paid major upgrades or similar. Edit: As a sibling comment pointed out it does actually do paid upgrades after a year so ignore my comment.

The Affinity Suite does the same and they're still around, even though there's massive competition in Adobe CS competitors.

Those are very different cases.

The adobe suite is bloated, slow, overly complex... There is a very strong niche for a suite or single tools that have better design, performance, integration and UX.

Jetbrains dev tools are highly praised just on their own and they have a strong plugin ecosystem (see: Cursive for Clojure).

Also these kind of developer tools have to indirectly compete with highly extensible and well established open source alternatives such as Vim, Emacs, VSCode who all have their unique strengths and support tons of languages.

Re: Zas Editor

#229
post #145

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

VSCode opens in 1s on my machine (macbook pro m1). Good enough for me.

What you say just underlines my point from above. People who are happy with performance of VS Code are not looking at performance graphs in a new editor. And those who seek performance are probably not using VS Code anyway.

PS:

> macbook pro m1

People were able to run IDEs and code editors 20 years ago. My 5 year old MB Pro is struggling with VS code. Not anything smart either, just UI, syntax highlighting, ... So while "good enough for me" is absolutely valid position, VS Code is objectively slow.

Post reply on HN