jSDM
Joint species distribution models in Gibbs-sampled C++, quiet since 2023.
A side-by-side editorial comparison of emuR and tidyprompt — release velocity, themes, recent moves, and the top alternatives to consider.
The R half of the EMU speech database system, fixing what was quietly broken.
emuR is the R interface to the EMU Speech Database Management System — loading annotated speech corpora, running hierarchical queries over annotation levels, extracting signal track data, and serving corpora to the EMU-webApp for browser-based annotation. It is at 2.6.0 on a slow cadence of roughly one release a year. Recent work has centred on the CRUD operations for annotation items and on widening what serve() can hand the web application.
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.
emuR is the R interface to the EMU Speech Database Management System — loading annotated speech corpora, running hierarchical queries over annotation levels, extracting signal track data, and serving corpora to the EMU-webApp for browser-based annotation. It is at 2.6.0 on a slow cadence of roughly one release a year. Recent work has centred on the CRUD operations for annotation items and on widening what serve() can hand the web application.
The releases read as a package being brought up to the standard its own API implied. delete_itemsInLevel() shipped in 2.1.1 as a first version, was described in 2.5.0 as heavily flawed and now usable, and the create/update/delete family is still called ongoing work. Alongside that, the query engine was rewritten onto CTEs and the signal-processing layer is being opened past the bundled wrassp, starting with Matlab. Speed work recurs — SQLite transactions, prepared statements, on-the-fly caching — consistent with corpora outgrowing the original design.
Two threads are explicitly unfinished: the CRUD documentation and behaviour, described as ongoing, and the add_signalVia family, described as a draft starting with Matlab. Expect the next release to advance one of them rather than open new ground.
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 emuR or tidyprompt.
Joint species distribution models in Gibbs-sampled C++, quiet since 2023.
An ecosystem model starts tracking carbon isotopes and land-use change.
Ten years in, US mapping splits its data out and finally adds Puerto Rico.
Fitness-tracking analysis in slow maintenance, still absorbing upstream breakage.
State-panel tooling holding steady since its 2020 data and ergonomics release.
Five years of compiler and CRAN fixes on a capture-recapture package.
See all emuR 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. emuR and tidyprompt 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. emuR and tidyprompt 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 emuR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "emuR alternatives" section above for the current picks, or visit /alternatives/emur 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.