Zoho Creator
Three months on, Zoho is still selling the HDS certification rather than shipping past it.
A side-by-side editorial comparison of nuggets and tidyprompt — release velocity, themes, recent moves, and the top alternatives to consider.
A pattern-mining package that keeps making its own search cheaper rather than wider.
nuggets is an R package for searching data for conditional patterns - association rules, contrast patterns, correlations - through its dig*() family. The 2.2.x line has settled into a steady rhythm of making that search faster and more inspectable rather than adding new pattern types. 2.2.3 adds permute(), improves axiom-based filtering in the excluded argument, and attaches a search_stats attribute to every dig*() result, so the cost of a search is now reported alongside its output.
An R prompting framework hands its provider plumbing to ellmer and inherits MCP tools
tidyprompt composes LLM prompts out of stackable 'prompt wraps' — answer_as_json(), answer_as_category(), answer_using_tools() — and validates what comes back. Its recent history is one decision: stop maintaining a provider layer. llm_provider_ellmer() arrived experimental, then became the path through which structured output, tool calling and streaming are done natively. The newest release adds dataframe and numeric extraction wraps and lets send_prompt() take an ellmer chat object directly.
nuggets is an R package for searching data for conditional patterns - association rules, contrast patterns, correlations - through its dig*() family. The 2.2.x line has settled into a steady rhythm of making that search faster and more inspectable rather than adding new pattern types. 2.2.3 adds permute(), improves axiom-based filtering in the excluded argument, and attaches a search_stats attribute to every dig*() result, so the cost of a search is now reported alongside its output.
The arc since 2.1.0 runs toward a leaner, faster core. Dependencies went first - Shiny moved to Suggests, BH and RcppThread dropped - then the search itself: 2.2.2 brought a sparse bit chain, and 2.2.3 adds condition-prefix handling and caching of conjunction supports. New user-facing surface arrives in small, single-function increments (dig_ancestors(), cluster_associations(), now permute()) rather than in themed releases. The search_stats attribute is the first move toward letting users see why a search was expensive rather than only how long it took.
Expect the next release to continue in the same shape - another caching or pruning refinement to the dig*() core plus one or two helper functions. The search_stats attribute is the kind of instrumentation that usually precedes tuning controls, so surfacing knobs for the new prefix and support caches is the plausible follow-up.
tidyprompt composes LLM prompts out of stackable 'prompt wraps' — answer_as_json(), answer_as_category(), answer_using_tools() — and validates what comes back. Its recent history is one decision: stop maintaining a provider layer. llm_provider_ellmer() arrived experimental, then became the path through which structured output, tool calling and streaming are done natively. The newest release adds dataframe and numeric extraction wraps and lets send_prompt() take an ellmer chat object directly.
Two lines run together. One is catalogue growth — every release adds a wrap for another answer shape. The other is consolidation onto ellmer, and that is where the leverage is: because ellmer tool definitions are what mcptools::mcp_tools() returns, tidyprompt gained access to Model Context Protocol servers without writing an MCP client. Its own Gemini provider is already marked superseded. Note the feed's stamps lie — 0.1.0, 0.2.0 and 0.3.0 were all published within two hours of each other in reverse version order.
The remaining first-party providers are the obvious next thing to fold in: the Gemini one is already superseded, and the Ollama and OpenAI providers carry the same duplicated plumbing. Expect the wrap catalogue to keep growing on top of an increasingly ellmer-only base.
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 nuggets or tidyprompt.
Three months on, Zoho is still selling the HDS certification rather than shipping past it.
Retool now debugs the apps its agent builds, and versions them across instances.
exametrika breaks its own numbers to fix them, and ships the fit statistic nominal data lacked.
Traefik's 2.11 line spends August fixing the names it generates for Kubernetes resources.
nginx returns to feature work with PROXY v2 upstream writes, and quietly adds JSON to core.
ESPHome closes the 2026.8 cycle, but the release body is a bare link to the real notes.
See all nuggets alternatives → · See all tidyprompt alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Infra & APIs. nuggets is currently shipping more aggressively (velocity 5.0 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. nuggets is currently shipping more aggressively (velocity 5.0 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 Infra & APIs products to evaluate alongside.
Top nuggets alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "nuggets alternatives" section above for the current picks, or visit /alternatives/nuggets for the full list with editorial commentary on each.
Top tidyprompt alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "tidyprompt alternatives" section above for the current picks, or visit /alternatives/tidyprompt for the full list with editorial commentary on each.