WPML
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
Comparison · Infra & APIs
bolasso vs projoint
A side-by-side editorial comparison of bolasso and projoint — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
bolasso vs projoint: at a glance
What is bolasso?
Bootstrap lasso got a fast mode, a second selection rule, and multinomial support
bolasso implements the bootstrapped lasso, refitting a regularized regression across bootstrap replicates and selecting variables by how consistently they survive. The 0.3.0 release reshaped it: a fast argument computes one cross-validated lambda on the full dataset instead of cross-validating inside every replicate, and selected_variables() gained a choice between the variable inclusion probability rule and a quantile rule based on bootstrap confidence intervals. Since then 0.4.0 exposed the bootstrap indices through bootstrap_samples(), and 0.5.0 extended the whole surface to multinomial responses, returning one list element per outcome level.
What is projoint?
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
projoint is an R package for analysing conjoint survey experiments, covering Qualtrics import, reshaping, and quantity-of-interest estimation with inter-rater reliability correction. Most of its release history is CRAN admission work — citation formats, DESCRIPTION fields, \value{} tags, vignette cleanups — with four tags backfilled within ninety seconds of each other on 15 July in non-monotonic version order, so neither tag order nor timestamps in this feed track the real sequence. The substantive releases are the ones fixing data-preparation bugs that silently corrupt estimates.
bolasso vs projoint: editorial side-by-side
bolasso
0.0INFRA · APIS
Bootstrap lasso got a fast mode, a second selection rule, and multinomial support
◆ Current state
bolasso implements the bootstrapped lasso, refitting a regularized regression across bootstrap replicates and selecting variables by how consistently they survive. The 0.3.0 release reshaped it: a fast argument computes one cross-validated lambda on the full dataset instead of cross-validating inside every replicate, and selected_variables() gained a choice between the variable inclusion probability rule and a quantile rule based on bootstrap confidence intervals. Since then 0.4.0 exposed the bootstrap indices through bootstrap_samples(), and 0.5.0 extended the whole surface to multinomial responses, returning one list element per outcome level.
◆ Where it's heading
The package spent 2022 dormant after its initial releases and has been actively developed since late 2024, moving from a single algorithm toward a workbench. The additions cluster around inspection rather than estimation: tidy() for bootstrap-level coefficients, plot_selection_thresholds() for selection stability across thresholds, plot_selected_variables() for the surviving covariates, and now the extracted bootstrap indices. Documented gaps remain, with mgaussian unsupported and multinomial prediction limited to class output.
◆ Prediction
The two stated limitations in 0.5.0 - no mgaussian family and class-only multinomial prediction - are the most likely next targets, since the maintainer flagged both as possible later additions.
projoint
2.5INFRA · APIS
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
◆ Current state
projoint is an R package for analysing conjoint survey experiments, covering Qualtrics import, reshaping, and quantity-of-interest estimation with inter-rater reliability correction. Most of its release history is CRAN admission work — citation formats, DESCRIPTION fields, \value{} tags, vignette cleanups — with four tags backfilled within ninety seconds of each other on 15 July in non-monotonic version order, so neither tag order nor timestamps in this feed track the real sequence. The substantive releases are the ones fixing data-preparation bugs that silently corrupt estimates.
◆ Where it's heading
The maintainer is hardening the path from raw Qualtrics export to estimate, which is where conjoint analysis quietly goes wrong. Three separate releases fix that path: dropped respondent-level weights in organize_data(), repeated-task reshaping in reshape_projoint(), and choice-to-profile mapping in 1.1.3. Each fix now arrives with regression tests and stricter validation rather than just a patch, and 1.1.3 adds an explicit .choice_map so the mapping is auditable instead of inferred.
◆ Prediction
Expect the validation-and-regression-test pattern to keep extending across the import path, with releases continuing to arrive in bursts around CRAN submission rather than on a cadence.
Alternatives to bolasso and projoint
Other Infra & APIs 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 bolasso or projoint.
forestploter
A forest plot package that keeps handing users control of one more graphical detail.
ggInterval
Interval-valued data plotting, spending 2026 making its function names and examples survive CRAN.
rgm
A microbiome network model that got itself un-archived by deleting the dependency that killed it.
contagionchannels
Three releases in ten days, every one of them a CRAN reviewer's correction rather than a code change.
tidyaudit
Pipeline provenance for tidyverse workflows, recording what changed at each step without keeping the data.
See all bolasso alternatives → · See all projoint alternatives →
Recent activity from bolasso and projoint
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 17d agoprojointExplicit .choice_map guards choice-to-profile mapping
- 1mo agoprojointCRAN submission housekeeping for DESCRIPTION and examples
- 1mo agoprojointCRAN formatting pass; minor make_projoint_data() fix
- 1mo agoprojointreshape_projoint() repeated-task bug fixed; validation tightened
- 1mo agoprojointCitation metadata updated with the CRAN DOI
- 4mo agobolassoMultinomial responses supported across selection and plotting
- 5mo agoprojointorganize_data() no longer drops respondent-level weights
- 10mo agobolassoBootstrap indices exposed via bootstrap_samples()
- 1y agobolassoFast estimation mode and a second variable selection rule ⚡
- 4y agobolassoBolasso v0.2.0
- 4y agobolassoBolasso v0.1.0
Frequently asked questions
What is the difference between bolasso and projoint?
Both compete on the same themes — r-package — within Infra & APIs. projoint is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is bolasso better than projoint?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. projoint is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to bolasso?
Top bolasso alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "bolasso alternatives" section above for the current picks, or visit /alternatives/bolasso for the full list with editorial commentary on each.
What are the best alternatives to projoint?
Top projoint alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "projoint alternatives" section above for the current picks, or visit /alternatives/projoint for the full list with editorial commentary on each.