Content negotiation is useful when there are multiple feasible return formats. But when is that the case? For data, Json is the absolute king. For content, htm

Content negotiation is useful when there are multiple feasible return formats. But when is that the case? For data, Json is the absolute king. For content, html is king. There is very little to negotiate. The only case where I needed that feature was when data scientists wanted to download data from my API and needed a bunch of formats (parquet, CSV, TSV). But then they did not really grok content negotiation and asked for a query param. So finally I think this is like a lot of html features: half baked and from a different time. Html would do well to drop it.