>The master branch approach isn’t always ideal and people prefer having actual releases to base their work on.

I think this is me. My view is basically like this - if you use a tech you know works, you're only wrangling with your bugs. If you use a tech that is still being worked on, you are wrangling your bugs and the bugs of the tech you're using.

To be fair, I've tried this master branch thing with both Iced and PopOS's Iced fork. One year ago, PopOs's Iced fork was so slow I realised it basically wasn't going to be production ready for non Pop distros anytime soon.

IMO, both suffer from having very slow release cadence but at least dioxus has CSS

▲

airstrike 2 days ago | parent [-]

I appreciate the thoughtful replies. I struggle to understand why CSS is such a big deal if you're not building for the web. I can make my app as pretty as I'd like using styling that isn't CSS. OK, maybe I miss glow effects, some nicer gradients and 3D transforms, but those are far from showstoppers and still worth giving up for everything else I gain with iced

▲

chironjit 2 days ago | parent [-]

I don't have an eye for styling. That said, I have hundreds of hours of experience using CSS and frameworks such as tailwindCSS.

Of course, if I am being honest, the real reason is that there is so much CSS code out there, I can really find anything I need. And so can the LLMs.

▲

airstrike 2 days ago | parent [-]

Thanks. I've been meaning to make a shadcn-like library for iced. Would that help?

	▲	chironjit a day ago \| parent [-]
		You bet! Shadcn is defacto component framework for a reason - it removes a lot of the mental load of design when you're an individual/small team building apps