Python was an example of my point, but I was thinking even more along the lines of any scripting language that employs pre-processors, so the code inlining works.
Much like PHP does with open and closing tags, in the early days of Web development, I remember doing websites with Dreamweaver that way.
> Python was an example of my point, but I was thinking even more along the lines of any scripting language that employs pre-processors, so the code inlining works
I’m sorry, I’m not really understanding what you mean here.
> client-side PHP subset
I’d dislike it for the same reasons as before.
Php was made to and evolved largely for generating HTML on a server. Not to have snappy, non blocking, event driven user interfaces.
And since PHP is not a standardized the same way JavaScript is, any browser may or may not implement it the same was as another.
We’d be back in the early 2000s world of browsers incompatibilities.
What would native browser support for php give you vs a wasm implementation of it?
Much like PHP does with open and closing tags, in the early days of Web development, I remember doing websites with Dreamweaver that way.
How'd you feel about a client-side PHP subset?