Bulma CSS Framework
bulma.io
bulma.io
I worked with it for a couple projects, I was not particularly pleased with it overall. It's okay, I guess, but just nothing to really write home about.
Also it’s a matter of taste, but its cyanish primary theme looks meh and it’s pretty hard to find a good theme. Feels like it could win 2x userbase by simply adopting better default colors.
Some of those are sellers of fake likes/follows on social media.
But I reckon in this case, if I had to guess, I think maybe it's an external or internal developer that's making lots of Casino websites. Maybe they work for a group that owns all those brands?
Surely it can't be individual casinos, where Bullma is big in the Casino website development space and has grown in that sector by word of mouth!? LOL
In this instance it feels a little weird. No good reason why a CSS framework would be particularly suited for gambling site operations, you may be right that it’s an SEO play.
css is the most performant way to create interactive experiences
if gaming (gambling in this genre) sponsored react, their customers would use a more performant poker app. react can barely handle being reddit.
you’re talking network
javascript, which i write every day and love, fundamentally can do what i’m talking about through shaders in webgl or webgpu but people generally reach for react, which is the performance bottleneck in the rendering loop i’m describing because javascript is fundamentally inefficient at graphics and why the technologies i’m referencing were implemented with javascript bindings in the first place.
i agree the network is important, but it is generally the last bit in a call stack for any given user interaction.
> you’re talking network
I'm talking overall page performance. A gambling site using React vs not is going to have an absolutely tiny impact compared to network latency. They're sponsoring this framework as an SEO play.
This framework works well and was pretty fun to use, until I wanted to style it my way, then it became my enemy.
But I saw there was a way to extend the styling to allow customization https://bulma.io/documentation/sass/extends so that issue is probably solved.
Just write css and save your brain space for actually useful abstractions.
Guess what? Taiwind has components too, but the built-in of course is never the exact thing people want, so they had to add utility classes. And when it doesn't cut, you go back to css anyway. A pointless effort only to add another thing you have to manage just for styling.
Make css model internally consistent, i.e. allocate inputs inside-out and not vice versa, plus another thousand microissues, then we’ll talk about raw css with only colorscheme imports. Until that, writing ad hoc half-framework is a waste of time.
You’re wrong because there’s no one size fits all: some prefer the design of Bulma, some prefer Bootstrap, some prefer Chakra…
The advantage of these frameworks is they come with a ready to use theme, which is why there are so many, not everyone likes the same thing. The disadvantage of these frameworks is that they’re often difficult to customize which is why headless frameworks like Radix and abstractions like Tailwind are taking over (but they will never replace the former framework because sometimes you want to use a pre-made design).
"instead of writing 100 class names"
"use semantic class names"
What a loop.
In less words, if you can’t stand Tailwind then DaisyUI is not for you.
The product website seems to suggest we can add DaisyUI to a React project -- and proceed with development with no additional notes on replacing the styles later before production
[1] https://react.daisyui.com/?path=/story/data-display-table--w...
[2] https://daisyui.com/resources/videos/react-ui-design-mastery...
<button class="bg-indigo-600 px-4 py-3 text-center text-sm font-semibold inline-block text-white cursor-pointer uppercase transition duration-200 ease-in-out rounded-md hover:bg-i">
Tailwind Button
</button>
<button class="btn btn-primary">
daisyUI Button
</button>
<Button>React Button</Button>You now need the extra JS from that <Button> component to encapsulate the HTML with TW classes.
Plus all the overhead from TW itself. You need a ton of classes to essentially replicate inline styles.
Plus all the CPU needed to parse and execute all that extra JS and CSS code.
I get that some people prefer this workflow and that's fine, everyone has preferences. But arguing this is better than sending an HTML tag with a couple of classes is absurd.
This works better for optimization because you reuse classes. End developer doesn't care. Designers use Storybook to keep track of the components.
> But arguing this is better than sending an HTML tag with a couple of classes is absurd.
If you compile/SSR your React, the end user will get an HTML tag with classes.
Isn’t that just semantic HTML with extra steps?
And when using TW with SSR you're still sending all those extra classes per element.
I am looking to create a reusable React template for a lot of POc /mockup/ demo websites - was thinking of using react-bootstrap so I can use components from bootstrap and apply bootstrap themes for the styling and colors.
Any advice on better choices today for this use case?
I see no explanation of the name on the site in the documentation, but there would be two origins that come to mind immediately:
- The japanese (romanized) spell of "bloomer", the garment, which is a well known cultural artifact, also famous in the manga/anime circles. It was removed from public school decades ago and stays in public's consciousness as an attire to wear mainly for porn, gravures etc.
- the DragonBall character named after the garment.
None of these two feel right in a corporate setting, and while a project name isn't everything, there's a myriad of other similar pojects out there with more recognition so the competition is tough.
It could enough for it to be only ever seriously checked in companies that are already past the point they care about any public image.
[0] https://news.ycombinator.com/item?id=41967064&goto=item%3Fid...
GIMP's name definitely hurted it before there was enough acceptance of it. Ultimately I think most names will work out if the project gets past a critical mass.
[0] I assume you put the sexy aspect into "politeness" ?
Names having connotations is one thing, their connotation coming either from the sexy field or a character in a giant commercial franchise is I think pretty rare.
It makes me wonder if there isn't some random system level library named "Pooh", getting it into a China target project could be an honorable feat.