Shell and python scripts are also code which is executed. HTML (at least back in the day) wasn’t really a network shipped executable, but more like markdown file which is just parsed and rendered
This feels a bit like the debate over whether a virus is “alive” or not. “But the virus/HTML has DNA/code.” “But it requires another cell/web browser in order to replicate/execute.” etc. 😄
For the sake of simplicity, let’s go back to the time when websites were not full of JS and other modern web stuff
You could in principle just wget the html file from a server and parse/render it without having to run that file. Like I said, it is like a simple markdown file.
In terms of modern web, a crude analogy would be to look at the output from static site generators. In those, the server essentially doesn’t execute code, hence a lot of cloud providers can host your static sites for free
Shell and python scripts are also code which is executed. HTML (at least back in the day) wasn’t really a network shipped executable, but more like markdown file which is just parsed and rendered
This feels a bit like the debate over whether a virus is “alive” or not. “But the virus/HTML has DNA/code.” “But it requires another cell/web browser in order to replicate/execute.” etc. 😄
I really don’t think so.
For the sake of simplicity, let’s go back to the time when websites were not full of JS and other modern web stuff
You could in principle just
wgetthe html file from a server and parse/render it without having to run that file. Like I said, it is like a simple markdown file.In terms of modern web, a crude analogy would be to look at the output from static site generators. In those, the server essentially doesn’t execute code, hence a lot of cloud providers can host your static sites for free
I agree. Html could also be compared to a config file. Only parsed; it doesn’t provide new instructions (unlike python etc)