4 ms·

Recently I had to develop a somewhat complex vuejs web app that works well in both desktop and mobile And most importantly I had only 7 days to develop it. And

by rukshn 4y ago

Recently I had to develop a somewhat complex vuejs web app that works well in both desktop and mobile And most importantly I had only 7 days to develop it. And I just breezed though the frontend development thanks to tailwind which I won’t be able to do had I used a different framework like bootstrap or vanilla css I think developers can select the features they want to use, and if they don’t want to use the new features they can just use the existing ones and leave the new ones alone. For the moment I don’t find a reason to skip tailwind

gedy 4y ago
> And I just breezed though the frontend development thanks to tailwind which I won’t be able to do had I used a different framework like bootstrap That’s interesting because I had the exact opposite experience with Tailwind. We were in a hurry to but Tailwind’s lack of standard component classes meant we spent a lot of time trying to find components to do basic things, we even paid for Tailwind UI but we found the experience really weird that all you get is code samples that you just paste into your code and tweak? We ended up going with bootstrap because there’s plenty of open source libraries that have all the components and it’s easy enough to tweak the bootstrap theme to look how our marketing and branding needed. Where we needed more customization, bootstrap has a lot of nice utility classes too now.
DoesntMatter22 4y ago
Tailwind is a lot of fun when you end up with spaghetti code and classes littered all over the place. Sometimes there are 20+ classes on 1 div, it's insanely hard to maintain. I love tailwind for small things but when I have to maintain it, it's pretty awful.
- tomtheelder 4y ago
  I've had the total opposite experience. I've found that any sort of CSS scheme that tries to be clever or have any meaningful amount of re-use becomes an unmaintainable nightmare over time. Tailwind keeps the bits and pieces of the utility classes as close to the content that they are styling as possible, and that _drastically_ reduces the complexity of maintenance. You use the reusability scheme you already have- typically components in some sense, React or templates or whatever- instead of attempting to layer another one on top for just your styles. In fact, maintainability is by far the #1 reason I use Tailwind. IMO it's actually quite a bit more clunky and slow for the initial styling process.
  - DoesntMatter22 4y ago
    idk what to say about that. Maybe you are using css wrong then
jmull 4y ago
I don't get that... Bootstrap a great for breezing through frontend development in my experience. The only issue is your site looks very much like a bootstrap site... which is completely fine for many kinds of projects (In fact, you might as well grab one of those decent bootstrap templates and breeze through even faster). I've been using tailwind for cases where a bootstrap site isn't OK. I can't breeze through so fast, but the site can look and act exactly as I need it to without fighting the framework.

by rukshn 4y ago

gedy 4y ago

> And I just breezed though the frontend development thanks to tailwind which I won’t be able to do had I used a different framework like bootstrap That’s interesting because I had the exact opposite experience with Tailwind. We were in a hurry to but Tailwind’s lack of standard component classes meant we spent a lot of time trying to find components to do basic things, we even paid for Tailwind UI but we found the experience really weird that all you get is code samples that you just paste into your code and tweak? We ended up going with bootstrap because there’s plenty of open source libraries that have all the components and it’s easy enough to tweak the bootstrap theme to look how our marketing and branding needed. Where we needed more customization, bootstrap has a lot of nice utility classes too now.

DoesntMatter22 4y ago

Tailwind is a lot of fun when you end up with spaghetti code and classes littered all over the place. Sometimes there are 20+ classes on 1 div, it's insanely hard to maintain. I love tailwind for small things but when I have to maintain it, it's pretty awful.

tomtheelder 4y ago
I've had the total opposite experience. I've found that any sort of CSS scheme that tries to be clever or have any meaningful amount of re-use becomes an unmaintainable nightmare over time. Tailwind keeps the bits and pieces of the utility classes as close to the content that they are styling as possible, and that _drastically_ reduces the complexity of maintenance. You use the reusability scheme you already have- typically components in some sense, React or templates or whatever- instead of attempting to layer another one on top for just your styles. In fact, maintainability is by far the #1 reason I use Tailwind. IMO it's actually quite a bit more clunky and slow for the initial styling process.
- DoesntMatter22 4y ago
  idk what to say about that. Maybe you are using css wrong then

jmull 4y ago

I don't get that... Bootstrap a great for breezing through frontend development in my experience. The only issue is your site looks very much like a bootstrap site... which is completely fine for many kinds of projects (In fact, you might as well grab one of those decent bootstrap templates and breeze through even faster). I've been using tailwind for cases where a bootstrap site isn't OK. I can't breeze through so fast, but the site can look and act exactly as I need it to without fighting the framework.