PerformanceContent SiteReviewsIndie

NativeMark Bench

Standardized benchmark comparing Electron and native Markdown editors

Problem
Many developers are fed up with Electron editors eating 500MB of RAM and 3% idle CPU, which is exactly why one builder wrote a native editor from scratch. But ordinary users have no comparable numbers to know which editor is truly lightweight, relying only on word of mouth.
Solution
A ready-to-run benchmarking tool that launches candidate editors in a clean environment and records cold start time, idle CPU, memory footprint with a large workspace, and binary size, then outputs a shareable comparison report. Expandable into a general lightweight-software benchmark site.
Users
Performance-sensitive writers, developers, software reviewers, corporate buyers
MVP
macOS-first measurement scripts; cover 5-10 mainstream Markdown editors; auto-generate start/memory/CPU/size reports; export PNG or web page; allow users to request new tools
Revenue
Affiliate links on benchmark pages; paid vendor submissions; membership for historical trends and raw data
Why now
A native app revival and Electron fatigue are happening at the same time, yet neutral, reproducible performance comparisons are scarce, letting indies build a trust asset quickly

Source discussions · 1

  1. Hacker NewsShow HN: Flo State, a fast, minimalist, native Markdown editor for macOS3↑ 0
← Back to list