$20k bounty was claimed

Original Article ↗ Hacker News Discussion ↗

A $20k bounty to build a Rust-based JavaScript formatter compatible with Prettier has been claimed by the Biome project, delivering dramatic speedups (often tens of times faster) while matching the vast majority of Prettier’s output. Commenters see this as a way to spur performance work on the original JavaScript Prettier, uncover edge-case bugs via an independent implementation, and reduce “config hell” through a shared toolchain. Much of the debate centers on Prettier’s highly opinionated formatting—especially aggressive line wrapping and semantic changes like removing parentheses—alongside broader questions about ecosystem fragmentation, Rust’s role in tooling, and how little core maintainers are paid relative to the impact of their work.

Biome / Rust Port and Performance

  • Biome (Rust-based, originally Rome) reached ~95% compatibility with Prettier’s test suite and claimed the $20k bounty.
  • Discussion highlights large speedups: benchmarks in the thread show Biome being tens of times faster than Prettier on some repos, and faster than dprint when using multiple cores.
  • Some argue Rust naturally yields big wins for parsing/string-heavy workloads; others think “Rust = fast” is partly hype and that performance depends on implementation details.

Motivation and Effects of the Bounty

  • The bounty was framed as a way to:
    • Obtain a high‑performance, Prettier‑compatible alternative.
    • Use an external implementation as a “sanity check” to uncover bugs and questionable decisions in Prettier.
    • Create real competition to spur performance work on the JS implementation.
  • One maintainer reportedly was “nerd‑sniped” into aggressively profiling and speeding up Prettier itself.

Formatting Philosophy & Pain Points

  • Many appreciate “no‑config” opinionated formatting to kill bikeshedding, similar to gofmt/Black.
  • Others strongly dislike Prettier’s behavior, especially:
    • Aggressive line wrapping based on print width, causing noisy diffs and harder reviews.
    • Refusal to honor author-chosen line breaks and semantic grouping (chained calls, template literals, math expressions).
    • Modifying parentheses and layout in ways that obscure intent.
  • Some resort to // prettier-ignore comments or disable Prettier entirely; others prefer alternative formatters (dprint, editor formatters, deno fmt).

Ecosystem, Compatibility, and Adoption

  • Biome is praised for fast progress and close compatibility, but users ask about:
    • Prettier config (.prettierrc) compatibility and migration paths.
    • Tailwind CSS class sorting and plugin extensibility as blockers for full adoption.
  • There is broader enthusiasm for the “Rust wave” in tooling (analogies to Ruff in Python, etc.), alongside concerns that Rust-based tools may attract fewer contributors than JS.

WASIX / Wasmer Side Thread

  • A long subthread debates compiling Biome to WASIX via Wasmer:
    • Pro side: sandboxed, near‑native execution with controlled FS/network access; more complete POSIX-like APIs (threads, sockets, subprocesses).
    • Critical side: sees WASIX as a divergent, potentially “hostile” fork from the WASI standards effort, with governance and incentive concerns.
  • Both sides agree WASI Preview 2 lacks some needed features today; disagreement centers on whether forking is justified and how it affects ecosystem cohesion.

Open Source Funding and Value

  • Commenters note that key maintainers receiving ~$1.5k/month is very low compared to the value Prettier provides (ubiquity in JS/TS projects).
  • A large portion of the thread debates realistic contractor rates ($100–$500+/hour) and whether $20k is “a bargain” for this work.