Backend guy here, but I wrote my website's Rails+Turbo frontend with Bulma. It's been pleasant, works well enough, generally hassle-free for typical web CMS-blog-infosite type duties. My only real complaint is the navbar menus lack submenus.
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
I've seen other open source projects with tons of gambling sponsors, it's not just Bulma. My guess is that it's a relatively cheap way to get links for SEO.
Usually it’s because the company uses the software in question and wants to ensure it sticks around.
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.
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.
In practice DaisyUI makes it easy for people who use Tailwind to quickly build prototype UIs. Later they can go back and replace the DaisyUI classes with Tailwind.
In less words, if you can’t stand Tailwind then DaisyUI is not for you.
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?
Bulma had a major update this past March to v1.0.0, with a couple minor releases since. Still receiving commits somewhat regularly, so I wouldn't call it dead.
Backend guy here, but I wrote my website's Rails+Turbo frontend with Bulma. It's been pleasant, works well enough, generally hassle-free for typical web CMS-blog-infosite type duties. My only real complaint is the navbar menus lack submenus.
About 50% of their sponsors are gambling websites. So sad.
I hate gambling ads and casinos.
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
I've seen other open source projects with tons of gambling sponsors, it's not just Bulma. My guess is that it's a relatively cheap way to get links for SEO.
It’s rather common for mid-sized OSS projects to have a lot of gambling sponsors for the links. Cheaper than ads.
Do they sponsor just for the SEO (getting your website mentioned on a frequently-visited website) or is there more to it?
Usually it’s because the company uses the software in question and wants to ensure it sticks around.
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.
Don't discount Bulma because of this though. It's quite a joy to use.
No. There's sadder.
Some of those are sellers of fake likes/follows on social media.
because it has follow links im there. It's a SEO spam.
Why is it sad?
Hard to see how casinos are much more exploitative than Silicon Valley social media companies. And they sponsor lots of tech.
I switched all my Bulma sites to https://daisyui.com/ since it works with Tailwind.
instead of writing 100 class names For every element, every page, every project, again and again…
use semantic class names sunglasses emoji Heck, how did we miss that for almost three decades? That's my favorite style now.No one missed anything. Most people now are using React with Tailwind, so their code is essentially
How is this a good thing?
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.
Bootstrap ?
he's joking
That's madness.
"instead of writing 100 class names"
"use semantic class names"
What a loop.
In practice DaisyUI makes it easy for people who use Tailwind to quickly build prototype UIs. Later they can go back and replace the DaisyUI classes with Tailwind.
In less words, if you can’t stand Tailwind then DaisyUI is not for you.
Looks very interesting and useful.
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 thought this project was dead?
Bulma had a major update this past March to v1.0.0, with a couple minor releases since. Still receiving commits somewhat regularly, so I wouldn't call it dead.
https://github.com/jgthms/bulma/releases
Aaaaannnd, it might be my own psychological issues, but I totally read the URL as "bulimia"