I've had gripes about Bulma pretty much since I started using it.
For example, why would anyone use "columns" and "column" class names ... "columns" to refer to a horizontal row and "column" to refer to a vertical column. Just about every other css framework, at least those claiming to be responsive, support naming horizontal rows as "row" and vertical column as "column".
All I can think of is that the developers are trying to avoid looking like they cloned something else.
I created a parser that modifies the Bulma framework and adds "row". Not to replace "columns", but to make it interchangeable. My version is 100% identical to Bulma for compatibility purposes, the "row" is an addition that makes it completely interchangeable. Anywhere "columns" is used, "row" can replace it. That way I can continue using snippets I find plus create my own.
Bulma version 1.0.0 is now released. That's one version I might skip. Absolute bloatware. "Puffer fish"-type bloatware, complete with spinny protrusions to keep away from.
Bulma version 0.9.4 was already huge at 240Kb. If you would believe it, Bulma v1.0.0 comes in at a whopping 713Kb. More than double the size (darn near triple the size).
Bulma v1.0.0 does support new features, notably Themes. Included are a light and dark theme. But, really, 713Kb? Using the minified version isn't that much better, 633Kb. The minified size of v1.0.0 is more than THREE TIMES bloated than the minified size of 0.9.4. Note: this is the generally available version of Bulma v1.0.0 (as found available as CDN).
There is a version of Bulma v1.0.0 with no dark theme included that is 380Kb (minified: 335Kb). This no-theme version is not generally available on CDN. If I use Bulma v1.0.0, I will be using this.
Gheez man, that's a whack of junk that needs to be loaded with each page. I already do everything I can to cache, pre-load, and compress pages to lessen the impact of size on bandwidth and speed up delivery of pages. I know most people are using high speed internet, but do we need to bloat the stream and limit display speeds back like we are in the 90s?
I don't use SASS. I just write small projects and (used to) use CDN to load Bulma css. Once I created my own customized version of 0.9.4 (253Kb raw, 211Kb minified), I include it with each project.
My customized version modifies two aspects of Bulma. The first, obviously, is to add the ability to interchangeably use "row" and "columns". I want to continue using "columns" for compatibility purposes. The second aspect is to remove Bulma's version of reset and replace it with sanitize code.
Let me explain. With the reset code in place, Bulma is as close to a useless tool as can be, in my opinion. With the reset code in place, Bulma forces you into a coding style that I don't want. For example, if you want <h1> to behave like a heading tag with large bold font, you have to put it in a container with the .content tag. That's not how I want to work. I don't mind better structure to HTML pages ... for example put all header code in a <header></header> pair, and put all footer code in a <footer></footer> pair ... but the main content of a website should not be forced into a div (or section or any other tag) with a .content class. It should be in <main></main> tags. Doing it properly like this gives you a lot more flexibility, for example: in creating sticky headers, sticky footers (that stay at bottom of page), and back-to-top buttons. Plus, it's clearer dileanation of the three main parts of a web page. Doing it this way means that anyone can use heading tags in headers, footers, and the main content sections. It's clear separation of content and code - and get a display that is expected (if degrading to no css).
Just as a by-the-way: I also have several other modifications that I include with most projects. These correct some aspects of Bulma that need enhancing, in my opinion. One is the burger included with most files. The line thickness is a bit wonky at some displays. I also have a typography css file ... now I must be clear, this is not strictly related to Bulma issues ... my background is page composition and typography standards in plain css files are absolutely horrid. One example: if you look at the <h1> tag on most websites, if the tag is the first element of a page, it appears lower than the top of the page. It should be aligned with the top of the page, particularly if there are left and right columns ... my css file adjust for all header tags with first-of-type statements that correct that. It's the same with bottom margin where the heading tags have way too much spacing and appear to be an element separated from text as opposed to supporting the text. Anyhow, that's a gripe for another column.