Комментарии:
You are missing a very crucial point: you can abstract a component with "messy CSS" and reuse, BUT that is going to be STILL repetition. You can easily write `class="bg-blue-500 hover:bg-blue-400 text-white font-bold py-2 px-4 border-b-4 border-blue-700 hover:border-blue-500 rounded"` for just 1 button, but if this button is repeated 1000x in the DOM, that this long line just adds up. Now multiple this for everything and you have a way larger HTML file than if you had simply followed many years of good practice and wrote `class="main-button"`. Also is that clean and effective to abstract every train wreck into its own component? People I see just copy-paste these long classes to every div in a form for example.
Moreover, a thing that is going to happen in every company that makes it to have users: redesign. A well-thought out CSS architecture anticipates design changes, light-dark schemes and so on with CSS variables. Build a CSS zen garden with Tailwind friends.
Of course you will have a very strong reaction when somebody undoes 10+ years of progress with great marketing. Just learn CSS (also learn SQL, your life will change).
Bootstrap forever!!!
ОтветитьI really don't like it because it's hard to read.
ОтветитьCreate your own class bro @
ОтветитьI would like to use NextUI, but... it has TailwindCSS.
ОтветитьTailwind makes me want to vomit. It's a trendy way of writing horrible sloppy UI that makes people feel better about not being able to grasp the concept of semantic styles. (And yes, I'm a developer, so your video is accurate.)
ОтветитьNice click-bait of a title, for basically saying Tailwind is great and if you don't like it it's because you must be some novelty hating boomer :)
ОтветитьI really want to like tailwind, but I find for the way I like to tweak my css in the browser, it's not that great of an experience. I usually create some html/css and then start adjusting the styles/css in devtools so that I can see my changes in the browser and adjust things at the pixel level and add and remove classes as needed, even with live reload, this is tricky to do with tailwind, cause you can't really 'tweak' tailwind classes in the browser because they are compiled, you can only really disable or add new classes (with a browser extension) so you can't take full advantage of fine tuning your design in the browser, which makes for a clunky experience imo.
ОтветитьI hate tailwind it is ugly as F**k. I dont konw how much faster it is at the end but the moment you try to revisit it its like pile of poop.
ОтветитьI don't know. I find that the more I learn about CSS the less I like tailwind. I find tailwind becomes more unnecessary when building components like with svelte. It's just not that hard to write scoped css. I'm on the fence. It does get you started quickly and copy pasting a pile of stuff that looks good from the jump is nice. But these shortcuts can prevent you from really learning CSS which is the best investment and worth your time.
Ответитьi personally love tailwindcss
ОтветитьI don’t hate it and it seems useful. I just like being able to create elements liberally without having to alter any framework classes.
ОтветитьActually, we, the developers, LOVE TailwindCSS
ОтветитьPandaCSS > TailwindCSS
ОтветитьI love tailwind very much.
ОтветитьWhy do you love tailwind , its like inline style but worst
ОтветитьI completely agree with your analysis! Tailwind is great for components, but when making a pure HTML based site, I can understand that people might not like the "messiness" of it. In that case I would still recommend using something like SASS over plain CSS, to clean up the code even more if you prefer that.
ОтветитьPeople who don't use css and scss, and people who don't know how to use tailwind hate CSS.
Ответитьdidnt meet anyone hate it. haters gonna hate
ОтветитьWhy developers hate tailwind?
Developers: who said?
i hate those who hate tailwind. they love bootstrap only because they don't have the ability design something better looking. I've used bootstrap/bulma for more than 3-4 years.
ОтветитьAs a senior frontend dev. I concur.
ОтветитьIf Tailwind is truly straightforward and advantageous, why did its creators take years to develop Tailwindui and why is there a cost associated with the complete version?
ОтветитьIt’s just styling. Not that big a deal no reason to hate it lol
ОтветитьI adore it!
Ответитьezy pezy, use those long ugly classes for quick mock-up, but create your own classes and apply tailwind style on production if you want clean html code. no more bloated CSS bundles you dont need like using other popular CSS framework
ОтветитьI am wondering how there are lots of paradigms of separating and isolating the code, that this is good, and at the same time people encourage applying tons of css classes for styling a single div. This mess with 3 lines of css classes in a single div could be useful only if it is not you who will maintain the code after somebody. Css should be isolated as well. However in some cases tailwind is very useful.
ОтветитьInterestingly, the guy who hates tailwind is the same developer who in 2023 uses SASS and jquery because he's too lazy to learn ES5 >= and modern CSS3
Ответитьdevlopers love tailwind css
ОтветитьHater here. I prefer pure css in svelte, either scoped or globally so the html looks clean. And I work hand in hand with designers so custom designs are easier with pure css/emmet.
ОтветитьNot convinced
Ответитьcss was invented not to write styles inline😂
ОтветитьWhy would I fill my components with garbage classes instead of using clean style objects🤷♂️
ОтветитьIt’s very time consuming working with tailwind
Ответитьas a fullstack i hate it
ОтветитьI can't find anyone (in my co-workers) who hates Tailwind, we love Tailwind, tailwind changes the industry and it's so amazing.
ОтветитьI like the video, but is tell not show, show example when component works
ОтветитьJust dont use it 👻
ОтветитьWhen I first started out, I used tailwind and I started to hate it, then I moved on to scss, and then I started to use tailwind again and I fell in love with it. If you know how to use it and get the most out of it, you are going to love it 100%
ОтветитьActually, this is just one way to use it. If you don't like inline styling, you can @apply tailwind classes in your css file, so you can create your own classes. I will never understand people who hate on tailwind, and the only thing they can say is that it requires inline styling. Just take a look at the documentation before hating on something.
ОтветитьIf there are no wireframes and I'm just freestyling it, I use TailwindCSS to quickly set up a layout. Then I go back and start organizing the components and add classes. When you have a better idea on how you want your site to look like, you can name the classes and components better. Using typescript prevents any simple mistakes along the way.
ОтветитьI love tailwindcss.
ОтветитьI agree with most of this stuff, but what do you mean 'responsive by design'? You literally have to set styles manually for every breakpoint. The only thing I've seen that's responsive by design is the container class.
ОтветитьSeparating css and html makes a lot of sense but it's not the way most teams work. When a dev is stuck building css they prefer tooling such as tailwind over making css files.
ОтветитьTailwind > CSS
fact 💯
Naahhh.... I'll just use Bootstrap.
ОтветитьAs a newbie, I learned basic CSS then discovered TailwindCSS I used it and it further improve my knowledge in vanilla CSS.
ОтветитьI love it, cuz it's trade between clean html template file but complex css rules and a bit ugly html but all rules in it, I choose the latter because it's easier to build middle sized websites without time wasting by trying to find common css rules between components, for large applications maybe writing your own css rules and using presets is good
Ответить