every once in a while we think about how javascript people sure do spend a lot of energy on trying to escape the actual javascript part (profusion of languages that compile down to js) and wonder if maybe there was a wrong turn taken somewhere

prepares to begin dodging tomatos

maybe the browser is a world made of shifting sands and we should not have built our technology around literal remote-code execution as a basis of delivering software, perhaps, just a little bit

yeah, yeah, yeah, other languages you have to download untrusted code for too, we know, we know

@atax1a Would you think I was out there if I suggested the wrong turn could have been CSS?

HTML x CSS combines what the remote party has to say with how they want it said. While that seems reasonable... the client doesn't belong to the one speaking - it belongs to the one listening.

@dat @atax1a oh. Thank you for humoring the idea anyway.

I do still think we took a wrong turn when we determined that the server owns the client's presentation though. Once sent, the content should belong to the recipient. All else stems from that.