Reader view in mobile safari solves these things client-side. There are others. It's a rendering decision which should be left to the client vs forcing a decision on users in a way which breaks some configurations for people (since there's no way to disable AMP).