I think Tailwind is phenomenal for implementing a design system on the engineering side, but it can't inherently solve many of the other reasons a design system exists: capturing and defining the patterns a specific product uses, creating consistency across the product, accelerating the design team and engineering team...
But most design systems fail to actually solve those problems too, and consume a fuckton of time and energy in doing so
Tailwind allows you to build a design system, but it certainly doesn't come with one out of the box.
Bootstrap on the other hand does.
Tailwind allows you to create a component library whose spec is a design system.
I think you're mixing design system with css frameworks.
There's Tailwind as a technology, but then there's Tailwind as a set of reasonable defaults. The original comment is referring to the latter, not the former.
That's correct^
reasonable defaults within a very limited scope vs a proper design system
sorry, Tailwind is the opposite of the design system concept. Design system is built around your product, not some generic style framework that helps you avoid building such a thing.