ESPHome
ESPHome ships on a calendar, and the August beta train is already three builds deep.
A side-by-side editorial comparison of quarto and quarto-r — release velocity, themes, recent moves, and the top alternatives to consider.
Quarto's editor extension is quietly becoming Positron-first while keeping VS Code parity.
This is the Quarto extension for VS Code and Positron — cell execution, preview and render, the visual editor, snippets, and the language-server plumbing that makes .qmd files behave like real code documents. The last several releases have pushed the editing experience toward parity with ordinary source files: diagnostics inside code cells, code symbols and cells in the outline, semantic highlighting, and clickable file links with autocompletion in _quarto.yml. A large share of every release is now Positron-specific work rather than generic VS Code support.
The R side of Quarto stopped being a render wrapper and became a project interface
The quarto R package gives R users programmatic access to the Quarto CLI, and its 1.4 release is where that access stopped being a thin call to quarto render. Project creation, extension installation, template use, environment diagnostics and a vignette engine all arrived together, and 1.5.0 followed by changing how output paths are communicated to the CLI — through Quarto metadata rather than a command-line flag.
This is the Quarto extension for VS Code and Positron — cell execution, preview and render, the visual editor, snippets, and the language-server plumbing that makes .qmd files behave like real code documents. The last several releases have pushed the editing experience toward parity with ordinary source files: diagnostics inside code cells, code symbols and cells in the outline, semantic highlighting, and clickable file links with autocompletion in _quarto.yml. A large share of every release is now Positron-specific work rather than generic VS Code support.
Two patterns hold across releases. First, Positron is where new surface appears first — notebook editor commands, statement execution, runtime-aware language selection for new cells, and a bundled-CLI preference setting all landed as Positron features. Second, the extension is steadily stepping back from things dedicated tooling does better, giving up .typ files to Typst extensions and commenting out IPython magics in the virtual document so Ruff and Pyrefly stop flagging them. The multi-language story keeps widening, with Julia cells joining Python and R for in-editor execution.
Given how much recent work has been notebook-editor commands and .ipynb conversion, expect further consolidation of the notebook and .qmd paths behind shared commands rather than new authoring features.
The quarto R package gives R users programmatic access to the Quarto CLI, and its 1.4 release is where that access stopped being a thin call to quarto render. Project creation, extension installation, template use, environment diagnostics and a vignette engine all arrived together, and 1.5.0 followed by changing how output paths are communicated to the CLI — through Quarto metadata rather than a command-line flag.
The package's job is to stay a faithful surface over a CLI it does not control, and the releases show what that costs. Version numbers track the Quarto release they target, tests are adapted around upstream regressions, and behaviour is reworked when the CLI changes — quarto_use_template() now errors clearly in non-empty directories because interactive prompting was never suitable for programmatic use. The 1.5.1 release exists entirely so CRAN checks pass on machines where Quarto is not installed at all.
Expect the next release to track the next Quarto CLI version, with the open question in the feed being how --no-prompt behaviour settles upstream for template use. Feature work here follows the CLI rather than leading it.
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 quarto or quarto-r.
ESPHome ships on a calendar, and the August beta train is already three builds deep.
The job scheduler's release stream is now almost entirely vulnerability patching and authorization hardening.
Helm runs two release trains in lockstep while v3 walks toward end-of-life.
The R package-quality checker returns from CRAN limbo with checks you can select by category.
Ten releases in six days, methodically porting Quarto's surface into a Rust binary.
The metadata cache under pak now speaks to authenticated and corporate repositories.
See all quarto alternatives → · See all quarto-r alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — quarto — within Infra & APIs. quarto and quarto-r are shipping at a similar cadence (velocity 0.0 vs 0.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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. quarto and quarto-r are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top quarto alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "quarto alternatives" section above for the current picks, or visit /alternatives/quarto for the full list with editorial commentary on each.
Top quarto-r alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "quarto-r alternatives" section above for the current picks, or visit /alternatives/quarto-r for the full list with editorial commentary on each.