I think the core mismatch here is that you are optimizing for experience and NYT, as a business, is optimizing for revenue. Those two things often do not overlap.
I can virtually guarantee you that NYT has spent thousands upon thousands of hours optimizing and multi-variant testing their headline display to maximize conversion. In other words, if they followed your advice, they would be leaving money on the table.
As for your stock ticker display bug, keep in mind that NYT likely employs hundreds of developers and dozens of teams each owning various pieces of the website. Bugs will make it to production, so it's a matter of prioritization. I'd be shocked if they weren't already aware of that bug. It's probably lower on some specific team's backlog than a bunch of stuff that will be more valuable for the company in terms of revenue.
You are making my point for me: “you are optimizing for experience and NYT, as a business, is optimizing for revenue.” That is simply an attempt to explain away the bad experience of reading the Times. The explanation is probably correct. But by offering explanations for why the site is bad, you are implicitly agreeing that it is bad.
I wouldn't call it "bad". I'd say it's not perfect, and rightly so, because perfection would be lower ROI than some other things their developers could be doing.
I can virtually guarantee you that NYT has spent thousands upon thousands of hours optimizing and multi-variant testing their headline display to maximize conversion. In other words, if they followed your advice, they would be leaving money on the table.
As for your stock ticker display bug, keep in mind that NYT likely employs hundreds of developers and dozens of teams each owning various pieces of the website. Bugs will make it to production, so it's a matter of prioritization. I'd be shocked if they weren't already aware of that bug. It's probably lower on some specific team's backlog than a bunch of stuff that will be more valuable for the company in terms of revenue.