I agree that it's important to write both good and bad stuff.
Is also important to mention good things tools bring and not only subjective opinion on the bad stuff only. Why not mention both advantages and disadvantages if the aim is to give perspective for those looking to use the tool?
The title and the article itself is written in a negative manner, which is much more like "hey folks, I tried tailwind, I don't understand all the pros, don't understand how it can improve solo/team work, but will pour lots of shit on it'
The problem with "why not mention the advantages?" is that there needs to be advantages worth mentioning.
I mean, I agree with you. There are lots of tools for programmers out there that provide both advantages and drawbacks**.
Before I became a programmer, I actually was a journalist, and one of the things that my co-workers and J-school professors hated was the idea of false equivelance. The typical example is that 99% of scientists would agree climate change is real and manmade, while 1% may disagree, and to give the appearance of showing "both sides", cable news networks would book, on one side, a fringe skeptic, and on the other, a scientist. Or more likely, Bill Nye the Science Guy.
I'm not going to mince words - if I can't find a single positive thing to mention about a tool, I'm not going to go out of my way to scrape the bottom of the barrel to find something.
The thesis of the post is that Tailwind adds nothing. That there are no advantages to be had.
** A good example: Mongoose ODM for MongoDB. I personally wouldn't use it - I think it's too much boilerplate and cruft to add ORM-like structure to the relatively simple syntax provided by the MongoDB native Node drivers, and I don't like the performance hit when I used it (back in 2015). But the advantage is that you can organize how you interact with your DB in a standard way, follow existing models established by decades of relational DB management, and help to acclimate established SQL-heads to Mongo. Mongoose has advantages and disadvantages.
I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
I don't think this is something you can say about articles in general. It's perfectly fine to have an article that says, "I love X because Y" without mentioning its drawbacks - especially on a forum like this, where people will bring up their criticisms in the comments. It's responsible of the author to address those criticisms - or even to say something like, "I don't mind the drawbacks, I expect it to improve in the future" which acknowledges the criticism and moves on.
OP has already said they don't consider the claimed advantages to be legitimate.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I agree that it's important to write both good and bad stuff.
Is also important to mention good things tools bring and not only subjective opinion on the bad stuff only. Why not mention both advantages and disadvantages if the aim is to give perspective for those looking to use the tool?
The title and the article itself is written in a negative manner, which is much more like "hey folks, I tried tailwind, I don't understand all the pros, don't understand how it can improve solo/team work, but will pour lots of shit on it'
Sad.
The problem with "why not mention the advantages?" is that there needs to be advantages worth mentioning.
I mean, I agree with you. There are lots of tools for programmers out there that provide both advantages and drawbacks
**.Before I became a programmer, I actually was a journalist, and one of the things that my co-workers and J-school professors hated was the idea of false equivelance. The typical example is that 99% of scientists would agree climate change is real and manmade, while 1% may disagree, and to give the appearance of showing "both sides", cable news networks would book, on one side, a fringe skeptic, and on the other, a scientist. Or more likely, Bill Nye the Science Guy.
I'm not going to mince words - if I can't find a single positive thing to mention about a tool, I'm not going to go out of my way to scrape the bottom of the barrel to find something.
The thesis of the post is that Tailwind adds nothing. That there are no advantages to be had.
**A good example: Mongoose ODM for MongoDB. I personally wouldn't use it - I think it's too much boilerplate and cruft to add ORM-like structure to the relatively simple syntax provided by the MongoDB native Node drivers, and I don't like the performance hit when I used it (back in 2015). But the advantage is that you can organize how you interact with your DB in a standard way, follow existing models established by decades of relational DB management, and help to acclimate established SQL-heads to Mongo. Mongoose has advantages and disadvantages.Yes there is almost always both advantages and disadvantages. And it is on every individual developer / team to decide what works best for them.
And it is on the author to cover both sides to provide reader with constructs which will help to choose or reject the tool.
In this case, there are no advantages I could find, only disadvantages.
I suppoes the fact that I could find no advantages but plenty of disadvantages should people decide whether or not to use the tool.
I don't think this is something you can say about articles in general. It's perfectly fine to have an article that says, "I love X because Y" without mentioning its drawbacks - especially on a forum like this, where people will bring up their criticisms in the comments. It's responsible of the author to address those criticisms - or even to say something like, "I don't mind the drawbacks, I expect it to improve in the future" which acknowledges the criticism and moves on.
OP has already said they don't consider the claimed advantages to be legitimate.