Skip to content

feat: derive published browser counts, and add Naver Whale - #7

Merged
vamgan merged 3 commits into
mainfrom
test/add-a-browser
Aug 25, 2026
Merged

vamgan merged 3 commits into
mainfrom
test/add-a-browser

Conversation

@vamgan

@vamgan vamgan commented Aug 25, 2026

Copy link
Copy Markdown
Owner

Someone asked what "three lines and no new skill" actually means, so I measured it by adding a real browser instead of asserting it.

The measurement

Adding Naver Whale took exactly three hand-written lines across two files:

File Line
references/app-data-locations.md the table row
scripts/platforms.py → CHROMIUM where the data lives, per platform
scripts/platforms.py → PROCESS_NAMES what the running process is called

locate whale and running whale both resolved, and all three skills covered it immediately. No new skill, no new code.

But it broke three tests, which is the useful part

The browser count published in the README and on the site was instantly wrong. Nothing except those drift tests would have caught it.

So the claim was still false. Adding a browser really cost three lines plus remembering to update two numbers and a list by hand — and "remember to update it" is how the earlier "one line in a table" claim went stale in the first place.

The fix: derive the numbers

sync-skills.py now reads platforms.py and rewrites, in both the README and the site:

  • the browser count (Eleven browsers, one markdown file)
  • the Chromium browser list in the coverage table and the site chips

CI fails if they drift. Adding a browser is three lines and one sync command again, this time accurately.

Whale stays

It is a real browser with real users, not a test fixture. All three skills cover it.

109 tests green.

vamgan added 3 commits August 24, 2026 23:43
Answering "what does three lines actually mean" by doing it. Adding Naver
Whale took three hand-written lines across two files: the reference table
row, the family path, and the process name.

It worked, and it also broke three tests, which is the useful part. The
browser count published in the README and on the site was suddenly wrong,
and nothing but those tests would have noticed. That made the claim
false: adding a browser really cost three lines plus remembering to
update two numbers and a list by hand.

So the published numbers are derived now. sync-skills.py reads
platforms.py and rewrites the count and the browser list in both the
README and the site, and CI fails if they drift. Adding a browser is
three lines and one command again, this time accurately.

Whale is kept rather than reverted. It is a real browser with real users
in Korea, and all three skills now cover it.
The coverage section still said "three lines and no new skill", which
omits the sync command and is the same overstatement just corrected
everywhere else. It now says three lines and one command, names the three
places, and cites Naver Whale as the browser added exactly that way.
The coverage copy said "Adding Vivaldi took three lines", which only
lands if you already know Vivaldi is a browser. Most readers do not, and
swapping in Naver Whale made it worse.

The prose now says every browser listed above was added that way, which
needs no prior knowledge and is equally true. The niche names stay in the
supported-browser list, which is exactly where an unfamiliar name is
useful rather than confusing.
@vamgan
vamgan force-pushed the test/add-a-browser branch from a9bc7bc to b15010a Compare August 25, 2026 03:43
@vamgan
vamgan merged commit 160e7fd into main Aug 25, 2026
7 checks passed
@vamgan
vamgan deleted the test/add-a-browser branch August 25, 2026 03:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant