Possibly the least surprising thing Dave could write about JsonFeed.
And the fact I remember the Atom kerfuffle is making me feel very old…
@bix Less good. I suspect the response is more about emotional investment than technology philosophy.
@adders @bix I would've loved for Dave to support it, but the good news is that JSON Feed is actually pretty widely implemented across tools and has been extremely useful in Micro.blog.
@adders Sigh.
It is a feature of visionaries like Dave that they hold fast to the One True Way they hold in their heads. This feature becomes a bug when that vision is not allowed to evolve as the world shifts around them.
…if 20 years after the advent of RSS, you don't have a toolkit in your environment to write feeds, you should probably do it yourself and share it with other devs.
And this is how we get the dependency nightmare that plagues most open source software.
@adders I find it very rich, considering Winer essentially said, “OK, RSS is done; it will never need anything else; Harvard, you own it now, and it’s frozen” (which, IIRC, is part of what got Atom started, but my memory from that era is in need of error-correcting storage media). Having RSS (as the dominant tech) without any way to adapt or steer it in the face of change is, I think, part of the reason feeds lost so much ground over the past decade.
I personally much prefer XML (because it looks like HTML, and I was familiar with HTML when I first encoutered XML) to JSON, but XML is such a pain, with its strictness and non-recoverability (yellow screen of death, yay 😜) and its annoying/buggy/painful parsers, and so forth…and the world in general got sick of those and moved on to JavaScript and JSON.
JSON Feed is clearly the feed format for this era of tooling (whether that’s good or bad, I can’t say, but the fact it’s alive and not frozen I see as a definite plus). // @bix @fgtech @manton