Live data from Hacker News

Thank You Bootstrap 1

kylerego.github.io

51–60 of 65 posts

Re: Thank You Bootstrap 1

#51
post #50
post #44

Earlier quoted context omitted.

I agree, but that approach seems to be uncommon or at least discouraged by the Tailwind creator. I'd actually recommend Tailwind shops use the DaisyUI plugin which gives component classes similar to Bootstrap.

Indeed, the reasoning I've read falls close to the last paragraph of your previous comment. Components will consistently apply "atomic styles" everywhere and so are thought to be a replacement for "semantic styling" (sprinkling in some quotes because I don't know the exact terminology).

Yeah it's one of those things I just don't agree with them from practical experience. No beef against utility classes in general just not for everything. In fact I really like Bootstrap's which are just enough to help, but are still themeable: https://getbootstrap.com/docs/5.3/utilities/api/

Re: Thank You Bootstrap 1

#53
post #46

Earlier quoted context omitted.

Things like Tailwind take the core concepts of bootstrap and build and improve on it on a grand scale. It is like comparing jQuery (bootstrap), to React (tailwind).

Tailwind and bootstrap are near opposite approaches to frontend design … What’re you on about?

People really do sell Tailwind as if it’s a Bootstrap-like framework. I think that’s why so many sites (see: most startups) have a very similar “Tailwind look” now - everybody wants to use Tailwind because it’s hip, but nobody actually wants to write styles if they can help it, so they just copy-paste a very basic rounded-border-plus-shadow style onto all their components and call it a day. It’s a little better than the “Bootstrap look” because at least it doesn’t come with a default accent color that nobody will ever change, but man, it’s not that much better.

Re: Thank You Bootstrap 1

#54

Something that I've often wished, as a primarily backend focused engineer, often without frontend support, is for designers or perhaps design engineers, to pretty much build Bootstrap themes. That would let me code to the Bootstrap docs (which are pretty good), while allowing us to brand or customise whatever we're working on. I've seen even contract designers push back on this idea, suggesting that doing such a thin…

I've seen both sides of this idea many times, and from my personal experience, this idea looks good on paper, but usually implodes in practice. Bootstrap gives you a baseline quickly, but what pretty much universally happens is that at one point a feature requires you to venture outside of its constraints and that's when the trouble starts. Overrides and extensions, then something changes in the underlying theme or y…

You’ve described it exactly. Bootstrap is great for concept. It’s easy to understand. Once you need greater customization look for something else.

Re: Thank You Bootstrap 1

#56

Something that I've often wished, as a primarily backend focused engineer, often without frontend support, is for designers or perhaps design engineers, to pretty much build Bootstrap themes. That would let me code to the Bootstrap docs (which are pretty good), while allowing us to brand or customise whatever we're working on. I've seen even contract designers push back on this idea, suggesting that doing such a thin…

> I've not used Tailwind, but it seems like perhaps the goal of Tailwind is to do something similar?

I'd say that's the opposite of the goal of Tailwind.

Tailwind is not like Bootstrap, Tailwind is to build your own design system component library. Tailwind makes it easy to build unique designs at the cost of having to make the design yourself. Bootstrap makes it easy to build a website with a premade design, at the cost of having the same design as your neighbour.

As someone who used Bootstrap / Semantic UI a lot in the past, I've finally concluded I won't be using them anymore: they ALWAYS end up being too rigid for what I want to do. It also invariably ends up breaking things in minor updates. Tailwind is freeing in comparison.

Re: Thank You Bootstrap 1

#57
post #25
post #11

Earlier quoted context omitted.

> What am I missing? You're not missing anything, companies like mine have done just this. We supported a messy situation of 7 webapps using different technologies looking 7 different ways. Once we got them to use Bootstrap, was a cinch to consolidate to a single company brand. The "big reskin" UX was gearing up for was as simple as a new theme, and was done without any drama. They were almost disappointed it was so…

The secret: use SCSS or LESS to pack the combined effect of "p-3 border-1 shadow-sm rounded-2" into a single class.

That just reinvents CSS the long way around. If you are making classes anyway, what do you need the shorthand DSL for the existing, robust DSL for?

Re: Thank You Bootstrap 1

#59
post #55
post #26

I can recommend halfmoon css for a visually pleasing nice drop in replacement.

That doesn't seem as well-maintained as Bootstrap. The last commit was half a year ago.

I hear ya, but it is CSS so the target doesn't move, Codeberg is using it for their docs [1], and it is easy enough to paper over any problems you might find. Good enough for me. Some might even say the more relaxed release cadence is a feature not a bug.

[1] https://github.com/halfmoonui/halfmoon/issues/116#issuecomme...

Re: Thank You Bootstrap 1

#60
post #25
post #11

Earlier quoted context omitted.

> What am I missing? You're not missing anything, companies like mine have done just this. We supported a messy situation of 7 webapps using different technologies looking 7 different ways. Once we got them to use Bootstrap, was a cinch to consolidate to a single company brand. The "big reskin" UX was gearing up for was as simple as a new theme, and was done without any drama. They were almost disappointed it was so…

The secret: use SCSS or LESS to pack the combined effect of "p-3 border-1 shadow-sm rounded-2" into a single class.

or use DaisyUI or something similar that does it for you
Post reply on HN