Because it's a lazy response. OP might not be a software developer. Should they learn complex software engineering to try and contribute or should they call out a missing feature that's important to them so the actual developers have some data on what to prioritise?
It's no lazier than saying "Still no <feature> support"
a) that's feedback
b) it's useful in a comment thread like this so people can quickly see what the 'caveats' mentioned in the title of the post are
Feedback in a forum stating something the developers are probably well aware people want in a location the developers might not even be reading is not particularly useful feedback. As for the comment thread utility, sure, I guess if you think that not reading the article is valuable for the HN community, but I could just as easily argue that pushing back against comments like that could be seen as valuable for a community that values more thoughtful feedback.
It was valuable for me. I've been waiting for Asahi on M3 and quickly wanted to know what the 'caveat' was. Saved me some time.
You're entitled to your opinion that scrolling to the last comment on the page is preferable to reading the article. I'm also entitled to mine that it's a net loss to the quality of conversation.