| > 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 and potential customers who they want to engage with. Engaging with people who tweet "Tailwind is a terrible way to write CSS" [0] and "Refactor tailwind out of your codebase" [1] isn't a good use of the company's time. Blocking those people will also downrank their comments in @tailwindcss threads, which seems useful from the company's perspective. They're running a business, not a grievance forum. Maybe, one could argue, the company should engage strenuously with critics like this to try to convert them. But for me, no, they should focus on supporting the people who want to be their customers. [0]: https://twitter.com/wolfr_2/status/1310887766595637248 [1]: https://twitter.com/wolfr_2/status/1280949237820383232 |
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.