Hacker News new | ask | show | jobs
by behnamoh 888 days ago
> Unlike VS Code, Obsidian is (for me) an actual example of an Electron app that feels fast. The quick open/command palette features are more responsive than similar features in native Mac apps I've tried.

Dude, VSCode is a freaking IDE, running all sorts of processes in the background (at least one terminal, language servers, type checkers, linters and formatters, possibly extensions, etc.) whereas Obsidian is just a text editor.

2 comments

> running all sorts of processes in the background (at least one terminal, language servers, type checkers, linters and formatters, possibly extensions, etc.)

That's a terrible excuse.

Your terminal is a separate process and should not affect how the editor itself feels. The language server exists out of process. The linters / type checkers exist out of process. (Or at least shouldn't block the main interaction/GUI thread) If those things make editing slow, either the design or the implementation is bad.

Sublime text runs the same stuff for me and works much faster than vscode. No excuses.

> Sublime text runs the same stuff for me and works much faster than vscode. No excuses.

Okay but this discussion is about electron apps. Sublime isn't.

This is an example for context. We've got 3 cases: Obsidian (non-ide/electron/fast), vscode (ide/electron/slow-ish), sublime (ide/non-electron/fast). My point was that neither the electron not the ide part is an excuse for vscode not being responsive, because we've got counterexamples for each.
Not arguing with that. In discussions about Electron, there are often comments along the lines of "Electron apps can be fast if done right, just look at VS Code" and that just doesn't hold true for me.