[Wolfr_]

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.

[stanmancan]

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.

[Wolfr_]

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.

[tinco]

Twitter blocking is not about owing attention, a Twitter block prevents the blockee from seeing your tweets. The company is basically punishing Wolf for their critical tweet.

No one is owed anyone in this scenario, but it's just crappy behaviour from Tailwind. They probably are just tired from the negativity, I mean just look at their site the framework does look terrible, they even admit to this with this quote on their site front and center:

"If you can suppress the urge to retch long enough to give it a chance, I really think you'll wonder how you ever worked with CSS any other way."

Even though the code is offensive to the senses, it apparently works really well. Judging from the adoption and the beautifully designed UI's they are showcasing people do recognise its usefulness.

[manojlds]

Those tweets are not just disagreeing.

[croes]

He just disagrees if using tailwind is a good idea.

Where is the problem that justifies blocking?