Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why Tailwind CSS Won

matt-rickard.com

Post reply on HN
Print view View original

521–530 of 559 posts

Re: Why Tailwind CSS Won

#521

Post by haswell »

emmacharp wrote: post #509
haswell wrote: post #470

Earlier quoted context omitted.

Most of my HTML/CSS skills were formed when these things did not have good built-in solutions. As someone who just wants to hack together a responsive blog that looks nice, the things that are now “simpler and easier in the long run” have not been easy or obvious to come by when looking for resources, and while I’d love a deep knowledge of CSS, the investment in time doesn’t make sense given my use case. This is why…

I understand this perfectly and is maybe the argument I have the most sympathy for. And, because you are absolutely right, I'm working right now on something like what you propose. The only way to convince people that CSS is a better (as in lighter, simpler, more efficient, etc.) solution than a framework like this, is to show and prove that it is. Arguments can only go so far... So, as the saying goes, I'll be putti…

If you need someone to test your content, I'll very happily raise my hand and provide feedback if desired.

Awesome of you to start a project like this.

Re: Why Tailwind CSS Won

#522

Post by emmacharp »

haswell wrote: post #521
emmacharp wrote: post #509

Earlier quoted context omitted.

I understand this perfectly and is maybe the argument I have the most sympathy for. And, because you are absolutely right, I'm working right now on something like what you propose. The only way to convince people that CSS is a better (as in lighter, simpler, more efficient, etc.) solution than a framework like this, is to show and prove that it is. Arguments can only go so far... So, as the saying goes, I'll be putti…

If you need someone to test your content, I'll very happily raise my hand and provide feedback if desired. Awesome of you to start a project like this.

Yeeah! That is really great to read!

If you are ok with sharing an email address or a website, I'll be sure to give you a heads up when the site is up and running.

Thank you for the kind and useful offer!

Re: Why Tailwind CSS Won

#523

Post by haswell »

emmacharp wrote: post #522
haswell wrote: post #521

Earlier quoted context omitted.

If you need someone to test your content, I'll very happily raise my hand and provide feedback if desired. Awesome of you to start a project like this.

Yeeah! That is really great to read! If you are ok with sharing an email address or a website, I'll be sure to give you a heads up when the site is up and running. Thank you for the kind and useful offer!

You bet! You can reach me at the email in my profile.

Re: Why Tailwind CSS Won

#524

Post by andrei_says_ »

weo3dev wrote: post #412
onion2k wrote: post #258

Earlier quoted context omitted.

You're not learning anything valuable by learning Tailwind. Learn CSS, that will stick with you for the next 20 years. You can't use Tailwind without knowing (quite a lot of) CSS. There's nothing in Tailwind that makes CSS easier or that obfuscates the technical understanding you need to make things with CSS. If you want to make a horizontal flexbox layout knowing "display: flex; flex-direction: row; flex-wrap: wrap;…

Except when using Tailwind, you're learning Tailwind nomenclature and syntax and approach - which really isn't modern CSS, at all. Today's CSS - if anyone would take the time to actually learn it as they do JavaScript - doesn't need something like Tailwind to make it powerful, scalable and manageable. I write plain CSS today, which is then scoped to components or bundles of interactivity, and all of those point to ma…

One more thing I find baffling is the preference to ignore the cascade… and seeing it as a benefit.

The cascade is where the value of CSS comes from! It’s an incredibly powerful concept.

I use and love the Inverted Triangle CSS (ITCSS) approach and write a fraction of the CSS code I used to.

Having a few utility classes, using variables for project-specific colors, breakpoints, spacing, using fluid typography, grid, and flexbox, make writing well-structured minimal CSS code a pleasure.

https://www.xfive.co/blog/itcss-scalable-maintainable-css-ar...

https://utopia.fyi/

Re: Why Tailwind CSS Won

#525

Post by andrei_says_ »

blitz_skull wrote: post #267
keyle wrote: post #140

Gray beard's 5c: Tailwind is a farce and a catastrophe. It's as modern as the style parameter is, and it's as reusable as a moving a dirt pile from one corner to the next. You're not learning anything valuable by learning Tailwind. Learn CSS, that will stick with you for the next 20 years. It amuses me when a library is implemented 'with tailwind', which means it's totally useless to the people _not using tailwind_,…

Cool hot-take but it’s not true. You’re literally learning CSS when you learn tailwind. And no one (good) picks up a tool solely because it’s shiny, they pick it up because they find it has utility, which evidently LOTS of people do. And if you don’t think it’s reusable then you at least need to bring an argument for why that’s so because the docs, personal anecdote, and the opinion of LOTS of people is completely op…

Most CSS codebases just like most JS codebases are low quality. This is a reflection of process more than anything else.

TailwindCSS puts a bottom threshold to the low quality - it guarantees a minimal level, regardless of what the rest of the codebase looks like.

This comes at the cost of general (but limited) messiness and guaranteed lack of maintainability.

I don’t use it but if I was on a team where engineers don’t talk to each other I probably would.

Re: Why Tailwind CSS Won

#526

Post by emmacharp »

haswell wrote: post #523
emmacharp wrote: post #522

Earlier quoted context omitted.

Yeeah! That is really great to read! If you are ok with sharing an email address or a website, I'll be sure to give you a heads up when the site is up and running. Thank you for the kind and useful offer!

You bet! You can reach me at the email in my profile.

Perfect! I certainly will.

Re: Why Tailwind CSS Won

#527

Post by jongjong »

dtagames wrote: post #478
ng12 wrote: post #443

Earlier quoted context omitted.

Web components are a decade old, what do you think has changed or will change to make them more popular than frameworks? I think unless there are massive improvements to the developer experience the best hope for web components is as an implementation detail for a higher-level framework.

Good question. I probably should have qualified my statement. I can think of a lot of cases where an organization is better off building custom components on something like Lit (close to bare metal), rather than trying to shoehorn Angular or React into what you want. On the other hand, having a lot of predefined pieces and methods is also helpful to some people. For me, I've been bitten and I would pick web component…

I also think not many devs have tried to work with web components and that likely explains its current lack of popularity. Many mid-level devs are not even aware of its existence or they mistakenly think of it as some low-level tech meant only for framework engineers or deep system engineering type people.

That said, having taught some introductory web development courses in the past few years, I sense that new devs entering the industry are interested in simpler solutions and not particularly keen to get into React. The React learning curve is much steeper than it once was now that it has so meany features and the benefits are not so clear to someone who is starting from scratch.

Re: Why Tailwind CSS Won

#528

Post by jstummbillig »

troupo wrote: post #191
jstummbillig wrote: post #82

Earlier quoted context omitted.

I do use tailwind and I find it terribly convenient for some things, but this argument still seems to mostly stem from too many people doing css who are not great at designing css and are doing things they really should not. How will I ever keep track of where I used px-6 and where md:px-4 in my templates and why, without semantic classes? Of course I can then build more solutions around that. Or I can accept that go…

> How will I ever keep track of where I used px-6 and where md:px-4 in my templates and why, without semantic classes? How will you track that in `.hero-text__sticky-container--primary` vs `.text-with-image__card-primary`?

I wouldn't. I would pick sensible class names. And then I won't care about what's inside specifically, because it's mostly dry.

And then it's still hard, because good css design is hard. Tailwind is not making that easier.

Re: Why Tailwind CSS Won

#529

Post by deprecative »

jonwinstanley wrote: post #265
deprecative wrote: post #194

Earlier quoted context omitted.

It's exactly the same but denser. There's no benefit that Tailwind brings that you can't get from writing your own cleaner CSS files. It's like a cult.

Yes, the only thing it does is makes writing styles slightly faster and stops you having to name every different component

Styles? Doubtful. Naming components? We have to do that anyway with how JavaScript/TypeScript frameworks work these days. Tailwind is a different way of doing it that introduces unnecessary abstractions. To me, that makes it worse than writing vanilla CSS. With CSS you don't have additional dependencies and build processes. It's just CSS.

Re: Why Tailwind CSS Won

#530

Post by mmis1000 »

arrowsmith wrote: post #486
jonwinstanley wrote: post #473

Earlier quoted context omitted.

When has anything in tech ever actually died? I guess there will be people building sites in React forever. Haha

Does anyone, anywhere still use Coffeescript?

I think that rely on several other fact.

- Javascript evolved, so you no longer need some crazy long template to support simple sentence like class extends - TypesScript appears, and also benefit the js eco system with d.ts files. And it even become coffeescript's short coming - Editor evolved, the editing experience is far better than before. The time typing long keywords can mostly compensated by auto-complete

But what will be the pain point that react can't resolve, other framework can and out weight any other benefits? I don't see that as for now

Post reply on HN