I was always wondering about how this approach could provide "instant playback".
This is the one feature that keeps me ensnared to the big streaming services TBH.
It's hard to get into the matter if one does not have much time to scoop information from the web.
I am a heavy user of spotify and their "station/radio" feature. Like a song? Go to it's song-station and explorer other songs like it.
It's this kind of discovery that keeps me using Spotify.
I feel like many of the points are complaining about the parsing side of JSON. Not the format itself.
You can argue that a format is useless when "everyone" parses it "wrong" but no specification on this earth is free of that.
Using a lot of json in our API space and it working fine (so far) leads me to think that OP complains about something that does not fit their use-case.
Firing people for choosing something that does not fit "your" use-case seems like a wild take.
I was always wondering about how this approach could provide "instant playback". This is the one feature that keeps me ensnared to the big streaming services TBH. It's hard to get into the matter if one does not have much time to scoop information from the web.