midr
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
A side-by-side editorial comparison of surveycore and ToolJet — release velocity, themes, recent moves, and the top alternatives to consider.
surveycore declared its API stable with every survey design type covered.
surveycore is the estimation engine of a two-package survey stack, handling design objects and variance estimation while surveytidy supplies the dplyr verbs on top. The June release marks it 1.0.0 and states the API is complete and stable across Taylor series linearization, replicate weights, two-phase and non-probability designs, with means, totals, frequencies, quantiles, ratios, correlations, regression, t-tests, ANOVA and effective sample size all in place.
Observability lands on OpenTelemetry semconv in the LTS train
ToolJet runs two lines in parallel and both are in a steady groove. The LTS train picked up frontend and app observability built on OpenTelemetry semantic conventions plus primary and backup access, following a 3.20.212 release that carried the substantive feature batch — dynamic height across Timeline, Filepicker, Reorderable List, RadioButtonV2 and Tags, dynamic number formats on Currency Input, camera flip on mobile, and AI build notifications. The beta line is mostly fixes and LTS cherry-picks.
surveycore is the estimation engine of a two-package survey stack, handling design objects and variance estimation while surveytidy supplies the dplyr verbs on top. The June release marks it 1.0.0 and states the API is complete and stable across Taylor series linearization, replicate weights, two-phase and non-probability designs, with means, totals, frequencies, quantiles, ratios, correlations, regression, t-tests, ANOVA and effective sample size all in place.
The last months before 1.0.0 were spent making the awkward designs behave like the ordinary ones. Non-probability designs gained jackknife replicate schemes and got their bootstrap repweights routed through the replicate-weight variance estimator in survey_glm(), matching every other estimation function. The survey_collection abstraction — several surveys treated as one pseudo-data-frame — was tightened rather than extended: divergent grouping across members now errors instead of stitching a patchwork with bind_rows(), and the missing-variable argument was renamed and given a stored default on the collection itself. A documentation audit before 1.0.0 turned up six dispatch and print bugs and corrections across forty-plus files, which is the kind of thing that surfaces when an API is being frozen rather than extended.
A declared-stable API means the next releases should be additive or corrective rather than breaking, and the pre-1.0.0 pattern of breaking renames should stop. The tight version pinning between the two packages means surveytidy releases will keep following surveycore's.
ToolJet runs two lines in parallel and both are in a steady groove. The LTS train picked up frontend and app observability built on OpenTelemetry semantic conventions plus primary and backup access, following a 3.20.212 release that carried the substantive feature batch — dynamic height across Timeline, Filepicker, Reorderable List, RadioButtonV2 and Tags, dynamic number formats on Currency Input, camera flip on mobile, and AI build notifications. The beta line is mostly fixes and LTS cherry-picks.
Most releases are small and corrective, with feature work collecting into occasional larger LTS drops. The recurring themes are component sizing, which appears in nearly every release, and enterprise-operations work — global data source certificates, automated RDS SSL setup, CVE patching, and now standards-based observability. It reads as a platform hardening for self-hosted enterprise deployments.
Expect the dynamic-height and sizing pass to continue across the remaining widgets, and the beta line's AI datasource integrations to graduate into the LTS train. Standardizing on OTel semconv suggests exported traces and metrics for customer-run dashboards next.
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 surveycore or ToolJet.
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
Spatial thinning grows a result object, and the API breaks to make room for it
A dormant plant-breeding package returns as a genomic selection index suite
CRAN download analytics maintained one micro-change at a time, hundreds per year
INSEE's statistics API gets a French R client that keeps meeting its edge cases
A bulk file reader became a labelled-survey-data toolkit, then went quiet
See all surveycore alternatives → · See all ToolJet alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. ToolJet 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. ToolJet 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 surveycore alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "surveycore alternatives" section above for the current picks, or visit /alternatives/surveycore for the full list with editorial commentary on each.
Top ToolJet alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ToolJet alternatives" section above for the current picks, or visit /alternatives/tooljet for the full list with editorial commentary on each.