3 ms·

My opinion moved from liking tailwind to loving it when tailwindplay got realsed (play.tailwind.com). It's so cool, and faster than any hot-reload ever will be.

My opinion moved from liking tailwind to loving it when tailwindplay got realsed (play.tailwind.com). It's so cool, and faster than any hot-reload ever will be. It's in my opinion is the smoothest way to create UI components on the fly with ease that of drag and drop tools, but with much more extended functionality.

epja 6y ago
I think you meant to link to https://play.tailwindcss.com https://play.tailwindcss.com
- mythz 6y ago
  Nice, instant live previews as you're toggling through IntelliSense is pretty slick.
jozzy-james 6y ago
even just using the element classes option in dev tools makes for rapid prototyping
jarek83 6y ago
I'm not convinced to Tailwind. Can someone explain to me how this is better than "normal" CSS? Take this example from the play site: 3 bullet points, each has to repeat the same thing: <li class="flex items-start"> <li class="flex items-start"> <li class="flex items-start"> vs classes: <li class="bulletpoint__container"> <li class="bulletpoint__container"> <li class="bulletpoint__container"> And when you have this all around your project, and then you decided to change 1 thing. How Tailwind makes it easier here? I tried to inspect the Tailwind styles in browser - sorry, but it looks like nightmare.
- cteague 6y ago
 It's worth noting here that the issue isn't duplicated css, but duplicated html. Ideally, this is handled by some other templating / component library (e.g. React). The idea is that if you have `bulletpoint__container`, that's going to be specific to this component only and hard to re-use in a different part of the application. It seems like Tailwind's main value proposition is that it forces developers to select from a limited, pre-defined set of options in styling which can then be used as building blocks for components. It basically circumnavigates css entirely to the extent the page can be styled using Tailwind's options. As far as I can tell, it's not really aimed at eliminating code-duplication per se. That should optimally be handled by whatever is generating your components. This article https://adamwathan.me/css-utility-classes-and-separation-of-concerns/ https://adamwathan.me/css-utility-classes-and-separation-of-... explains it better.
 - jarek83 6y ago
 Ok, the said article tells that it was not meant to be used in React or similar front-end stuff, but more in things like Rails. But even disregarding that, you might want to have multiple places with lists, or other elements that I guess would not be 'big enough' to become components.

epja 6y ago

I think you meant to link to https://play.tailwindcss.com https://play.tailwindcss.com

mythz 6y ago
Nice, instant live previews as you're toggling through IntelliSense is pretty slick.

jozzy-james 6y ago

even just using the element classes option in dev tools makes for rapid prototyping

jarek83 6y ago

I'm not convinced to Tailwind. Can someone explain to me how this is better than "normal" CSS? Take this example from the play site: 3 bullet points, each has to repeat the same thing: <li class="flex items-start"> <li class="flex items-start"> <li class="flex items-start"> vs classes: <li class="bulletpoint__container"> <li class="bulletpoint__container"> <li class="bulletpoint__container"> And when you have this all around your project, and then you decided to change 1 thing. How Tailwind makes it easier here? I tried to inspect the Tailwind styles in browser - sorry, but it looks like nightmare.

cteague 6y ago
It's worth noting here that the issue isn't duplicated css, but duplicated html. Ideally, this is handled by some other templating / component library (e.g. React). The idea is that if you have `bulletpoint__container`, that's going to be specific to this component only and hard to re-use in a different part of the application. It seems like Tailwind's main value proposition is that it forces developers to select from a limited, pre-defined set of options in styling which can then be used as building blocks for components. It basically circumnavigates css entirely to the extent the page can be styled using Tailwind's options. As far as I can tell, it's not really aimed at eliminating code-duplication per se. That should optimally be handled by whatever is generating your components. This article https://adamwathan.me/css-utility-classes-and-separation-of-concerns/ https://adamwathan.me/css-utility-classes-and-separation-of-... explains it better.
- jarek83 6y ago
  Ok, the said article tells that it was not meant to be used in React or similar front-end stuff, but more in things like Rails. But even disregarding that, you might want to have multiple places with lists, or other elements that I guess would not be 'big enough' to become components.