Cronicle
The job scheduler's release stream is now almost entirely vulnerability patching and authorization hardening.
A side-by-side editorial comparison of quarto and webfakes — 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.
A fake web server for tests that keeps closing the gap with the real thing.
webfakes runs a real HTTP server inside R tests so packages can exercise network code without hitting the internet. Its releases follow a consistent logic: find a class of behaviour that only the real internet could reproduce, then implement it locally. HTTPS arrived in 1.4.0; before that the httpbin clone reached full parity with the Python original, and a fake git HTTP server landed alongside CGI middleware. The most recent release, 1.5.0, is about the server's own rough edges — keep-alive timeouts, locale-independent HTTP date parsing, and trailing-slash route matching.
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.
webfakes runs a real HTTP server inside R tests so packages can exercise network code without hitting the internet. Its releases follow a consistent logic: find a class of behaviour that only the real internet could reproduce, then implement it locally. HTTPS arrived in 1.4.0; before that the httpbin clone reached full parity with the Python original, and a fake git HTTP server landed alongside CGI middleware. The most recent release, 1.5.0, is about the server's own rough edges — keep-alive timeouts, locale-independent HTTP date parsing, and trailing-slash route matching.
The package is converging on being indistinguishable from a real server for test purposes, which is the only way it stays useful — every unsupported protocol feature is a piece of code someone cannot test offline. The remaining work has visibly shifted from missing endpoints to correctness details: date header parsing under unusual locales, keep-alive tuning, request body handling across content types.
Expect continued fidelity work against real-server behaviour rather than new app types, with HTTP/2 or authentication schemes the most plausible next gaps given the direction HTTPS opened. The entries do not indicate a specific planned feature.
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 webfakes.
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.
R's old dependency manager now runs on a vendored copy of its own successor.
See all quarto alternatives → · See all webfakes alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. quarto and webfakes 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 webfakes 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 webfakes alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "webfakes alternatives" section above for the current picks, or visit /alternatives/webfakes for the full list with editorial commentary on each.