I'll try to explain. I was a nvim user for a couple of years and used vimwiki (not a power user though) then switched to Doom Emacs about 3 years ago and would

I'll try to explain. I was a nvim user for a couple of years and used vimwiki (not a power user though) then switched to Doom Emacs about 3 years ago and would consider myself an almost-power user for org mode. What I like about org mode over vimwiki is how seamless the experience is. It is super-easy to pause what I'm working on, create a note or TODO or almost anything very quickly, and get right back to what I was working on. This note (or whatever I created) is linked to the file I was in when I started the note, it's timestamped, if I make it a TODO then it automatically shows up in my org todo list, if I schedule it or give it a deadline it automatically shows up in my org agenda. And then there's literate programming. I actually just finished an interview 30 minutes ago where I used literate programming. It was "create a database structure and a very rough outline of a UI for this thing" so I opened an org file, copied the requirements at the top, asked some questions and wrote those down as well, then started an org table to approximate a [database structure][0]. Once I was ready to write code I created a [code block][1] which gets syntax highlighting, formatting, basically all the LSP stuff in that code block. Everything I needed was in one place. And sure you could say "you can do that in a html file and just make all the non-html stuff comments". Yes you can, but it is just nicer and better supported in org mode imo. And you can evaluate these code blocks too, and the output will be printed just below the code block :) [0]: | Foo Table | |----------------| | id | | name | | description | [1]: #+begin_src html <h1>Hello, World</h1> <h2>Hope you're doing great!</h2> etc #+end_src