Is bootstrap going to be replaced with tailwind?

Not until tailwind have supported components like tabs, modals etc

Most developers on IHs and twitter love wasting time. When doing client work etc you want to move fast and make sure you don't have to maintain old features.

TL;DR: No. Yes. It depends.

There's no simple answers here since the technologies are not 1:1, and many folks don't seem to understand the differences or similarities. For example, you have to pay $250 to gain access to the TW component template which has no JS, while BS's component framework is a dominant feature that has been a go-to choice for 10 years. That's a lot of lead time.

BS5 is coming out very soon, and it drops the jQuery dependency which was a major pain point. Meanwhile, 90% of the utility classes that TW offers have direct parallels in BS, they just aren't grouped and described as a "utility framework". So much of this is how things are bundled and branded.

Tailwind is typically a lot harder for the average user to set up.

However, the biggest difference between the two frameworks is the availability of tens of thousands of themes - free and paid - for Bootstrap, where no parallel exists for TW.Bootstrap themes are a meritocratic cottage industry worth many millions, while Adam Wathan has structured TW so that the only person making money is Adam Wathan. These two market models speak to the very different core demographics for each framework. Bluntly: TW attracts geeks who are chill with spending the day tweaking PostCSS and think of their sites as a hierarchy of components with elements holding 20+ CSS classes, while Bootstrap is a huge success with designers and less technical bloggers and solo entrepreneurs who don't mind paying a small amount to have a nice looking site out of the gate. I'd hazard to guess that the typical TW enthusiast wouldn't buy a paid theme, even though they would be very sad if someone pointed out that their sites all look like programmers made them.

As for the total market size: it goes without saying that there's more than enough opportunity for these two very different approaches to coexist; I'd speculate that most Bootstrap users wouldn't even hear about Tailwind, because their problems have already been long since solved by Bootstrap.

So with that said, I'd like to point your attention to Bootstrap vs "tailwindcss" on Google Trends. Notably, the disproportion between the two is such that Tailwind doesn't even have its own recognized tag. Tailwind's impact on Bootstrap has been and continues to be a rounding error, and Bootstrap 5 is going to renew the excitement all over again.

https://trends.google.com/trends/explore?geo=US&q=%2Fm%2F0j671ln,tailwindcss

Don't know the point of tailwind and don't want to know. I know bootstrap with its container, container-fluid, row, col, nailed flex, align-item, order so why do I need to bother with something else. 🤷‍♀️

Personally, I don't see them as doing the same thing. Tailwind is about writing your own components, composing classes etc.

Bootstrap gives you prebuilt components out of the box. For me, it's an issue of productivity. I hate doing frontend, so I'm glad for frameworks like Bootstrap that give me things I can throw into my app and customise, rather than start from scratch.

I like Tailwind but I dont think Bootstrap will go anywhere soon. I do technical consultation to some big product companies. The number of third party components amount of auto-code generation and apps built, knowledge, the way we share design and styles... and how deep bootstrap and other frameworks (like Fomantic-ui/Semantic-ui) are, it needs years for Tailwind to grab complete market.

I defiently love to play with Tailwind because it is fun and easy, but I wont use it in my consulting employers projects.

I am guessing Bootstrap and others will incorporate Tailwind style into their frameworks.

I've designed more than 50 websites in Bootstrap and it is awesome. I gave Tailwind a try after it's fame shot up. Right now, I am developing all new websites in Tailwind, almost zero learning curve, gives me completely flexibility to design whatever I want and however I want. Without a doubt, loads faster than Bootstrap.

I like it but I have no knowledge of bootstrap really so for me it’s not a big cost to adopt either.

I think it’s preference here really and bigger teams or heavy custom UI projects might profit from tailwind others might profit from bootstrap

I'm still using Bootstrap and it gets the work done.
But just for the sake of trying something new, I'll try TailwindCSS and compare both based on my own preferences.

Being a Laravel developer i love tailwind, its very freeing. But the past month or so ive been working on a project using bootstrap v4.5. I think the last time i used bootstrap before this was v3.

I must admit it was weirdly refreshing and familiar. Still found myself trying to apply tailwind classes though.

I don't think it will die, it will/is moving more towards tailwind while still retaining the core components like made it soo popular in the first place.

Yes, it will but they still have a long way to go.

It's missing the javascript part, and some devs can't write js, but there is many components made with Alpine.js that are incredibly easy to use, and responsive.

Personally, I am working on Tailwind CSS templates and sections

the site is made with Tailwind CSS V2 and alpine.js, on the navigation.

Honetsly, there's hundreds of resources to make your landing page.

TW is a thin abstraction over CSS, turning continuous css values into discrete ones aka tokens aka utilities classes, helping devs spend less time making design decisions, and minimizing the chance of making bad ones. Hence why many devs swear they magically become better at design when they use TW.

If your team is well versed in design systems you probably don't need TW because you can make your own utility classes specifically designed for your design system, but that's a lot of work if you consider that each utility is coupled with breaking points, states, etc..so you'll just end up recreating a subset of TW.

So TW is great if you don't want to make that effort and if you're down coding common interactive component, because none come with TW, which makes sense as TW is just a utilities lib.

On the other hand Bootstrap is a fully implemented design system and css framework that comes with many interactive components out of the box. Many devs like bootstrap for the convenience, the huge ecosystem, something TW is lacking.
TW will eat a bit of bootstrap users, but won't kill it.
Bootstrap will likely stay the most popular.

I used tailwindcss once in a landing page.
But, still I use material design (vuetify) for most websites and web applications.
It's easier for me who is NOT AN EXPERT ui/ux designer to use a FRAMEWORK.

I don't think so. I think there is some Bootstrap fatigue, but Bootstrap 5 (due to come out soon, you can try the beta too) really improves on it.

As a more general answer on hot new technologies:
I think that boring is good for long-lasting technology, clever frameworks/tech will come and go from popularity but boring stuff (Wordpress, Bootstrap, Go, Java, Django, PHP, JQuery) will forever play a hidden but large role (due to it just working).

This makes the "boring" choice a good one for business: it may be less fun to develop but it will work forever and finding someone to take over development from you eventually should be easy. Imagine 4 years ago making the choice to use Meteor (I've used it in a few projects - SUPER productive in it! But it's all magic), you would regret that choice now.

Personally I think tailwind >>>>> bootstrap. It's just so much more intuitive, extensible and flexible. But I'm not hear to start a flame war :) Just to share my opinion

Looks something like https://allmassagechair.com/ also comes with a website builder for your marketing site.