datefixR
The messy-date parser rewrote its core in Rust and came out 300x faster.
A side-by-side editorial comparison of nanonext and webchem — release velocity, themes, recent moves, and the top alternatives to consider.
nanonext keeps shrinking its build requirements while adding messaging primitives.
The R binding to NNG ships roughly monthly. Since February the package added an HTTP server that can run synchronously or through the later event loop, a zero-copy device forwarder for building brokers and proxies, and support for pthread-enabled WebAssembly targets. Send operations now move the buffer straight into the NNG message, halving peak memory on serialized sends.
Adding chemical databases with one hand while public ones close programmatic access with the other.
webchem is the R interface to public chemical data — retrieving identifiers, properties and structures across roughly a dozen web services. Its release history reads as a running account of which of those services still allow automated access. Version 1.3.0 removed two functions outright because their sources withdrew: ChemIDplus was retired by the NLM, and PAN stopped supporting programmatic access. Version 1.3.1 continues the pattern, updating URLs that stopped working and noting that ChemSpider InChIKey validation now requires an API key like the rest of that provider's endpoints.
The R binding to NNG ships roughly monthly. Since February the package added an HTTP server that can run synchronously or through the later event loop, a zero-copy device forwarder for building brokers and proxies, and support for pthread-enabled WebAssembly targets. Send operations now move the buffer straight into the NNG message, halving peak memory on serialized sends.
Two directions run in parallel. One is making the package installable anywhere — the build-time cmake dependency is gone, so compiling bundled NNG and Mbed TLS needs only a C compiler, and WebAssembly targets are supported. The other is raising the ceiling on what can be built on top: device_aio() for message forwarding, an HTTP and WebSocket server with a content map, and stream buffer control. Bug fixes in recent releases concentrate on memory safety in the bundled C sources.
Given the pace and the tight coupling declared in each release, expect the next version to track a mirai requirement and continue hardening the HTTP server paths that the last two releases have been leaking memory in.
webchem is the R interface to public chemical data — retrieving identifiers, properties and structures across roughly a dozen web services. Its release history reads as a running account of which of those services still allow automated access. Version 1.3.0 removed two functions outright because their sources withdrew: ChemIDplus was retired by the NLM, and PAN stopped supporting programmatic access. Version 1.3.1 continues the pattern, updating URLs that stopped working and noting that ChemSpider InChIKey validation now requires an API key like the rest of that provider's endpoints.
Two opposing forces run through these entries. The package keeps widening its coverage — ChEMBL in 1.2.0, LIPID MAPS and SwissLipids identifiers via Wikidata, structure images, Mol export — while the open, unauthenticated end of the chemical web keeps contracting. The other consistent thread is interface harmonisation: successive releases have converged the get_* functions on the same query and from arguments, tibble returns, and CAS reformatting, so the package feels like one interface rather than a dozen wrappers.
Expect further defunct functions and URL repairs as more providers move behind keys or shut down, alongside occasional additions of sources that remain open. The entries show no sign of a general credential-management layer, which is what a package facing this trend would eventually need.
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 nanonext or webchem.
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 nanonext alternatives → · See all webchem alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. nanonext is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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. nanonext is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top nanonext alternatives in Analytics are ranked by recent ship velocity. Browse the "nanonext alternatives" section above for the current picks, or visit /alternatives/nanonext for the full list with editorial commentary on each.
Top webchem alternatives in Analytics are ranked by recent ship velocity. Browse the "webchem alternatives" section above for the current picks, or visit /alternatives/webchem for the full list with editorial commentary on each.