← Back to home
Comparison · Analytics

crul vs simtrial

A side-by-side editorial comparison of crul and simtrial — release velocity, themes, recent moves, and the top alternatives to consider.

crul vs simtrial: at a glance

Featurecrulsimtrial
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themeshttp-client, async, mocking, ropensciclinical-trials, group-sequential, survival-analysis, simulation
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is crul?

crul took mocking back from webmockr and made it a property of the client itself

crul is the R6-based HTTP client underneath much of rOpenSci's package stack, covering synchronous requests, three flavours of async, pagination and retries. Its 1.6.0 release in July 2025 changed where test mocking lives: each client — HttpClient, Async, AsyncVaried — now takes a mocking parameter at initialisation or per method, and the standalone mock() function is deprecated. Mocking used to be something webmockr switched on from outside; it is now a setting on the client.

Read the full crul trajectory →

What is simtrial?

A fixed-design trial simulator grew a pluggable test framework, then spent a year proving the numbers

simtrial simulates time-to-event clinical trials and applies the tests used to analyse them — logrank, weighted logrank, MaxCombo, RMST, milestone. The 0.4.0 release turned it from a fixed-sample simulator into a group sequential one and standardised every test behind a common output contract, and the releases since have been about making that machinery correct and fast enough to run at scale. Version 1.0.0 arrived in June 2025 with the API settled and three vignettes explaining both the one-call and build-it-yourself paths.

Read the full simtrial trajectory →

crul vs simtrial: editorial side-by-side

C
crul
ANALYTICS
0.0

crul took mocking back from webmockr and made it a property of the client itself

◆ Current state

crul is the R6-based HTTP client underneath much of rOpenSci's package stack, covering synchronous requests, three flavours of async, pagination and retries. Its 1.6.0 release in July 2025 changed where test mocking lives: each client — HttpClient, Async, AsyncVaried — now takes a mocking parameter at initialisation or per method, and the standalone mock() function is deprecated. Mocking used to be something webmockr switched on from outside; it is now a setting on the client.

◆ Where it's heading

The async surface has been the growth area for years — retries reached Async, AsyncVaried, AsyncQueue and HttpRequest in 1.4, AsyncQueue gained the response accessors in 1.2, and 1.5.0 wired async requests up to webmockr. The 1.6.0 change reverses that direction of dependency, and it landed within a minute of webmockr's own release severing its tie to vcr. Read together, the rOpenSci HTTP stack is being deliberately untangled so each package can be used without the others.

◆ Prediction

With mock() deprecated rather than removed, the next major release is the likely point of deletion. Expect the remaining work to follow the same decoupling theme rather than adding request features.

S
simtrial
ANALYTICS
0.0

A fixed-design trial simulator grew a pluggable test framework, then spent a year proving the numbers

◆ Current state

simtrial simulates time-to-event clinical trials and applies the tests used to analyse them — logrank, weighted logrank, MaxCombo, RMST, milestone. The 0.4.0 release turned it from a fixed-sample simulator into a group sequential one and standardised every test behind a common output contract, and the releases since have been about making that machinery correct and fast enough to run at scale. Version 1.0.0 arrived in June 2025 with the API settled and three vignettes explaining both the one-call and build-it-yourself paths.

◆ Where it's heading

Post-1.0 the work is almost entirely statistical correctness and speed, and it is concentrated in sim_gs_n(): one-sided efficacy bounds, stratified targeted-event cut dates, a helper that derives cuttings straight from the design object. Performance moves in one direction throughout — dplyr replaced by data.table, foreach combination replaced by manual assembly, parallelisation added to sim_fixed_n() — because simulation-based operating characteristics are only useful if you can afford enough replications.

◆ Prediction

The recent fixes cluster on stratified and group sequential paths, so the next release most likely continues there rather than adding a new test type. The cut_from_design() helper suggests tighter coupling to gsDesign2 design objects is the direction of travel.

Alternatives to crul and simtrial

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 crul or simtrial.

See all crul alternatives → · See all simtrial alternatives →

Recent activity from crul and simtrial

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 8mo agosimtrialOne-sided efficacy bound and stratified cut date corrected
  2. 11mo agosimtrialsim_gs_n moved to data.table; stratified design example added
  3. 1y agocrulMocking becomes a client parameter, independent of webmockr
  4. 1y agosimtrial1.0.0 settles the wlr interface and documents both simulation paths
  5. 1y agosimtrialMilestone Z-score denominator corrected; parallel sim_fixed_n arrives
  6. 2y agocrulAsync requests become mockable through webmockr
  7. 2y agosimtrialChecks pass without Suggests dependencies
  8. 2y agosimtrialRMST and milestone tests, plus a user-definable cut and test framework
  9. 2y agocrulDocumentation fixes and test helper tweak
  10. 3y agocrulHTTP retries reach the async classes
  11. 3y agocrulClearer error for mismatched urls and disk lengths
  12. 4y agocrulAsyncQueue gains response accessors; results print as a summary

Frequently asked questions

What is the difference between crul and simtrial?

They serve adjacent needs but don't currently overlap on shipped themes. crul and simtrial 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 crul better than simtrial?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. crul and simtrial 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 crul?

Top crul alternatives in Analytics are ranked by recent ship velocity. Browse the "crul alternatives" section above for the current picks, or visit /alternatives/crul for the full list with editorial commentary on each.

What are the best alternatives to simtrial?

Top simtrial alternatives in Analytics are ranked by recent ship velocity. Browse the "simtrial alternatives" section above for the current picks, or visit /alternatives/simtrial for the full list with editorial commentary on each.