modeltime
modeltime built conformal intervals in, then went quiet on features.
A side-by-side editorial comparison of Simple Analytics and tidyr — release velocity, themes, recent moves, and the top alternatives to consider.
Privacy analytics tightening its API and moving IP blocking off the CDN
The feed stores each change several times — once with the body text captured as the title, once as a clean headline, sometimes a third time with a date prefix. Behind the duplication, three real changes: API v6 with proper interval support while v5 stays unchanged for compatibility, IP blocking moved off the bunny.net CDN so it works on custom domains and applies per site rather than account-wide, and Events Explorer readability work with column truncation, a full-width toggle and collapsible headers.
tidyr replaced separate() with a family that says what it does.
tidyr is at 1.3.2, a collection of argument additions — fill() gains .by, expand_grid() gains .vary — and better error messages around unchop() and pivot_wider_spec(). The structural work is 1.3.0, which introduced separate_wider_delim(), separate_wider_position(), separate_wider_regex(), separate_longer_delim() and separate_longer_position() as thorough replacements for separate(), extract() and separate_rows().
The feed stores each change several times — once with the body text captured as the title, once as a clean headline, sometimes a third time with a date prefix. Behind the duplication, three real changes: API v6 with proper interval support while v5 stays unchanged for compatibility, IP blocking moved off the bunny.net CDN so it works on custom domains and applies per site rather than account-wide, and Events Explorer readability work with column truncation, a full-width toggle and collapsible headers.
The work is about removing borrowed constraints. IP blocking inherited the CDN's limits and blast radius; moving it in-house made it per-site and custom-domain compatible. API v6 does the same for time handling — hourly data separates day and hour, weeks and months carry explicit start dates — while keeping v5 stable so nobody is forced to migrate. Both are the moves of a product whose users integrate it and stay.
With v6 shipped alongside an unchanged v5, expect a deprecation timeline for v5 to be the next API announcement, though the entries do not name one.
tidyr is at 1.3.2, a collection of argument additions — fill() gains .by, expand_grid() gains .vary — and better error messages around unchop() and pivot_wider_spec(). The structural work is 1.3.0, which introduced separate_wider_delim(), separate_wider_position(), separate_wider_regex(), separate_longer_delim() and separate_longer_position() as thorough replacements for separate(), extract() and separate_rows().
Two habits define this window. Verbs are being split into explicitly named variants rather than overloaded with arguments, which is what the separate_* family does to separate(). And .by is spreading as the standard way to express grouping inline — nest(.by=) in 1.3.0, fill(.by=) in 1.3.2 — pulling users away from wrapping calls in group_by().
Given that .by has now reached fill() and nest(), the next release most likely extends the same argument to further verbs rather than reworking another function family.
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 Simple Analytics or tidyr.
modeltime built conformal intervals in, then went quiet on features.
performance keeps adding ways to check a model you have already fitted.
CmdStanPy is clearing deprecations ahead of a 2.0 it keeps announcing.
DoWhy adds one estimation method a year and keeps its identification edge.
OpenHouse is hardening the seams where table policies and jobs quietly fail.
silx 3.0 moved its default Qt binding to PySide6 — a migration for everyone embedding it.
See all Simple Analytics alternatives → · See all tidyr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Simple Analytics and tidyr 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. Simple Analytics and tidyr 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 Analytics products to evaluate alongside.
Top Simple Analytics alternatives in Analytics are ranked by recent ship velocity. Browse the "Simple Analytics alternatives" section above for the current picks, or visit /alternatives/simple-analytics for the full list with editorial commentary on each.
Top tidyr alternatives in Analytics are ranked by recent ship velocity. Browse the "tidyr alternatives" section above for the current picks, or visit /alternatives/tidyr for the full list with editorial commentary on each.