Oh God, no wonder she's always overworked 🤣 I thought they were a myth

Reply to this note

Please Login to reply.

Discussion

No, I use it, sometimes, but I'm mostly in Obsidian or Codium or Nostr, now.

Codium? Like VSCodium? That's where I work for code.

I think for long-form articles and content, LogSeq doesn't really do anything spectacular, unless you're comfortable sorting segments up into a graph. I understand why overall LogSeq is less popular- because many users are "do'ers" more than "archivers". LogSeq as a package aims to serve do'ers who need to manage their notes in a graph type ecosystem. As well as archive them, or publish them in theory.

So generally Joplin/Obsidian are by far the most popular solutions. VSCodium for devs. And emacs and so on for really efficient devs. I have never gotten into emacs, but I actually do have an interest in trying it some day. I could never really get comfortable with Vim either. There is an insanely fleshed out terminal version of essentially LogSeq. I could dig it up some time. Never used it myself but certainly cool to see.

We exist! Almost attempted an emacs package. Figured the more "sensible" path would be to make an elisp wrapper for NAK and find general patterns others could work into for own cli stuff. Can post kind1 now 😇

also 😉

https://github.com/nobiot/org-transclusion?tab=readme-ov-file