> XML just lost naturally, like GOPHER

Lost? The format is literally everywhere and a few more places. Hard to say something lost when it's so deeply embedded all over the place. Sure, most developers today reach for JSON by default, but I don't think that means every other format "lost".

Not sure why there is always such a focus on who is the "winner" and who is the "loser", things can co-exists just fine.

▲

sharpfuryz 2 days ago | parent [-]

Do you use it daily in browser?

▲

jeroenhd 2 days ago | parent | next [-]

Tons of APIs and applications work with XML. XSLT less so; that's more of a backend language.

▲

aragilar 2 days ago | parent | prev | next [-]

Yes, RSS.

▲

TiredOfLife 2 days ago | parent [-]

Which browser? Firefox and Chrome have no support

	▲	aragilar 21 hours ago \| parent [-]
		Which is why people are up in arms about XSLT, as you can provide previews of the feed via it.

▲

MrVandemar 2 days ago | parent | prev [-]

Immaterial. If the answer is either 'yes' or 'no', it makes no actual difference: gopher still exists, is still a thing, is still successful. It feels like you're just trying to move the goal-posts and redefine what 'lose' means and trying to lure the poster into a "gotcha".

▲

sharpfuryz 2 days ago | parent [-]

It's not about a "gotcha." Browsers once supported the GOPHER protocol but dropped it around a decade ago. This serves as an analogy: if users don't use XSLT/XML daily, browsers may eventually drop support for XSLT - supporting features cost money

	▲	MrVandemar 20 hours ago \| parent [-]
		That's not a great analogy. Firefox once supported RSS feeds as live bookmarks and dropped it, and not because people didn't use it, because people did use it and bemoaned its loss for years afterwards.