4 ms·
So the takeaway for me here is to avoid dogma, and if your “senior” coworkers are forcing it on you, leave asap. Oh and if you want to be productive, use Tailwi
by eep_social 3y ago
So the takeaway for me here is to avoid dogma, and if your “senior” coworkers are forcing it on you, leave asap. Oh and if you want to be productive, use Tailwind first and hand craft the small percent of CSS where that’s required later, if such a thing actually occurs. Everything else is just religion (in the emacs vs vim sense).
- timeon 3y ago> use Tailwind first and hand craft the small percent of CSS where that’s required later What is the difference between Tailwind and in-line CSS?
- throwaway98797 3y agoterseness
- eep_social 3y agoI don’t know, I haven’t done frontend in years. But I suspect this is an insanely common request, since the preamble on this [1] page addresses it head on: > Often the biggest challenge when working with a framework is figuring out what you’re supposed to do when there’s something you need that the framework doesn’t handle for you. [1] https://tailwindcss.com/docs/adding-custom-styles#using-css-and-layer https://tailwindcss.com/docs/adding-custom-styles#using-css-...
- rawfan 3y agoInline styles have no support for media queries, container queries pseudo classes (hover, focus), pseudo elements (before) and attribute selectors. With tailwind I can even just stack them like this "lg:hover:px-[10px]".
- andrei_says_ 3y agoNote that similarly to writing inline classes, if you need to refactor the css, you’d need to re-read and rewrite the class soup everywhere in your project.