Add SeqLog to Proprietary - #122
Open
nekocode wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adding SeqLog to the Proprietary section.
Disclosure: I am the author.
SeqLog is a native macOS outliner in the Logseq/Roam lineage, built with Swift/SwiftUI/AppKit and a Rust core rather than Electron.
Why it belongs on a list that tracks storage format so carefully: the Markdown files are the database. There is no index and no sidecar DB, so search is ripgrep over the folder and any external tool, including a coding agent pointed at the vault, sees exactly what the app sees. That property became less common after Logseq 2.0 moved its source of truth into SQLite.
Checklist:
I did not add a row to the Quick Comparison table since that section is scoped to the most-searched tools.