November 29, 2025
Exit code: drama 1
Zigbook Is Plagiarizing the Zigtools Playground
Dev world drags “zero‑AI” Zigbook over alleged copy‑paste and a license snub
TLDR: Zigtools says Zigbook copied its web playground and skipped required credit under an open license, then closed a fix attempt. The community’s split between ethics and law, worrying about harm to newcomers and asking if trademarks or any central authority in Zig can actually do something.
The Zig community lit up after Zigtools accused the new “zero‑AI” Zigbook of copy‑pasting their online code playground and shipping it as a flashy “high‑voltage beta.” The claim: Zigbook’s web files are allegedly “byte‑for‑byte” identical to Zigtools’ custom builds, with chunks of JavaScript matching too. The kicker? Zigtools says the open‑source MIT license—basically “you can use this, but credit us”—was ignored, and a polite fix was shut down. Cue pitchforks.
On Hacker News, the mood swings between courtroom and comedy club. One camp fumes that this hurts beginners—“misinformation kills momentum,” says one user—while another shrugs that in open source, attribution drama is sadly routine. The hot debate: moral plagiarism vs. legal violation. As one commenter put it, plagiarism is dirty, but licenses are the law. Some wonder if Zig’s name or mascot is trademarked; others note the project’s decentralized nature means there’s no “official Zig police” to step in. Meanwhile, the internet’s roasting the “no AI here” promise, joking it reads like “LLM slop with a mustache,” and riffing on the copied error text as an “exit with credibility code.” It’s part tech whodunit, part community therapy session, with a side of meme-fueled justice.
Key Points
- •Zigtools alleges Zigbook’s Zig playground uses identical custom WASM binaries (zig.wasm and zls.wasm) from the Zigtools Playground.
- •Zigtools provides SHA-256 checksums and states the WASM files were archived on the Internet Archive for verification.
- •Parts of Zigbook’s JavaScript code are reportedly copied, with some sections identical, including a specific exit-code logging string.
- •Zigbook’s ZLS integration is described as non-functional due to missing the required JavaScript ZLS API used to interact with the ZLS WASM binary.
- •Zigtools claims Zigbook failed to comply with MIT license attribution requirements and says a corrective PR was closed and its description deleted.