bad3r

Leaking memory is safe

Rust’s memory safety guarantees make it difficult, but not impossible, to accidentally create memory that is never cleaned up (known as a memory leak). Preventing memory leaks entirely is not one of Rust’s guarantees in the same way that disallowing data races at compile time is, meaning memory leaks are memory safe in Rust. We can see that Rust allows memory leaks by using Rc and RefCell: it’s possible to create references where items refer to each other in a cycle. This creates memory leaks because the reference count of each item in the cycle will never reach 0, and the values will never be dropped.

Unlike obsidian Logseq is FOSS. Arguably that doesn’t directly contribute to it being more private but I would rather use and support FOSS.

its lack of protocol support from firefox end. Firefox doesn't support the FS API. The logseq team plans to migrate to a different protocol that is supported by FF OPFS

you have complete control over your data with logseq.

If you use emacs, you have no right to call something unfriendly lol /s. Logseq supports both markdown and or-mode. I don't use orgmode, but to make an alias in Markdown, all you need to do is [alias]([[page name]])

I do agree that UX could use a lot of improvement.

Hey there! great to see you too. Hopefully, once the database version is released you will give it another shot!

yes