[scoutt]

I don't think it has evolved. I feel that it became more like a hack, on top of a hack, on top of another hack, and so on.

In the late 90's - early 2000's, HTML started to being pushed into fields that, at my opinion, were unrelated (remember active desktop?). Before you had time to react, HTML was being used to pass data between applications. At the time I was already doing embedded stuff and I remember being astonished to learn that I have to code an HTML parser/server/stack in my small 16-bit micro because some jerk thought it was a good idea to pass an integer using HTML (SOAP, for example).

In the meantime, HTML was being dynamically generated, and then dynamically modified in the browser, and then modified back in the server using the same thing you use to modify it in the browser. It's a snowball that will implode, sooner or later.

[082349872349872]

"a hack, on top of a hack, on top of another hack, and so on" is evolution.

My HN username may be a case in point, drawing from a selection of twice five[0] digits due to legacy code of Hox genes: https://pubmed.ncbi.nlm.nih.gov/1363084/

[0] "This new art is called the algorismus, in which / out of these twice five figures / 0 9 8 7 6 5 4 3 2 1, / of the Indians we derive such benefit"

https://upload.wikimedia.org/wikipedia/commons/thumb/3/35/Ca...

[scoutt]

You might see the Homer Simpson Car[0] and call it evolution too. But what I see is a mess, described as a sequence of hacks and bad decisions, just like HTML (and web stuff) today.

[0] https://www.wired.com/2014/07/homer-simpson-car/

[xboxnolifes]

Homer Simpsons car did not evolve at all. It was designed all in a single iteration.

[kanox]

SOAP is XML not HTML, unless I'm missing something.

I'm happy that the world moved on to the point that json/yaml-like formats are strongly preferred.

[scoutt]

Correct. I wanted to say "pass an integer over HTTP (SOAP, for example)". An XML to pass some value, all over HTTP, ~20 years ago.