@smallcircles🫧 socialcoding.. It's even crazier than that. I saw the thread a few days ago where 
@cwebberChristine Lemmer-Webber apologized for JSON-LD in AP and 
@evanEvan Prodromou defended it (but for backwards-compat, not because AP is linked data). The "extensibility" claim is technical gaslighting since that's only true if you use JSON-LD processing of AP data (practically no one does and there's no requirement to do it). 🤪 Even then it's a weak form of protocol extensibility.
@eyeintheskyThe Eye @smallcircles🫧 socialcoding.. @evanEvan Prodromou To be clear, I think json-ld has a lot of great ideas in it, and it's the extensibility and linked data compatibility (which was a strong group requirement) story we had at the time.
"JSON-LD is bad" doesn't really capture my views. "JSON-LD turned out to be too complicated for the majority of the ecosystem to work with, particularly when we gave the view that you could ignore it, except it creates a rift of interoperability between those who ignore it and those who don't and puts a burden on the latter who are doing their best to behave well" does match my views.
There are paths out of the situation, but I'm not confident in the discourse around them right now, and hesitant about how much I want to engage with it.
If you have a fediverse account, you can quote this note from your own instance. Search https://social.coop/users/cwebber/statuses/116120124765173116 on your instance and quote it. (Note that quoting is not supported in Mastodon.)