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

Coming to Terms with Tailwind

johanronsse.be

Post reply on HN
Print view View original

41–50 of 117 posts

Re: Coming to Terms with Tailwind

#41

Post by croes »

manojlds wrote: post #35
Wolfr_ wrote: post #27

Earlier quoted context omitted.

I was just using my other Twitter accounts to stay up to date, it's not a big deal. I just genuinely wonder if blocking people that don't agree with you is a good strategy. I guess over time things also changed, Tailwind 2y ago was not the same as Tailwind now. They hired a bigger team and became much more of a company.

Those tweets are not just disagreeing.

He just disagrees if using tailwind is a good idea.

Where is the problem that justifies blocking?

Re: Coming to Terms with Tailwind

#42

Post by tshaddox »

cldellow wrote: post #14

> Then there comes the point where I have to use Tailwind for work and I am blocked by an offical account and – that feels kind of stupid? Getting blocked by a company entity for having an opinion is kind of… strange? I don't understand comments like this. You still have access to tailwindcss.com for documentation. The company doesn't owe you space in their social media conversations. The company has real customers a…

Honestly, the only stupid thing is that Twitter won’t show you public posts from an account who has blocked you. Of course you can log out and see everything. That’s just silly. Twitter may as well say “this account has blocked you, so complete this tedious minigame to see their content.”

The end result is pretty ridiculous: because this author wrote posts critics of a very popular piece of software, the author must log out of Twitter temporarily in order to see any relevant posts or announcements from the official Twitter account of that piece of software.

Re: Coming to Terms with Tailwind

#43

Post by sergiomattei »

cldellow wrote: post #14

> Then there comes the point where I have to use Tailwind for work and I am blocked by an offical account and – that feels kind of stupid? Getting blocked by a company entity for having an opinion is kind of… strange? I don't understand comments like this. You still have access to tailwindcss.com for documentation. The company doesn't owe you space in their social media conversations. The company has real customers a…

Yeah, an open source project doesn't have to endure anyone's abuse.

That bit rubbed me the wrong way.

Re: Coming to Terms with Tailwind

#44

Post by mgkimsal »

DrBazza wrote: post #24

Not liking React, and Tailwind, is a bit like saying 'I don't like Netty/Sprint Boot, I'll write my own web server'. css (and javascript/webasm) are the lowest levels in web development, of course people are going to build on top of them. Building a design system on top of css is not a surprising outcome. It's not different to building a library on top of a language. The only problem I have with tailwind is that it r…

How is saying "I don't like tailwind" leading to "I'll write my own webserver"? If tailwind was, magically, the only alternative to hand-rolling everything, perhaps, maybe, but it's not.

Re: Coming to Terms with Tailwind

#45

Post by [deleted] »

Wolfr_ wrote: post #36
stanmancan wrote: post #29

Earlier quoted context omitted.

There’s a difference between disagreeing and being an ass. If you wanted to engage with them then try to have a conversation. All you did was say how terrible it was and not to use it. Big difference. Nobody owes you their attention.

I agree, but none of those tweets were directed at the authors. They were just talking about Tailwind in general. One was a poor joke. My 3 blog posts were a genuine attempt at trying to dissect what I didn't like about the framework. Many people wrote in to thank me for that perspective. I find it unfair to single out two historical tweets neither of which is directed at the authors.

[deleted]

Re: Coming to Terms with Tailwind

#46

Post by jf22 »

brightball wrote: post #7
hnedeotes wrote: post #3

Sincerely I don't understand what's the appeal of tailwind. It's just one more sign of dementia to add to the landscape.

After years of wrestling with what the “right” UI framework was and marrying your project to the syntax and rules, Tailwind has entirely removed that concern from my life. https://www.brightball.com/articles/thank-you-tailwindcss

Can you explain how you aren't married to Tailwind's syntax and rules?

Re: Coming to Terms with Tailwind

#47

Post by tambourine_man »

handrous wrote: post #40
tambourine_man wrote: post #16

> Just like I don’t like React I will probably never really like Tailwind. >But that doesn’t mean that I can’t be a professional and write the best Tailwind code I can if that’s what’s asked of me. This is something that I can’t understand. Maybe it’s just me, but we’re incredibly fortunate to be in a market with huge demand. It’s not like we live in a React only world. You can make a pretty good living writing in wh…

Some tech is easier to sell than others, depending on your market. If you're an agency chasing startupy clients, for instance, the more technical people on the other side of the table want to hear that you're going to use tech that they think will look good on their résumés and/or enable them to easily hire startup-type developers, so making sales means choosing some subset of that tech that will make them nod in agr…

>Depending on the kinds of jobs you want…

That's the thing. If you enjoy the tech, you can make a great living write the code you love. If the start-up name-droping life style is more important to you, than sure, go for it, just don't complain that the market demands XYZ.

Re: Coming to Terms with Tailwind

#48

Post by tambourine_man »

Wolfr_ wrote: post #21
tambourine_man wrote: post #16

> Just like I don’t like React I will probably never really like Tailwind. >But that doesn’t mean that I can’t be a professional and write the best Tailwind code I can if that’s what’s asked of me. This is something that I can’t understand. Maybe it’s just me, but we’re incredibly fortunate to be in a market with huge demand. It’s not like we live in a React only world. You can make a pretty good living writing in wh…

The context is that we're primarily a design company, the front-end is a way to express our designs. A big reason for me is that I want the bigger group in our company to experiment with several CSS techniques to grow as front-end developers. If I (as a manager) set a constraint on one type of CSS it is difficult to learn more. As an agency it makes sense to have broad capabilities. I think as a freelancer it's super…

It's wonderful to experiment. I wanna give Tailwind (and React) a second try if I find the time.

It's just that the post comes across as resignation, as if these techs are a fact of life.

Re: Coming to Terms with Tailwind

#49

Post by hesarenu »

leephillips wrote: post #26

One sentence in the article suggested that, ideally, people making websites would just learn CSS , but since that‘s an unrealistic expectation (why?), Tailwind can be useful if you have big team of “front-end engineers” who don’t quite understand the markup languages that they use in their jobs. I can’t argue with that. But it suggests that if you work alone or in a small group, actually learning CSS might make more…

Are people using tailwind without knowing css?

Re: Coming to Terms with Tailwind

#50

Post by tshaddox »

Keats wrote: post #37

I still don't get Tailwind either but I found https://github.com/seek-oss/vanilla-extract recently which solves the TS/CSS modules nicely. All the styles are extracted at compile time so no overhead like most CSS-in-JS.

vanilla-extract combined with Sprinkles is roughly comparable to the Tailwind software architecture, but without the default configuration out of the box. There’s definitely room for someone to come along with a default configuration that covers similar functionality to Tailwind’s.
Post reply on HN