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.
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.