[krinchan]

Having been outside of the frontend development world for innumerable years, I'm talking out of my backend here. But a cursory look gives me the instinct that Tailwind is kinda like Very Fancy Bootstrap. This blog post certainly makes the discourse around Tailwind to sound eerily similar to the discourse around Bootstrap.

Bootstrap got trashed regularly for being the Times New Roman of web development and any mention of it online would summon a howling pack of CSS purists. However, back in it's heyday, you could join a team and immediately start to make an impact because you knew the CSS class names and what they did. You still had to have someone around who knew CSS extensively to work out some corner cases. However, it definitely let the juniors get up to speed and when they hit one of those corners, provided a great mentoring opportunity to help them grow their knowledge of CSS.

[antihero]

It absolutely isn’t a very fancy bootstrap, that would be more like DaisyUI

[krinchan]

Okay you pointed me at a Tailwind plugin that provides Bootstrap classes.

I have no idea what point you're trying to make.

[antihero]

> a cursory look gives me the instinct that Tailwind is kinda like Very Fancy Bootstrap

I was refuting this as it is not really the same, and pointing to you something (a UI library built with Tailwind) which is more logically comparable to Bootstrap.

[krinchan]

> kinda like

You seem to have missed some words. Please point out how Tailwind is not a tool that makes working with CSS more standardized and simpler for someone just sitting down to your code base?

Literally the entire original comment was just that Tailwind fills much the same role as Bootstrap did, just with far more capabilities. Thus, it engenders the same flame wars that were fought over Bootstrap. You responded by saying, "It's a superset of Bootstrap."

Which is what I was saying by "Very fancy Bootstrap"?