← Back to home
Comparison · Analytics

markdown vs webchem

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

markdown vs webchem: at a glance

Featuremarkdownwebchem
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesmarkdown-rendering, maintenance-mode, succession, r-packagecheminformatics, web-apis, data-access, ropensci
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

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 →

What is webchem?

Adding chemical databases with one hand while public ones close programmatic access with the other.

webchem is the R interface to public chemical data — retrieving identifiers, properties and structures across roughly a dozen web services. Its release history reads as a running account of which of those services still allow automated access. Version 1.3.0 removed two functions outright because their sources withdrew: ChemIDplus was retired by the NLM, and PAN stopped supporting programmatic access. Version 1.3.1 continues the pattern, updating URLs that stopped working and noting that ChemSpider InChIKey validation now requires an API key like the rest of that provider's endpoints.

Read the full webchem trajectory →

markdown vs webchem: editorial side-by-side

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.

W
webchem
ANALYTICS
0.0

Adding chemical databases with one hand while public ones close programmatic access with the other.

◆ Current state

webchem is the R interface to public chemical data — retrieving identifiers, properties and structures across roughly a dozen web services. Its release history reads as a running account of which of those services still allow automated access. Version 1.3.0 removed two functions outright because their sources withdrew: ChemIDplus was retired by the NLM, and PAN stopped supporting programmatic access. Version 1.3.1 continues the pattern, updating URLs that stopped working and noting that ChemSpider InChIKey validation now requires an API key like the rest of that provider's endpoints.

◆ Where it's heading

Two opposing forces run through these entries. The package keeps widening its coverage — ChEMBL in 1.2.0, LIPID MAPS and SwissLipids identifiers via Wikidata, structure images, Mol export — while the open, unauthenticated end of the chemical web keeps contracting. The other consistent thread is interface harmonisation: successive releases have converged the get_* functions on the same query and from arguments, tibble returns, and CAS reformatting, so the package feels like one interface rather than a dozen wrappers.

◆ Prediction

Expect further defunct functions and URL repairs as more providers move behind keys or shut down, alongside occasional additions of sources that remain open. The entries show no sign of a general credential-management layer, which is what a package facing this trend would eventually need.

Alternatives to markdown and webchem

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

See all markdown alternatives → · See all webchem alternatives →

Recent activity from markdown and webchem

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

  1. 1y agowebchemRepairs broken URLs; ChemSpider check now needs a key
  2. 1y agomarkdownmark() becomes a thin wrapper around litedown::mark()
  3. 2y agomarkdownPackage declared feature-complete; work moves to litedown
  4. 2y agomarkdownAdds compatibility shims for rmarkdown's document functions
  5. 2y agomarkdownFixes verbatim code blocks with language attributes
  6. 2y agomarkdownFixes raw blocks broken by code-block attribute support
  7. 2y agomarkdownFenced code blocks gain attributes; HTML widgets render
  8. 3y agowebchemChemIDplus and PAN queries removed as sources shut down
  9. 3y agowebchemAdds ChEMBL access for bioactive compound data
  10. 4y agowebchemcir_query() returns a tibble, a breaking change
  11. 4y agowebchemAdds Mol structure export; aw_query renamed to bcpc_query
  12. 5y agowebchemFetches LIPID MAPS and SwissLipids identifiers from Wikidata

Frequently asked questions

What is the difference between markdown and webchem?

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

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

What are the best alternatives to webchem?

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