| > after I wrote a bit of criticism that got popular. Nah, you was just jumping on the bandwagon of hating on Tailwind without even trying to understand the fact you are meant to use components with it. Given that this bandwagon regularly attacks Tailwind (or anything modern in fact) and the fact that you tweeted completely antagonistic and unneeded "refactor tailwind out of your codebase" to someone who was showing an interesting way of doing animation in Vue, I can't blame them for blocking all the N number of accounts that are harassing them. Anyone is in their rights to block someone that is antagonistic or nasty or just generally hurtful on a constant basis to them. Arguing against something knowingly in bad faith (e.g. stating incorrect facts about X to hate on X) is 100% antagonistic. Actions have consequences? https://twitter.com/wolfr_2/status/1280949237820383232 And even now you continue with "Now, getting blocked by a person, that’s one thing. I guess Adam’s coping strategy with criticism was an “I don’t want to hear it.”. Yeah, again, I can see why he blocks accounts of people like this. Flippantly phrasing it as "Oh, I guess they don't like being criticised" shows a lack of appreciation for why someone might block someone. Because they just don't want to put up with someone's shit. Who can blame them? > I don’t know if I was entirely productive at first because I first had to shake up my dev stack to add in support for PostCSS, PurgeCSS and figure out all kinds of Tailwind specific things. Fortunately you don't need to purge anymore, as it instead creates the CSS file you need upfront instead of purging it after. |