← Back to home
Comparison · Analytics

brulee vs r2rtf

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

brulee vs r2rtf: at a glance

Featurebruleer2rtf
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesdeep-learning, tabular-models, torch, tidymodelsclinical-reporting, rtf, internationalization, document-conversion
Last editorial update3h ago1h ago
WebsiteVisit →Visit →

What is brulee?

tidymodels' torch backend grew from MLPs into a tabular deep learning suite with foundation models.

brulee fits neural networks for tidymodels on torch, and 1.0.0 redefined what that means: alongside the original MLP it now ships Regularization Learning Networks, ResNet with skip connections and batch normalization, AutoInt with columnwise attention, SAINT with row and column attention, and Chronos2, a foundational forecasting model. GPU acceleration arrived in the same release with automatic CUDA selection and opt-in MPS. Version 1.1.0 added TabICL, an open-source tabular foundation model, and 1.1.1 spent its time cleaning up the consequences of shipping models that need weight downloads.

Read the full brulee trajectory →

What is r2rtf?

The clinical-report table engine learned Chinese, then learned to leave RTF entirely

r2rtf builds the RTF tables, listings and figures that go into clinical study reports, and its recent releases have been about widening who and what it can serve rather than changing how tables are composed. The 1.2.0 release added internationalization — a SimSun font path for Chinese characters plus hyphenation control — and 1.3.0 followed with write_docx() and write_html(), turning the LibreOffice conversion the package had documented into exported functions.

Read the full r2rtf trajectory →

brulee vs r2rtf: editorial side-by-side

B
brulee
ANALYTICS
0.0

tidymodels' torch backend grew from MLPs into a tabular deep learning suite with foundation models.

◆ Current state

brulee fits neural networks for tidymodels on torch, and 1.0.0 redefined what that means: alongside the original MLP it now ships Regularization Learning Networks, ResNet with skip connections and batch normalization, AutoInt with columnwise attention, SAINT with row and column attention, and Chronos2, a foundational forecasting model. GPU acceleration arrived in the same release with automatic CUDA selection and opt-in MPS. Version 1.1.0 added TabICL, an open-source tabular foundation model, and 1.1.1 spent its time cleaning up the consequences of shipping models that need weight downloads.

◆ Where it's heading

The package has crossed from a torch convenience wrapper into a catalog of current tabular architectures, and the recent releases show it absorbing what that costs. Pretrained weights meant a 400MB download, so 1.1.1 stopped fetching them on attach and moved the cache to the platform-appropriate R_user_dir location. Numerical robustness is the other constant thread — 64-bit tensors, Gaussian initialization, gradient clipping extended architecture by architecture, and a ResNet batch-normalization bug where a single-row trailing batch produced all-NA predictions.

◆ Prediction

Gradient clipping has been rolled out one architecture at a time and TabICL is the newest arrival, so the likely next step is bringing the foundation models to parity with the trained ones on device selection, prediction types, and the tuning surface.

R
r2rtf
ANALYTICS
0.0

The clinical-report table engine learned Chinese, then learned to leave RTF entirely

◆ Current state

r2rtf builds the RTF tables, listings and figures that go into clinical study reports, and its recent releases have been about widening who and what it can serve rather than changing how tables are composed. The 1.2.0 release added internationalization — a SimSun font path for Chinese characters plus hyphenation control — and 1.3.0 followed with write_docx() and write_html(), turning the LibreOffice conversion the package had documented into exported functions.

◆ Where it's heading

Two threads run through the window. One is output reach: RTF remains the composition target, but the artifacts that come out of it now include DOCX and HTML, and page numbering can be made table-relative across multi-page tables. The other is durability under a moving R and font stack — the ANSI/Unicode converter was rebuilt, the LaTeX mapping table generated from code rather than shipped as sysdata, unlist() usage fixed for R 4.5, and graphics-device leaks that produced stray Rplots.pdf closed off.

◆ Prediction

Having exported DOCX and HTML conversion, the likely next step is filling in what those formats lose relative to RTF — pagination and footnote fidelity are the obvious gaps. The i18n path currently covers Chinese only, so additional font families are the other plausible direction.

Alternatives to brulee and r2rtf

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 brulee or r2rtf.

See all brulee alternatives → · See all r2rtf alternatives →

Recent activity from brulee and r2rtf

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

  1. 1mo agobruleeModel weights no longer download on package attach
  2. 1mo agobruleeTabICL foundation model added, gradient clipping extended
  3. 1mo agobruleeFive new architectures and GPU support arrive at 1.0.0
  4. 7mo agor2rtfDOCX and HTML output become exported functions
  5. 11mo agobrulee64-bit tensors and new optimizers to stop loss overflow
  6. 11mo agor2rtfChinese character support arrives via an i18n font path
  7. 1y agobruleeNumerical overflow unit test removed
  8. 1y agor2rtfText colour fixed for figures encoded into RTF
  9. 1y agor2rtfFootnote handling fixed for R 4.5.0
  10. 1y agor2rtfUnicode converter rebuilt and mapping table made inspectable
  11. 1y agobruleebrulee_mlp_two_layer() convenience wrapper for parsnip
  12. 2y agor2rtfUTF-8 conversion fix and LibreOffice 7.6 support

Frequently asked questions

What is the difference between brulee and r2rtf?

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

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

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

What are the best alternatives to r2rtf?

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