Basedash
Basedash keeps pushing its data out of the workspace — now to people without accounts
Comparison · Analytics
scales vs tulpa
A side-by-side editorial comparison of scales and tulpa — release velocity, themes, recent moves, and the top alternatives to consider.
scales vs tulpa: at a glance
What is scales?
scales keeps widening what ggplot2 can put on an axis.
scales supplies the breaks, labels and transformations behind ggplot2's axes and legends. Unlike much of the tidyverse infrastructure around it, it still ships genuine feature work each release: native timespan handling in 1.3.0, then custom range-training classes and label_glue() in 1.4.0.
What is tulpa?
The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.
tulpa is the C++/R Bayesian spatial inference engine sitting under gcol33's family of ecological occupancy packages, tagging 0.0.x releases several times a week. 0.1.0 is its first CRAN release, and the notes state outright that the engine surface is unchanged from 0.0.198 — the work is packaging discipline: local T bindings rebound to n_t/n_times, OpenMP teams capped under R CMD check, the pkgdown deploy narrowed, an aspell dictionary added. The window behind it splits between the S3 generics conversion and numerical-correctness work in the nested-Laplace grid.
scales vs tulpa: editorial side-by-side
scales
0.0ANALYTICS
scales keeps widening what ggplot2 can put on an axis.
◆ Current state
scales supplies the breaks, labels and transformations behind ggplot2's axes and legends. Unlike much of the tidyverse infrastructure around it, it still ships genuine feature work each release: native timespan handling in 1.3.0, then custom range-training classes and label_glue() in 1.4.0.
◆ Where it's heading
The arc runs toward extensibility and type coverage. First came built-in support for awkward types like difftime and hms; 1.4.0 inverts that by letting any third-party class participate in range training simply by implementing range() or levels(). Labelling is getting more expressive rather than merely more numerous.
◆ Prediction
Expect continued type-support and labelling work, with extension points that let downstream packages plug in their own classes instead of scales enumerating every one.
tulpa
7.5ANALYTICS
The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.
◆ Current state
tulpa is the C++/R Bayesian spatial inference engine sitting under gcol33's family of ecological occupancy packages, tagging 0.0.x releases several times a week. 0.1.0 is its first CRAN release, and the notes state outright that the engine surface is unchanged from 0.0.198 — the work is packaging discipline: local T bindings rebound to n_t/n_times, OpenMP teams capped under R CMD check, the pkgdown deploy narrowed, an aspell dictionary added. The window behind it splits between the S3 generics conversion and numerical-correctness work in the nested-Laplace grid.
◆ Where it's heading
Two moves in nine days point at the same destination: the generics conversion made tulpa extensible by downstream packages, and CRAN admission makes it installable by them. The current cadence — several tags a week, some existing only to record a measurement that produced no code change — does not survive CRAN's submission overhead, so the release rhythm has to slow whether or not the project intends it. The correctness work still clusters on the joint nested-Laplace driver, and 0.1.0 extends the same diagnostics habit with .NL_AXIS_SD_REASONS, a closed vocabulary for an outer axis whose grid does not contain its own posterior mode.
◆ Prediction
Expect tulpaObs to follow tulpa onto CRAN, since it is the consumer whose registrations the engine has spent this window unblocking, and expect the version line to move in larger, less frequent steps now that each one carries a submission.
Alternatives to scales and tulpa
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 scales or tulpa.
RStudio
RStudio ships through release branches, and the notes are commit messages
dbt Core
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Fulcrum
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
Holistics
Holistics keeps fencing in the AI layer it spent the summer building.
Dovetail
Dovetail spent July opening doors to other tools and August making its own rooms easier to enter.
See all scales alternatives → · See all tulpa alternatives →
Recent activity from scales and tulpa
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 18h agotulpaFirst CRAN release: engine surface unchanged from 0.0.198 ⚡
- 4d agotulpatulpa_re_aghq() exposes the mode/theta cross-Hessian
- 8d agotulpaDense batched joint path could silently drop a grid cell
- 8d agotulpaCalibration and goodness-of-fit entry points become S3 generics ⚡
- 9d agotulpaCUDA backend had two definitions; link order decided if it ran
- 9d agotulpaHyperparameter bounds now flag when they leave the node range
- 1y agoscalesscales 1.4.0 opens range training to custom classes
- 2y agoscalesscales 1.3.0 makes timespans first-class on axes
- 4y agoscalesscales 1.2.1 re-documents to fix .Rd HTML issues
- 4y agoscalesscales 1.2.0 fixes currency sign order and adds scale_cut
- 6y agoscalesscales 1.1.1 fixes palette inversion and adds oob_keep()
- 6y agoscalesscales 1.1.0 reorganises breaks and labels into a naming scheme
Frequently asked questions
What is the difference between scales and tulpa?
They serve adjacent needs but don't currently overlap on shipped themes. tulpa is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 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.
Is scales better than tulpa?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. tulpa is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 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.
What are the best alternatives to scales?
Top scales alternatives in Analytics are ranked by recent ship velocity. Browse the "scales alternatives" section above for the current picks, or visit /alternatives/scales-r for the full list with editorial commentary on each.
What are the best alternatives to tulpa?
Top tulpa alternatives in Analytics are ranked by recent ship velocity. Browse the "tulpa alternatives" section above for the current picks, or visit /alternatives/tulpa for the full list with editorial commentary on each.