Hey, let's not be putting PHP in the same bucket as Tailwind! :P
But absolutely agree, popularity doesn't equate to worth of a project/language/etc. Just look at some of the projects on npm like is-odd (and its counterpart is-even which relies on the former). Thousands of downloads per week to avoid modulus math in our code and make things look "nicer" and more "functional".
Tailwind might have solved a problem, and that's logical to assume so (I've not seen what that problem is, but that doesn't mean it didn't exist), but it also creates its own problems, as you've pointed out. What we need to be doing is more of this, more questioning on our tools, and looking at alternatives that solve the problems in better ways without creating more issues.
I may be prejudiced on my view of PHP, mostly because I once took a job... an overseas job, too... where the job listing was for a JS engineer, the job interview talked about JS experience, the take-home test was to write a JS front-end (React), the technical interview was conducted in Javascript, and the job title was for "Front-End Engineer"... and then I open up the codebase, and it's 95% PHP.
I explored all possible avenues -- transferring to a different department -- putting transition to Node on the roadmap for the next quarter -- everything. No, apparently I was now the PHP guy on the team.
I lasted two and a half days, and started packing my bags, getting ready to move once again.
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.
Hey, let's not be putting PHP in the same bucket as Tailwind! :P
But absolutely agree, popularity doesn't equate to worth of a project/language/etc. Just look at some of the projects on npm like
is-odd(and its counterpartis-evenwhich relies on the former). Thousands of downloads per week to avoid modulus math in our code and make things look "nicer" and more "functional".Tailwind might have solved a problem, and that's logical to assume so (I've not seen what that problem is, but that doesn't mean it didn't exist), but it also creates its own problems, as you've pointed out. What we need to be doing is more of this, more questioning on our tools, and looking at alternatives that solve the problems in better ways without creating more issues.
I may be prejudiced on my view of PHP, mostly because I once took a job... an overseas job, too... where the job listing was for a JS engineer, the job interview talked about JS experience, the take-home test was to write a JS front-end (React), the technical interview was conducted in Javascript, and the job title was for "Front-End Engineer"... and then I open up the codebase, and it's 95% PHP.
I explored all possible avenues -- transferring to a different department -- putting transition to Node on the roadmap for the next quarter -- everything. No, apparently I was now the PHP guy on the team.
I lasted two and a half days, and started packing my bags, getting ready to move once again.