I built this after getting frustrated with unsafe file operations in automation workflows.
Key features:
• Atomic writes (no partial/corrupted files)
• Automatic ZIP backups before every change
• Regex and AST-based text replacement
• 1,050 automated tests with 100% pass rate
• Dual implementation (Python + Go, Go is 20x faster)
Use cases:
• CI/CD pipelines that modify config files
• Automated refactoring scripts
• Any workflow where file corruption would be catastrophic
PyPI: https://pypi.org/project/super-editor/
GitHub: https://github.com/larryste1/super-editor
Would love feedback from the HN community!codebitdaily3 hours ago
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.