tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of forcis and pysparklyr — release velocity, themes, recent moves, and the top alternatives to consider.
A foraminifera data-access package whose entire release history is the rOpenSci review process.
forcis provides R access to the FORCIS database of planktonic foraminifera occurrences. All three releases in the window are review milestones rather than feature work: first stable release, the release answering rOpenSci reviewer comments, and a post-CRAN-review polish. Release notes point at NEWS.md rather than enumerating changes.
Posit's Spark Connect bridge keeps adding backends — and now runs tidymodels tuning on the cluster.
pysparklyr is the Python-backed backend that lets sparklyr talk to Spark Connect, Databricks Connect, and now Snowflake, handling the reticulate environment, authentication, and Arrow configuration so R users mostly do not have to. The 0.2.x line has widened it well past a connectivity shim: 0.2.0 brought the Spark 4.0 ML function family and Snowpark Connect, and 0.2.2 added tune_grid_spark() so a tidymodels tuning grid executes inside a Spark Connect cluster. Authentication has become a first-class concern, with Snowflake's native authenticators, connections.toml discovery, and Posit Connect viewer credentials all supported.
forcis provides R access to the FORCIS database of planktonic foraminifera occurrences. All three releases in the window are review milestones rather than feature work: first stable release, the release answering rOpenSci reviewer comments, and a post-CRAN-review polish. Release notes point at NEWS.md rather than enumerating changes.
The package is moving from research artifact to reviewed, distributable infrastructure — submitted to rOpenSci at 0.1.0, integrated review feedback at 1.0.0, cleared CRAN at 1.0.1. That arc is complete, so the next phase should be the first release driven by users rather than reviewers.
With review and CRAN acceptance both behind it, the next release is most likely to track upstream FORCIS database changes or add query conveniences; the entries themselves say nothing about planned features.
pysparklyr is the Python-backed backend that lets sparklyr talk to Spark Connect, Databricks Connect, and now Snowflake, handling the reticulate environment, authentication, and Arrow configuration so R users mostly do not have to. The 0.2.x line has widened it well past a connectivity shim: 0.2.0 brought the Spark 4.0 ML function family and Snowpark Connect, and 0.2.2 added tune_grid_spark() so a tidymodels tuning grid executes inside a Spark Connect cluster. Authentication has become a first-class concern, with Snowflake's native authenticators, connections.toml discovery, and Posit Connect viewer credentials all supported.
Two directions are running at once. Horizontally, the package is becoming backend-plural — what started as Databricks-and-Spark now covers Snowflake through Snowpark Connect, with credential handling generalized per platform rather than special-cased. Vertically, it is climbing from data manipulation toward modeling: distributed ML functions in 0.2.0, distributed tuning in 0.2.2. A persistent third thread is absorbing upstream churn — Pandas 3.0 conversion, sparklyr 1.9.5 and dbplyr 2.6.0 restructuring the tbl source slot, reticulate's changing environment management.
With tuning distributed and the Spark 4.0 ML surface in place, the unfinished edge is the rest of the tidymodels workflow — expect fitting and resampling paths to follow tune_grid_spark() onto the cluster.
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 forcis or pysparklyr.
A tables-listings-graphs package that reached CRAN and then went quiet.
Tplyr made clinical summary tables explain where every number came from.
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
See all forcis alternatives → · See all pysparklyr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. pysparklyr is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 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. pysparklyr is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 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.
Top forcis alternatives in Analytics are ranked by recent ship velocity. Browse the "forcis alternatives" section above for the current picks, or visit /alternatives/forcis for the full list with editorial commentary on each.
Top pysparklyr alternatives in Analytics are ranked by recent ship velocity. Browse the "pysparklyr alternatives" section above for the current picks, or visit /alternatives/pysparklyr for the full list with editorial commentary on each.