I believe you don't find Tailwind as a requirement in job listings because it's so easy to learn it doesn't make sense to list. Just learn it on the job. Actually, the same applies to SCSS or any CSS solution for that matter. While it's an important decision for a project it shouldn't be a priority for the hiring devs to find people with those skills, or for job seekers to judge a job posting on.
That is, generally speaking. Of course there are exceptions. And I'm speaking from a fullstack dev perspective :)
Tech Lead/Team Lead. Senior WebDev.
Intermediate Grade on Computer Systems-
High Grade on Web Application Development-
MBA (+Marketing+HHRR).
Studied a bit of law, economics and design
Location
Spain
Education
Higher Level Education Certificate on Web Application Development
Nope, the reason is that almost nobody is using it in enterprise projects which cover the major part of the market.
Community hype is not a reflex nor the present nor the future, it could be and it could not, we'll see.
As tech lead I see tailwind as a way to avoid unused css code in production but the drawbacks are there as well to be realistic and of course it's not the only way to reach that, there are several and the devs I work with focus so much in JS and so poorly in CSS that having to use this atomic class->css prop way to work would be a huge mess quickly in comparison on some (that knows HTML and CSS well) providing good styled components to others (that know only the very basic +JS)
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.
I believe you don't find Tailwind as a requirement in job listings because it's so easy to learn it doesn't make sense to list. Just learn it on the job. Actually, the same applies to SCSS or any CSS solution for that matter. While it's an important decision for a project it shouldn't be a priority for the hiring devs to find people with those skills, or for job seekers to judge a job posting on.
That is, generally speaking. Of course there are exceptions. And I'm speaking from a fullstack dev perspective :)
Nope, the reason is that almost nobody is using it in enterprise projects which cover the major part of the market.
Community hype is not a reflex nor the present nor the future, it could be and it could not, we'll see.
As tech lead I see tailwind as a way to avoid unused css code in production but the drawbacks are there as well to be realistic and of course it's not the only way to reach that, there are several and the devs I work with focus so much in JS and so poorly in CSS that having to use this atomic class->css prop way to work would be a huge mess quickly in comparison on some (that knows HTML and CSS well) providing good styled components to others (that know only the very basic +JS)