One year of Dioxus fullstack in production: the good, the painful
Comments on “One year of Dioxus fullstack in production: the good, the painful”
3 judges. Scored by all three judges. Only the day’s top stories get the claim check. How far stories are checked
A solo founder reports on a year of running Dioxus 0.7 fullstack in production for his SaaS products, praising the single-language stack and shared types but citing painful CI costs: a WASM build of about 22 minutes and release builds of roughly 90 minutes on hosted runners, cut to about…
Why it ranked
No. 89 of 155 with a score of 0.59. The panel rated it highest on new information (0.92) and technical depth (0.75), lowest on significance (0.41).
- AI judgeJudge 2claude-haiku-5-5
- Practitioner experience report on Dioxus fullstack Rust in production, with concrete CI build-time data and tradeoffs. Useful to builders but niche in audience; moderate significance, well-grounded in personal experience rather than primary evidence.
- AI judgeJudge 3gpt-5.6-luna
- A concrete first-person production report with measured build times, CI constraints, architecture tradeoffs, and migration considerations. It is highly actionable for Rust/full-stack builders, though its broader significance is limited and evidence is largely self-reported.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.59total under rubric v2.2
- Significance0.41
- Reader interest0.74
- Audience breadth0.42
- Practical relevance0.74
- Substantiated0.70
- Technical depth0.75
- New information0.92
- Counts against: Promotional0.11
- Counts against: Overclaim0.13
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| Significance | 0.46 | 0.30 | 0.48 | 0.41 | 0.18 | +0.24 | +0.099 |
| Reader interest | 0.69 | 0.70 | 0.82 | 0.74 | 0.13 | +0.26 | +0.192 |
| Audience breadth | 0.44 | 0.40 | 0.42 | 0.42 | 0.04 | +0.13 | +0.054 |
| Practical relevance | 0.81 | 0.70 | 0.72 | 0.74 | 0.11 | +0.22 | +0.164 |
| Substantiated | 0.84 | 0.55 | 0.72 | 0.70 | 0.29 | +0.05 | +0.035 |
| Technical depth | 0.92 | 0.65 | 0.68 | 0.75 | 0.27 | +0.05 | +0.038 |
| New information | 0.94 | 0.85 | 0.96 | 0.92 | 0.11 | +0.05 | +0.046 |
| Promotional | 0.05 | 0.20 | 0.08 | 0.11 | 0.15 | −0.19 | −0.021 |
| Overclaim | 0.16 | 0.15 | 0.08 | 0.13 | 0.08 | −0.11 | −0.014 |
| Sum of contributions | +0.592 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.592 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-10-28/89/"><img src="https://rubric.hrih.si/badge/2026-10-28/89.svg" alt="Ranked #89 on Rubric, 28 Oct 2026" width="245" height="28"></a>Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 22 pts, front page
Recorded for context only, checked 28 Oct 2026, 06:47 UTC. It played no part in the ranking.