← Back to home
Comparison · Analytics

crul vs markdown

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

crul vs markdown: at a glance

Featurecrulmarkdown
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themeshttp-client, async, mocking, ropenscimarkdown-rendering, maintenance-mode, succession, r-package
Last editorial update1h ago4h 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 markdown?

A package that finished, declared itself done, and handed its core function to a successor.

The R markdown package spent 2023 adding real capability — fenced code block attributes, HTML widget rendering, compatibility shims for rmarkdown's document functions. Then 1.13 declared the package feature-complete and maintenance-only, naming litedown as where development continues. Version 2.0 completes that handover: mark(), the package's core function, is now a thin wrapper around litedown::mark(), and users are told to call litedown directly.

Read the full markdown trajectory →

crul vs markdown: 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.

M
markdown
ANALYTICS
0.0

A package that finished, declared itself done, and handed its core function to a successor.

◆ Current state

The R markdown package spent 2023 adding real capability — fenced code block attributes, HTML widget rendering, compatibility shims for rmarkdown's document functions. Then 1.13 declared the package feature-complete and maintenance-only, naming litedown as where development continues. Version 2.0 completes that handover: mark(), the package's core function, is now a thin wrapper around litedown::mark(), and users are told to call litedown directly.

◆ Where it's heading

This is a controlled retirement rather than abandonment. The maintainer closed out the outstanding feature work first, announced the succession explicitly, and only then reduced the package to a compatibility surface. What remains is a stable shim for the installed base while new work happens in a package with a different name and scope.

◆ Prediction

Expect only CRAN-driven fixes here from now on, with any genuinely new rendering capability appearing in litedown instead. The entries state this policy directly, so the main open question is how long the wrapper is kept before deprecation warnings appear.

Alternatives to crul and markdown

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 markdown.

See all crul alternatives → · See all markdown alternatives →

Recent activity from crul and markdown

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

  1. 1y agocrulMocking becomes a client parameter, independent of webmockr
  2. 1y agomarkdownmark() becomes a thin wrapper around litedown::mark()
  3. 2y agocrulAsync requests become mockable through webmockr
  4. 2y agomarkdownPackage declared feature-complete; work moves to litedown
  5. 2y agocrulDocumentation fixes and test helper tweak
  6. 2y agomarkdownAdds compatibility shims for rmarkdown's document functions
  7. 2y agomarkdownFixes verbatim code blocks with language attributes
  8. 2y agomarkdownFixes raw blocks broken by code-block attribute support
  9. 2y agomarkdownFenced code blocks gain attributes; HTML widgets render
  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 markdown?

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

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

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