Skip to content

docs: clarify Yoga is C++, Rust was the Pilates port path#143

Merged
zhijiewong merged 2 commits into
mainfrom
clarify-rust-vs-cpp
May 23, 2026
Merged

docs: clarify Yoga is C++, Rust was the Pilates port path#143
zhijiewong merged 2 commits into
mainfrom
clarify-rust-vs-cpp

Conversation

@zhijiewong

Copy link
Copy Markdown
Contributor

Caught during a pre-Reddit-post review: the "Rust + WASM port" framing was ambiguous and could be read as "Yoga is Rust" (which is wrong — Yoga has been C++ → WASM since 2014).

Updated all 5 mentions across the announcement doc and the launch copy. The argument is unchanged — algorithmic fix in TS beats a hypothetical native-compiled rewrite — but the language is now unambiguous: Yoga is C++; Rust would have been the migration target for Pilates, since Rust has better JS-migration tooling than C++ in 2026.

Removes a reasonable comment-thread objection ("but Yoga is C++") before it can land.

🤖 Generated with Claude Code

zhijiewong and others added 2 commits May 23, 2026 15:10
The "Rust + WASM port" framing was ambiguous — readers could
infer Yoga is Rust, which is wrong (Yoga is C++ → WASM since
~2014). Updated all 5 mentions across the announcement doc and
launch copy to:

- Acknowledge Yoga itself is C++
- Clarify Rust was the modern port path *for Pilates* (better
  JS-migration tooling than C++ in 2026)
- Frame the lesson as "pure TS vs native-compiled-to-WASM",
  language-agnostic

The argument unchanged: algorithmic fix in TS beats a
hypothetical native-compiled rewrite because Yoga's edge was
algorithmic, not arithmetic-speed. The clarification just makes
sure no commenter can derail the post with "but Yoga is C++".

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Per author preference: the post compares pure TS against Yoga's
C++ (the actual benchmark) — bringing Rust in as "the port we
considered for Pilates" was a distraction that invited the
"but Yoga is C++" objection while not adding value.

Generalized all five mentions to "native-compiled-to-WASM" /
"native code" framing. The argument unchanged: algorithmic fix
in TS beats a hypothetical native-compiled rewrite because
Yoga's edge was algorithmic, not arithmetic-speed.

Section header in r/programming body is now "Why pure TS over
C++" — direct apples-to-apples with Yoga, matches the question
readers actually ask.

(Ratatui mention in STRATEGY.md retained — that's naming a Rust
TUI library as comparison point, not the port-path framing.)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@zhijiewong zhijiewong merged commit 167551f into main May 23, 2026
4 checks passed
zhijiewong added a commit that referenced this pull request May 23, 2026
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>
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