The choice of Go for the backend logic and Python for the scripting flexibility is a solid architectural decision for an editor. I’m particularly interested in how you handle the 'atomic' part during high-frequency writes to prevent file corruption. Does it use a WAL (Write-Ahead Logging) approach or simple temporary file swapping? Great to see more local-first tools being built with robustness in mind.
The choice of Go for the backend logic and Python for the scripting flexibility is a solid architectural decision for an editor. I’m particularly interested in how you handle the 'atomic' part during high-frequency writes to prevent file corruption. Does it use a WAL (Write-Ahead Logging) approach or simple temporary file swapping? Great to see more local-first tools being built with robustness in mind.