tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
torchvision vs webmockr
A side-by-side editorial comparison of torchvision and webmockr — release velocity, themes, recent moves, and the top alternatives to consider.
torchvision vs webmockr: at a glance
What is torchvision?
R's torchvision is porting PyTorch's vision stack one task at a time — instance segmentation just landed.
torchvision for R has moved past being a thin tensor-transform helper into a task-complete vision library. The last three releases added dataset loaders by the dozen, then face detection and recognition, and now Mask R-CNN for instance segmentation. The 0.9.0 release also splits the COCO detection loader from a new segmentation loader, cutting memory use roughly in half for detection-only work.
What is webmockr?
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
webmockr intercepts HTTP requests in R tests and returns stubbed responses, and since 1.0.0 it covers all three clients that matter — httr, httr2 and crul. The releases through 2025 have been about shedding dependencies: internal R6 classes unexported in 2.1.0, crul demoted from Imports to Suggests in the same release, and the mutual dependency with vcr severed in 2.2.0. The package now installs and runs without pulling in the rest of the rOpenSci HTTP stack.
torchvision vs webmockr: editorial side-by-side
torchvision
0.0ANALYTICS
R's torchvision is porting PyTorch's vision stack one task at a time — instance segmentation just landed.
◆ Current state
torchvision for R has moved past being a thin tensor-transform helper into a task-complete vision library. The last three releases added dataset loaders by the dozen, then face detection and recognition, and now Mask R-CNN for instance segmentation. The 0.9.0 release also splits the COCO detection loader from a new segmentation loader, cutting memory use roughly in half for detection-only work.
◆ Where it's heading
The pattern is a deliberate walk through PyTorch's torchvision feature matrix: datasets first, then model architectures, then the visualization and transform utilities that make each task usable end to end. Each release breaks a little API to align R naming with upstream PyTorch conventions — `$categories` became `$classes`, `coco_classes()` now matches the 90-class sparse PyTorch layout. Community contributors are doing most of the volume, with maintainers arbitrating the API shape.
◆ Prediction
Expect the next release to fill in the remaining segmentation and detection model families and continue aligning class and label handling with upstream PyTorch, given that every release so far has paired new models with a matching dataset loader.
webmockr
0.0ANALYTICS
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
◆ Current state
webmockr intercepts HTTP requests in R tests and returns stubbed responses, and since 1.0.0 it covers all three clients that matter — httr, httr2 and crul. The releases through 2025 have been about shedding dependencies: internal R6 classes unexported in 2.1.0, crul demoted from Imports to Suggests in the same release, and the mutual dependency with vcr severed in 2.2.0. The package now installs and runs without pulling in the rest of the rOpenSci HTTP stack.
◆ Where it's heading
Two arcs run in sequence. The first is coverage — multiple queued responses in 0.7.0, basic auth mocking, async through crul, then httr2 — building out what can be stubbed. The second, starting with 2.0.0, is correctness and independence: stubs are now deleted if an error occurs mid-construction rather than lingering half-built, partial matching arrives for bodies and queries, and the dependency graph is pruned release by release. The 2.2.0 split from vcr landed within a minute of crul's release taking mocking control into its own clients.
◆ Prediction
RequestPattern is documented as still exported in 2.1.0 but slated for removal, so the next major release is where that lands. Expect continued dependency pruning rather than new client support — the three clients that exist are already covered.
Alternatives to torchvision and webmockr
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 torchvision or webmockr.
Tplyr
Tplyr made clinical summary tables explain where every number came from.
rlistings
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
hoardr
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
riem
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
See all torchvision alternatives → · See all webmockr alternatives →
Recent activity from torchvision and webmockr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agotorchvisionMask R-CNN brings instance segmentation to R torchvision ⚡
- 9mo agotorchvisionFace detection models and 35 RoboFlow datasets land
- 1y agowebmockrvcr dependency severed
- 1y agotorchvisionFashion-MNIST, COCO, and a dozen more dataset loaders
- 1y agowebmockrInternal classes unexported; crul becomes an optional dependency
- 1y agowebmockrFailed stub construction cleans up; partial matching extends to bodies and queries
- 2y agowebmockrhttr2 joins httr and crul as a supported client ⚡
- 3y agowebmockrQueued responses, body matching and integer status codes fixed
- 3y agowebmockrRegex URI matching fixed
Frequently asked questions
What is the difference between torchvision and webmockr?
They serve adjacent needs but don't currently overlap on shipped themes. torchvision and webmockr 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.
Is torchvision better than webmockr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. torchvision and webmockr 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.
What are the best alternatives to torchvision?
Top torchvision alternatives in Analytics are ranked by recent ship velocity. Browse the "torchvision alternatives" section above for the current picks, or visit /alternatives/torchvision for the full list with editorial commentary on each.
What are the best alternatives to webmockr?
Top webmockr alternatives in Analytics are ranked by recent ship velocity. Browse the "webmockr alternatives" section above for the current picks, or visit /alternatives/webmockr for the full list with editorial commentary on each.