I think the point is that you can wrap all of this stuff inside a component, right? You don't want to have it like that all the time, all over the place.
BTW when using Bootstap I already tend to use a utility style approach like class="btn p-2 mb-3 d-flex" and so on, whenever possible. But of course Tailwind takes it up a notch.
Yup, you probably already use some form of separation of concerns, be it through a component library like React or template partials in backend frameworks like Laravel.
I have the same experience with Bootstrap and Vuetify. They adopt more and more low-level utilities. Interesting to see where this goes...
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Nice tutorial.
I think the point is that you can wrap all of this stuff inside a component, right? You don't want to have it like that all the time, all over the place.
BTW when using Bootstap I already tend to use a utility style approach like
class="btn p-2 mb-3 d-flex"and so on, whenever possible. But of course Tailwind takes it up a notch.Yup, you probably already use some form of separation of concerns, be it through a component library like React or template partials in backend frameworks like Laravel.
I have the same experience with Bootstrap and Vuetify. They adopt more and more low-level utilities. Interesting to see where this goes...