datefixR
The messy-date parser rewrote its core in Rust and came out 300x faster.
A side-by-side editorial comparison of dfms and patentsview — release velocity, themes, recent moves, and the top alternatives to consider.
Peer-reviewed, feature-complete, and now able to hand its models to other forecasting engines.
dfms estimates dynamic factor models in R, the workhorse for nowcasting economic activity from ragged, mixed-frequency data. The package worked through the Banbura and Modugno (2014) specification in stages — quarterly variables in 0.3.0, AR(1) idiosyncratic errors combined with mixed frequency in 0.4.0 — then declared 1.0.0 feature-complete on completing rOpenSci peer review, adding news decomposition to attribute forecast revisions to specific data releases. Version 1.0.1 adds convert(), which exports fitted models to dlm or KFAS state-space objects.
Dormant for years, then rewritten wholesale when the API underneath it broke.
patentsview is an R client for the USPTO PatentsView API, and version 1.0.0 is less a feature release than a forced reconstruction: the upstream API introduced mandatory keys, renamed and re-nested its endpoints, and the package had to follow. Between 2017 and 2021 the release cadence was roughly annual and almost entirely defensive — wrapping examples so CRAN would not fail during API outages, patching URL encoding, adding throttling retries. The 1.0.0 work restores the package to parity with an API that no longer resembles the one it was written against.
dfms estimates dynamic factor models in R, the workhorse for nowcasting economic activity from ragged, mixed-frequency data. The package worked through the Banbura and Modugno (2014) specification in stages — quarterly variables in 0.3.0, AR(1) idiosyncratic errors combined with mixed frequency in 0.4.0 — then declared 1.0.0 feature-complete on completing rOpenSci peer review, adding news decomposition to attribute forecast revisions to specific data releases. Version 1.0.1 adds convert(), which exports fitted models to dlm or KFAS state-space objects.
The package has finished the implementation programme it set out in its 2023 vignette and is now working on the edges: interoperability with other state-space packages rather than more estimation methods of its own. The convert() function is the clearest signal — instead of implementing smoothing and prediction intervals natively, it hands the model to packages that already have them. The rOpenSci move also puts it on a review-backed, documented footing that research users can cite.
Expect continued interoperability and diagnostic work rather than new estimators, since the maintainer has explicitly scoped the package as complete. Bug fixes against RcppArmadillo releases will likely remain the other recurring driver.
patentsview is an R client for the USPTO PatentsView API, and version 1.0.0 is less a feature release than a forced reconstruction: the upstream API introduced mandatory keys, renamed and re-nested its endpoints, and the package had to follow. Between 2017 and 2021 the release cadence was roughly annual and almost entirely defensive — wrapping examples so CRAN would not fail during API outages, patching URL encoding, adding throttling retries. The 1.0.0 work restores the package to parity with an API that no longer resembles the one it was written against.
The arc here is a client package whose roadmap is entirely dictated by an upstream service it does not control. Every release since 0.2.0 has been reactive — HTTPS migration, throttling, encoding fixes, and now a full breaking rewrite. The one forward-looking piece is retrieve_linked_data(), which follows HATEOAS links the API now returns, meaning the package is starting to navigate the API rather than just query fixed endpoints.
Expect the next releases to be small follow-ups against the reworked API — field list refreshes and error handling for endpoints that behave differently in practice than in the documentation. The entries do not show any independent roadmap, so anything beyond that would depend on further upstream API changes.
Other Analytics 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 dfms or patentsview.
The messy-date parser rewrote its core in Rust and came out 300x faster.
The legend engine mapsf spun out, now covering legend types the parent map package can draw.
R help pages translated on demand by whichever LLM you point it at.
Thematic mapping in base R that finally got a theming system, then spent two years polishing legends.
qualtRics moved its contact functions onto XM Directory days before the old endpoints died.
The tidyverts forecasting core rebuilt model combination on full residual covariance.
See all dfms alternatives → · See all patentsview alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. dfms and patentsview 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. dfms and patentsview 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 Analytics products to evaluate alongside.
Top dfms alternatives in Analytics are ranked by recent ship velocity. Browse the "dfms alternatives" section above for the current picks, or visit /alternatives/dfms for the full list with editorial commentary on each.
Top patentsview alternatives in Analytics are ranked by recent ship velocity. Browse the "patentsview alternatives" section above for the current picks, or visit /alternatives/patentsview for the full list with editorial commentary on each.