← Back to home
Comparison · Infra & APIs

Biome vs DNSControl

A side-by-side editorial comparison of Biome and DNSControl — release velocity, themes, recent moves, and the top alternatives to consider.

Biome vs DNSControl: at a glance

FeatureBiomeDNSControl
SectorInfra & APIsInfra & APIs
Velocity score5.05.0
Sparks · 30d00
Top themeslint-rules, markdown-support, framework-coverage, css-formatterdns, infrastructure-as-code, refactor, release-candidates
Last editorial update2h ago9h ago
WebsiteVisit →Visit →

What is Biome?

Biome's patch train keeps adding rules — and is quietly growing a Markdown linter.

Six patch releases since mid-June, each mixing new nursery rules with parser and formatter fixes. 2.5.8 adds useReactCompiler, which surfaces React Compiler's own lint diagnostics through Biome, and makes HTML style attribute values parse as CSS so every CSS rule applies inside them. Framework coverage keeps deepening — Svelte legacy {@const} tags, Vue instance properties, Tailwind arbitrary values — and the JavaScript API package reached 6.0.0 with a byte-to-UTF-16 span helper.

Read the full Biome trajectory →

What is DNSControl?

DNSControl is rewriting its record internals in public, one release candidate at a time

DNSControl is mid-way through a v5 refactor being shipped as a visible candidate series — rc1 through rc4 in roughly two weeks, all of them explicitly promising zero user-facing change. The work replaces how DNS record fields are stored internally with a dnsv2.RDATA type, with legacy structs converted bidirectionally so existing providers keep working untouched. Two other threads run alongside: migrating the miekg/dns dependency from GitHub to Codeberg, now complete and no longer dual-imported, and removing old fields to cut memory use. The release notes read as direct appeals to users — naming nine providers nobody has tested and asking for volunteers, and inviting anyone to a monthly community call.

Read the full DNSControl trajectory →

Biome vs DNSControl: editorial side-by-side

B
Biome
INFRA · APIS
5.0

Biome's patch train keeps adding rules — and is quietly growing a Markdown linter.

◆ Current state

Six patch releases since mid-June, each mixing new nursery rules with parser and formatter fixes. 2.5.8 adds useReactCompiler, which surfaces React Compiler's own lint diagnostics through Biome, and makes HTML style attribute values parse as CSS so every CSS rule applies inside them. Framework coverage keeps deepening — Svelte legacy {@const} tags, Vue instance properties, Tailwind arbitrary values — and the JavaScript API package reached 6.0.0 with a byte-to-UTF-16 span helper.

◆ Where it's heading

The rule set is widening along two axes at once: frameworks and file types. Framework rules are now specific enough to argue about Svelte runes rather than generic JavaScript, and CSS handling has pushed into HTML attributes and registered custom properties. The larger move sits in 2.5.8's PR list rather than its changelog — a markdown linter, a markdown rule generator, a markdownlint rule source, a two-phase markdown parser, and a first rule in useTopLevelHeading, none of it documented for users yet.

◆ Prediction

Markdown linting looks close enough to ready that it should appear in the changelog proper rather than the PR list, most likely as nursery rules in the next minor.

D
DNSControl
INFRA · APIS
5.0

DNSControl is rewriting its record internals in public, one release candidate at a time

◆ Current state

DNSControl is mid-way through a v5 refactor being shipped as a visible candidate series — rc1 through rc4 in roughly two weeks, all of them explicitly promising zero user-facing change. The work replaces how DNS record fields are stored internally with a dnsv2.RDATA type, with legacy structs converted bidirectionally so existing providers keep working untouched. Two other threads run alongside: migrating the miekg/dns dependency from GitHub to Codeberg, now complete and no longer dual-imported, and removing old fields to cut memory use. The release notes read as direct appeals to users — naming nine providers nobody has tested and asking for volunteers, and inviting anyone to a monthly community call.

◆ Where it's heading

The stated goals are about future velocity rather than present features: making new DNS record types faster to adopt and custom record types easier to implement. That is a bet that the bottleneck on supporting new record types was the internal representation, and it is being paid for with a long candidate series rather than a big-bang release. The provider conversion finished during this window — rc3 declares all providers converted with long-tail work remaining — so the refactor is past its riskiest stretch.

◆ Prediction

The maintainer states v5.x is on schedule to ship before September, and the untested-provider list is the visible blocker; expect further candidates focused on provider coverage rather than new goals.

Alternatives to Biome and DNSControl

Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Biome or DNSControl.

See all Biome alternatives → · See all DNSControl alternatives →

Recent activity from Biome and DNSControl

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 14h agoBiomeReact Compiler rule lands; HTML style attributes lint as CSS
  2. 7d agoBiomeTailwind arbitrary values and noExtendNative join the rule set
  3. 8d agoDNSControlDNSControl v5 rc4 completes the move to Codeberg-hosted miekg/dns
  4. 10d agoDNSControlDNSControl v5 rc3 finishes converting every provider
  5. 14d agoBiomenoMisusedPromises performance regression fixed
  6. 19d agoDNSControlDNSControl v5 rc2 continues the internal rewrite
  7. 21d agoBiomeBigint switch cases fixed; partial-type diagnostics suppressed
  8. 21d agoDNSControlDNSControl v5 rc1 lays out the dnsv2.RDATA refactor
  9. 27d agoBiomeAccessibility fixes; noCommentText autofix no longer hangs
  10. 1mo agoBiomeCSS Modules parser panic and Svelte false positives fixed

Frequently asked questions

What is the difference between Biome and DNSControl?

They serve adjacent needs but don't currently overlap on shipped themes. Biome and DNSControl are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is Biome better than DNSControl?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Biome and DNSControl are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to Biome?

Top Biome alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Biome alternatives" section above for the current picks, or visit /alternatives/biome for the full list with editorial commentary on each.

What are the best alternatives to DNSControl?

Top DNSControl alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "DNSControl alternatives" section above for the current picks, or visit /alternatives/dnscontrol for the full list with editorial commentary on each.