As I answered above in the comments (twice) here and here, the article was written from the perspective that Tailwind CSS is ALREADY in your project.
So why write something by hand from scratch if you ALREADY use a framework where this functionality is ALREADY implemented out of the box with just two classes?
That's all, there was no further purpose to this article.
OK. I will add a warning about this at the beginning of the article, so that readers immediately understand that no one is going to CANCEL their favorite technology (SVG) on a global scale. Only on a project scale, where Tailwind is ALREADY used.
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.
Over-complexity. I have nothing against using CSS Frameworks, but we have SVG, period.
Hi,
As I answered above in the comments (twice) here and here, the article was written from the perspective that Tailwind CSS is ALREADY in your project.
So why write something by hand from scratch if you ALREADY use a framework where this functionality is ALREADY implemented out of the box with just two classes?
That's all, there was no further purpose to this article.