rsample
tidymodels' resampling package is retiring its old splitters for sliding windows.
A side-by-side editorial comparison of Gemini and mlr3 — release velocity, themes, recent moves, and the top alternatives to consider.
A billion monthly users, and a feed running on audience content between launches
The last two weeks of this feed are almost entirely audience content: usage tips, a state-fair guide, a builder showcase, a monthly news roundup, a course retrospective. The one item of substance is a milestone rather than a release — the Gemini app passed a billion monthly users. The actual product news in range, the Chrome integration and Robotics ER 2, published at the end of July.
mlr3 is hardening the seams where its abstractions meet real learners
Releases arrive every few weeks and read as a systematic audit of the Learner interface. Recent versions added a native_model binding and a predict_raw flag so users can reach the underlying package's model and raw prediction, gave encapsulated learners a wall-clock deadline alongside the existing timeout, and removed the deprecated Task$divide(). A run of fixes addresses correctness at the boundary - factor level ordering that inverted binary probabilities, fallback learners losing state, misaligned probability columns.
The last two weeks of this feed are almost entirely audience content: usage tips, a state-fair guide, a builder showcase, a monthly news roundup, a course retrospective. The one item of substance is a milestone rather than a release — the Gemini app passed a billion monthly users. The actual product news in range, the Chrome integration and Robotics ER 2, published at the end of July.
Google is using this channel to consolidate attention on the app between launches rather than to announce capability. The releases it does carry point at Gemini reaching into other surfaces — Spark inside Chrome, computer use in 3.5 Flash, robotics — rather than the app growing on its own. Everything between those dates is demonstration of existing features.
On this feed's own pattern, the next item of substance will cluster on a launch date as a model or surface announcement; nothing in the current run of lifestyle posts signals what it will be.
Releases arrive every few weeks and read as a systematic audit of the Learner interface. Recent versions added a native_model binding and a predict_raw flag so users can reach the underlying package's model and raw prediction, gave encapsulated learners a wall-clock deadline alongside the existing timeout, and removed the deprecated Task$divide(). A run of fixes addresses correctness at the boundary - factor level ordering that inverted binary probabilities, fallback learners losing state, misaligned probability columns.
The framework is maturing from wrapping models to being accountable for what happens when wrapping goes wrong. Structured Mlr3Error and Mlr3Warning classes, conditions stored on the learner log, and messages replaced by conditions all point at making failures programmatically inspectable rather than printed. In parallel, escape hatches to the upstream model are being formalised instead of left to users digging into internals.
Expect the remaining deprecated surface to follow Task$divide() out, and further work on encapsulation and fallback behaviour, which is where most recent fixes have clustered. The raw and native_model accessors suggest more of the upstream model will be surfaced deliberately.
Other ai-assistants 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 Gemini or mlr3.
tidymodels' resampling package is retiring its old splitters for sliding windows.
tidymodels' preprocessing engine learned sparsity, then settled into deprecations.
The resampling companion to scikit-learn now ships mostly to stay compatible with it.
parsnip added a whole new regression type, then wired R models to JAX and PyTorch
Mem0 splits agent memory from user memory, then spends a week hardening the plumbing
Every post is a comparison page, and Pictory is always the answer.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Gemini is currently shipping more aggressively (velocity 8.8 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. Gemini is currently shipping more aggressively (velocity 8.8 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 ai-assistants products to evaluate alongside.
Top Gemini alternatives in ai-assistants are ranked by recent ship velocity. Browse the "Gemini alternatives" section above for the current picks, or visit /alternatives/gemini for the full list with editorial commentary on each.
Top mlr3 alternatives in ai-assistants are ranked by recent ship velocity. Browse the "mlr3 alternatives" section above for the current picks, or visit /alternatives/mlr3 for the full list with editorial commentary on each.