Skip to content

docs: add dev.to long-form launch copy#145

Open
zhijiewong wants to merge 2 commits into
mainfrom
add-devto-copy
Open

docs: add dev.to long-form launch copy#145
zhijiewong wants to merge 2 commits into
mainfrom
add-devto-copy

Conversation

@zhijiewong

Copy link
Copy Markdown
Contributor

Adds a dedicated dev.to section to launch-copy.md.

dev.to is a friendlier long-form community than HN/Reddit; it expects a complete article with cover image, up to 4 tags, and a TL;DR up front. The previous "other venues" bullet pointed at the existing announcement doc, but that's HN-shaped, not dev.to-shaped.

New section includes:

  • Title framed as a how-to write-up
  • Cover image suggestion (assets/bench-comparison.png)
  • 4 tags: #typescript #javascript #performance #showdev
  • TL;DR up front (dev.to convention)
  • Code blocks for the algorithm sections (linear-recurrence vs cumulative-sum diff)
  • Same campaign discipline elsewhere: C++ framing (no Rust), suite-scoped caveats, fuzzer-found-bug story, validation summary

🤖 Generated with Claude Code

zhijiewong and others added 2 commits May 23, 2026 15:23
Previously the V2EX and 掘金 copy only existed in chat
ephemera; committing them to the canonical launch-copy file
so the campaign assets are version-controlled.

Both versions use the cleaned C++/native framing (no Rust
detour) consistent with PR #143's revisions:

- V2EX 分享创造 post (short, casual register)
- 掘金 long-form article (with section headers, code blocks,
  validation-infra-paid-off story, API stability call-out)
- Other Chinese venues mentioned briefly: 知乎, 少数派
- Suggested ordering: 掘金 first as "authoritative long
  read", V2EX/知乎 link back to it

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
dev.to is a friendlier, long-form-oriented community than HN or
Reddit; it expects a complete article with cover image, 4 tags,
and a TL;DR up front. The previous "Other venues" bullet for
dev.to just pointed at "the announcement doc" which isn't quite
right — the announcement doc is structured as an HN-style read,
not a dev.to article.

Added a full dev.to-tailored section:
- Title framed as a how-to write-up, not a release announcement
- 4 dev.to tags: #typescript #javascript #performance #showdev
- Cover image: bench-comparison.png
- TL;DR up front (dev.to convention)
- Markdown code blocks for the algorithm sections (linear
  recurrence vs cumulative sum diff)
- Same content discipline as the rest of the campaign:
  C++ (not Rust) framing, suite-scoped caveats, fuzzer-found-
  bug story, validation infra summary

Removed the outdated "dev.to" line from the "Other venues"
section since it now has its own dedicated section.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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