So it needs to be commented on in every single article?
Yes
If so, is that going to change anything?
Potentially.
The alternative is not bringing up the concern and it goes forgotten until it is too late and we are stuck with the results of bad decisions for no good reason.
Developers voicing their concerns is the only way things can change for the better.
Here's two examples:
-
Redis licensing rug pull
- Redis unexpectly changed its own licencing
- Developers demanded Redis return to its original (or similar) licence
- Redis said no
- Developers formed their own Redis clones from scratch with compatible APIs
- Developers switched to the new Redis replacements
- Redis returned back to the original licence in an attempt to keep existing users
-
Google's JpegXL whiplash
- Google added support for jpegxl in Chrome
- Google removed support for jpegxl in Chrome in favour of inferior standards
- Developers demanded support added back
- Google said no
- Developers flooded every issue tracker and feature request with support for jpegxl, consistently, unrelentingly, for years
- Other browsers add support for jpegxl
- Creative industry adds support for jpegxl
- PDF association adds support for jpegxl
- Google forced choose between jpegxl or fall out of supporting pdf standard
- Google readds jpegxl support
And there's plenty of other examples (e.g. Microsoft against linux -> WSL support, etc...)
If developers don't voice their concerns, then things stop changing for the better.