This would have meant a lot more earlier in 2024. Back when I was invested in using Bulma CSS Framework. Back when using Bulma CSS Framework had some relative meaning.
You see, we all need validation. We need our decisions validated. We need our actions validated. When I used Bulma CSS Framework, I wanted to know it was ok, that it was good.
Turns out that Bulma was probably one of the worst choices to make as a CSS Framework. That was emphasized in March 2024 when v1.0.0 was released and again in May when version 1.0.1 was released. In my opinion, Bulma CSS Framework is garbage. The release of v1.0.0 made it bloated garbage (bloated: gheez, v1.0.0 is 713Kb). The release of v1.0.1 reinforced that (wow, still ... 714Kb). And now the release of market share data cements it. What it should do is encapsulate it in a cement outer shell and drop it in a body of water somewhere ... t'would make a thud on the ocean floor.
Tailwind CSS has increased in market share, nearly doubling to 0.8% market share. Bootstrap has dropped a bit ... well almost equivalent to Tailwind's gain. That Bulma CSS Framework hasn't picked up any gains is notable – especially with two new releases. Bulma CSS Framework remains at 0.2% market share.
0.2% market share. Consider that ... if Bulma CSS Framework were a skunk odor (and I nearly define it that way) it could saunter right past you without nasal detection. 0.2% is barely a blip on the usage charts. That places it just ahead of MetroUI and just slightly behind SemanticUI. Surprisingly, Skelton CSS has three times the market share. Skelton CSS for pete's sake. A tiny 400 line library surpasses the bloated junk by a huge wide margin (relatively speaking).
The market share report also clearly shows that users prefer the utility-first approach of Tailwind CSS.
I need to make it clear: I do not use Tailwind CSS. I have taken a close look at the structure and direction of Tailwind CSS ... and I must say I believe this is the right approach. Tailwind CSS recommends post-processing as opposed to SASS pre-processing methods. I completely agree. It's the same approach I use in My CSS Framework. I have no intention of releasing mine ... I highly recommend you use and implement Tailwind CSS.
Better yet, make your own. It's infinitely more rewarding. Haven't got the time? Leave Bulma behind and take a look at CSS Frameworks that are increasing in popularity: Tailwind CSS has almost tripled in market share since the beginning of 2024. Skelton CSS is gaining. UI Kit is gaining.
The real market share losers are Bulma CSS, Foundation, Materialize.
By the way, Bulma CSS is just ahead of MetroUI and Spectre CSS. What are MetroUI and Spectre CSS? That's the same question we should be asking about Bulma CSS. What is it?
And, by the way, take this all with a grain of salt. It's my opinion. And to put that in perspective, I had originally selected, and used, Bulma CSS. Must - find - 12 - step - program ... LOL
As an add-on comment: I really like My CSS Framework. Between projects, I tweak it and add functionality. Adding functionality doesn't mean increasing size. It means meaninful gains in usability and functionality. Size: it's actually gone down. My flexbox grid covers every possible use of a responsive grid and has decreased to nearly half the size. It's gone from 14Kb to just below 9Kb. And, more functionality. I've even added a CSS Grid as a separate utility-first module ... only 6Kb. Load both in just a few bytes more than my original responsive grid module. Compare that to Bulma that tripled in size between v1.0.0 and it's predeceasor (v0.9.4).