@.:A-MAN:. Yeah true. I just ended up using tailwind because I didn't want to be restricted by default styles and you have a way larger range of motion with it. It got really comfy when I got used to it. You can't really compare it to bootstrap, because it's meant to be an all-around styling system rather than a rigid framework. Their docs have some neat examples.
@CJ101 yeah you kinda have to know what components you used if you wanna use a custom bootstrap to reduce the size, but then again, because bootstrap is so common, assuming you use the official CDN it's basically free cuz of the odds you've downloaded it somewhere else and have it cached.
I'm not sure how bootstrap works since it's not really compiled unless used with a framework-specific package based on it (we use vue-bootstrap at work), but tailwind will purge any unused styles, keyframes, to reduce package size, which I like.
@CJ101 Ok, the color thing is definitely fair. Bootstrap seems unnecessarily conservative with their theming out of the box. That is one aspect that I wish was different.
@.:A-MAN:. I can kind of, but I have more flexibility with component styling in tailwind. I'm somewhat limited in color spectrum on bootstrap, too, whereas I have a muuuch larger range of shades to choose from w/ tailwind, and, again, I don't have to write any rules or pull out a color picker, I can just chuck it into class names. Bootstrap is made to just include and build a bootstrap interface, whereas with tailwind you can make look like a ton of different styles without customizing it beyond stock.
Also, I can prototype for multiple breakpoints all in one line, so once I'm done fiddling with the html, I can just clean it up by grouping it under one class name in the .css.
@umer936 I'm not writing out whole properties, I'm using tailwind shorthands, which I can do in one line. I get that it's "solving" a problem that doesn't necessarily plague anyone, but it noticeably speeds up my ui creation time
I honestly like tailwind a lot. If you don't want to write it all out per tag, simply make a css attribute with @apply and boom, a whole styled component under one classname.
@umer936 oh it's good, it's just one less download you're required to have. I still use it for some things occasionally, but just having the option to not use it for simple projects is great.
@BlueLake2 This is kinda how I felt looking through it.
My apps need to be maintained for 20ish years and tailwind doesn't feel like it will last so easily.
I do use Bootstrap, but every few years I can just do a migration to the new version and it looks more "modern" or whatever.
Like right now I'm getting rid of tons of stuff that use jQuery.
TailwindCSS seems like it would just be a bad path to develop stuff for the long term on.
I think I wrote a long status a while ago about how much I hate tailwind. It's cluttered, hard-to-read, and is the source of so many problems that become hard to discover. My girlfriend swears by it, but her team also maintains a project that's pretty isolated from the rest of her company's stack so they have more ownership and overall better comprehension.
I feel like tailwind could be great for fast mockups, but if I'm building anything that I'd have to read and understand at a glance 1+ years down the road then I'd be going with something else
@umer936 Yeah I feel like bootstrap has just the right amount of helper classes for common stuff without getting to niche. Just type up some css like a normal person if you have a special case?
People absolutely swear by it. Basically there are classes defined in css so you do <div class="py-8 text-base leading-6 space-y-4 text-gray-700 sm:text-lg sm:leading-7"></div> to define the style for the div
Please Login To Post
...but then why use that when it can just be a classname in SCSS?
I'm removing it in places as I go along, but didn't find it a big deal either way.
My apps need to be maintained for 20ish years and tailwind doesn't feel like it will last so easily.
I do use Bootstrap, but every few years I can just do a migration to the new version and it looks more "modern" or whatever.
Like right now I'm getting rid of tons of stuff that use jQuery.
TailwindCSS seems like it would just be a bad path to develop stuff for the long term on.
I feel like tailwind could be great for fast mockups, but if I'm building anything that I'd have to read and understand at a glance 1+ years down the road then I'd be going with something else
People absolutely swear by it. Basically there are classes defined in css so you do <div class="py-8 text-base leading-6 space-y-4 text-gray-700 sm:text-lg sm:leading-7"></div> to define the style for the div
See: https://play.tailwindcss.com/