The Bulma CSS framework reaches 1.0

Original Article ↗ Hacker News Discussion ↗

Bulma, a popular lightweight CSS framework, has released version 1.0 featuring a full Sass rewrite, CSS variables, theming, and a new grid system, while preserving backward compatibility for existing layouts. Commenters weigh its simplicity and readability against growing concerns over Sass’s long‑term viability, accessibility quirks, responsiveness gaps, and the added build‑step complexity compared with modern “just CSS” approaches or alternatives like Tailwind and Bootstrap. The project’s reliance on sponsorships from numerous online gambling sites also raises ethical and reputational questions for developers choosing it for client work.

Release & Project Direction

  • Bulma 1.0 is described as a full Sass rewrite with CSS variables, themes, and colors as main additions.
  • Some users are surprised it took this long to reach 1.0 but are reassured the project is still maintained.
  • At least one user notes 1.0 didn’t break their existing HTML, which is praised as high quality.
  • One commenter claims the minified size is about 3x larger than 0.9 (~647 KB), raising concerns about bloat.

Sass vs. Modern CSS

  • Several comments argue Sass is becoming a liability as native CSS gains features and syntax (e.g., max(), division, color-contrast()), and Sass syntax occasionally conflicts with new CSS features.
  • Others defend Sass, pointing to useful functions like “enough contrast” and new helpers for working with CSS variables.
  • Alternatives mentioned include Dart Sass and a Rust implementation (Grass); node-sass is noted as deprecated.

Usage, DX, and Feature Set

  • Bulma is praised as lightweight, easy to learn, and good for quick prototyping, small sites, and especially form inputs.
  • Some see it as “Bootstrap with less,” which is positive for those wanting minimalism, negative for those wanting more components.
  • There’s interest in using Bulma without a build pipeline; some refuse build steps in hobbies and hope CSS variables make customization feasible, but documentation on them is described as incomplete.
  • Comparisons to Tailwind: Bulma is seen as more component- and readability-focused; some prefer Tailwind + component layers like daisyUI.

Accessibility & Semantics

  • Criticism that some Bulma components require <a> tags for styling, even when not links; this is called bad for accessibility.
  • A maintainer response (in-thread) says they plan to make those elements tag-agnostic.
  • Another detailed review flags: non-accessible default colors (e.g., yellow on white), dark mode issues, and devtools contrast checks failing due to color definitions.

Sponsors & Ethics

  • Multiple commenters notice a large share of sponsors are online casinos, including unlicensed or self-exclusion-evading sites targeting Sweden.
  • Consensus is these sponsors mainly seek cheap, high-quality SEO backlinks.
  • Some find this off-putting enough to consider abandoning Bulma; others argue it’s irrelevant to using a free CSS library.
  • There’s disagreement over whether it’s reasonable or “overreacting” to avoid Bulma for this reason.

Quality, Issues, and Performance

  • Reports of Bulma’s own site having layout issues on mobile landscape and sluggish dark/light-toggle performance in Firefox.
  • A longstanding open issue related to mobile behavior is mentioned; unclear if the 1.0 rewrite fixes it.
  • Use of stale bots to auto-close GitHub issues is called a red flag by some, though others note this is now common.

Miscellaneous Discussion

  • Several users share personal sites and apps built with Bulma and express strong satisfaction.
  • Questions arise about missing components (e.g., accordions) and whether CSS frameworks are needed at all.
  • Short-hand numeronyms like a11y/i18n/k8s are explained and debated as confusing vs. convenient.