Live data from Hacker News

Knowledge Management in the Age of AI

ericgardner.info

91–92 of 92 posts

Re: Knowledge Management in the Age of AI

#91
post #85
post #80

Earlier quoted context omitted.

Note that I worked with Emacs already a few years ago, and it was Spacemacs specifically. That said, VSCode is - much nicer looking, a lot of things come working out of the box that I had to work hard to make work in Emacs (even with Spacemacs), a lot of great plugins exist and are easy to add to VSCode. Really it's the "great experience out of the box" and lack of weird edge cases where custom code/plugins interact…

I really dont get the idea of having a vim mode in emacs, og an emacs mode on VSCode. Why dont just use the keybindings for the editor you are using?

> I really dont get the idea of having a vim mode in emacs

vim-mode is not just about keybindings.

It's about modal editing philosophy - the distinction between command and insert modes fundamentally changes how you think about text manipulation. When you're in command mode, every key becomes a text object or motion command, making complex edits incredibly efficient. You're not just getting vim's keybindings; you're getting vim's grammar of editing. The real power comes from composability - vim motions aren't just shortcuts - they're a linguistic system for describing text transformations.

Emacs veterans often detest "modality" without realizing how much modality already exists in Emacs. Key chords like C-x put you in a modal state where the next key has different meaning. Recording macros creates a modal context. The minibuffer is literally a different mode with its own keybindings and behavior. Transient menus are explicitly modal interfaces. Even isearch is a modal state. Vim-style modality is just making this concept more explicit and systematic.

Besides, it's simply an obtuse exercise to ask Emacs users why would they do something with their editor. The answer is obviously "because they can."

Vim's model of modality and mnemonics is a beautiful, powerful, amazing paradigm. Here's the thing though - there's no such thing as the "vim-mode". None of the IDEs and editors like IntelliJ, VSCode, XCode, Android Studio, Sublime, etc., can properly emulate Vim navigation. The one exception is Emacs.

Pretty much every other IDE fails to comprehensively replicate Vim. Unless it's Vim/Neovim, vim-mode in all of them is just that - an emulation. However, Evil mode in Emacs feels much more natural. Sometimes, you forget that it's an afterthought, an extension, and not a built-in functionality.

While Evil-mode obviously is not the most important or even built-in feature of Emacs, as a nerd and a computer programmer, if I discovered that there's a civilian plane that can perform a vertical landing, yet never actually needs to use it, I would still love that model over any other planes, even if the feature is purely accidental. The fact that it can do so alone would be great evidence of amazing engineering.

Re: Knowledge Management in the Age of AI

#92
post #46

Earlier quoted context omitted.

Not sure on encryption, but the notes themselves are just files and folders, you can host and sync the files with anything you want. Unless you're talking about wanting it as a self-hosted web app?

My primary concern is the lack of encryption for the notes. This absence of encryption leaves them exposed and vulnerable. Relying on third-party services like Dropbox, iCloud, or similar platforms to sync notes across devices only heightens the potential for data exposure. There is also a Obsidian forum thread about that [1]. I believe the primary issue with nearly all note-taking tools is the lack of genuine encryp…

True, Obsidian lack of native local encryption is absurd in 2025. Standard Notes, Joplin, OneNote, even Apple Notes support this. Obsidian people will keep replying you have to protect your whole filesystem. This is absurd. Zero Trust is one of OPSEC main principle. Sounds crazy to me to externalize security for a note-taking app in 2025.
Post reply on HN