Kindling vs Parca

Kindling is a free desktop writing app for fiction writers who plan their stories while drafting. Its writing view can show scene beats as expandable prompts, or switch to a full-page prose editor. Tagged characters and locations appear in a reference panel with descriptions, notes, and custom fields. Projects import from Plottr, Scrivener, yWriter, Obsidian Longform, novelWriter, and Markdown, then export to DOCX, EPUB, HTML, plain text, Markdown, Scrivener, Longform, and novelWriter. Editorial review uses a .kindling-review file containing tracked suggestions and threaded comments; feedback can be imported and changes accepted or rejected. Screenplay projects add slugline entry, page-count estimates, and one-page or five-page DOCX treatments. Data stays in local SQLite files, with no account, analytics, telemetry, or usage tracking required. Writing and review work offline. Kindling is open source under MIT, does not use AI to analyze writing, and runs on Windows 10+, macOS 12+, and x86_64 Linux.

Parca is a self-hosted profiling system that collects and stores CPU, memory, I/O, and other profiles for queries over time. Its eBPF-based Parca Agent captures user-space and kernel-space stack traces, while the system also accepts valid pprof-formatted profiles pushed through gRPC or pulled from targets over HTTP. Users can query by labels, compare dimensions such as processes or code versions, and view profiles in the web interface with Icicle Graphs. A Grafana plugin can display profiles stored in Parca. The agent supports automatic profiling for languages including C, C++, Go, Rust, .NET, Deno, Erlang, Java, Julia, Node.js, Wasmtime, PHP, Ruby, and Python. Installation options include binaries, containers, Kubernetes, and Snaps. Parca is open source under the Apache 2 License and is free. The agent requires Linux kernel 4.18 or newer and privileged access to load eBPF programs. Parca says it receives profiling statistics and function-name metadata, not binaries or source code.