4 ms·
Discussing HTML: > Just look at this video. It shows me pulling chunks out of the Amazon homepage as I browse it, while the page continues to run. Jut [sic] ho
by ad-hominem 9y ago
Discussing HTML:
> Just look at this video. It shows me pulling chunks out of the Amazon homepage as I browse it, while the page continues to run. Jut [sic] how… INCREDIBLE is that? Can you imagine pulling random chunks of code out of the memory of your iPhone or Windows laptop, and still expecting it to work? Of course not! But with HTML, it’s a given.
Yeah, because HTML isn't a programming language, and it's not related to whether or not the browser can render some site. It has nothing to do with the code in the browser's sanity or the server serving content. The more accurate analogy would be "Could you imagine pulling random chunks out of a string that was passed to a string manipulation function, and the function still completing?!" And the answer is yes, I can imagine that. Especially considering it is a mundane fact of life for most web developers. It's almost like the author doesn't fully comprehend the difference between a markup language and a programming language.
- bandrami 9y agoOr, more likely, you don't comprehend the point she is making about the browser as a programming target. Go try SmallTalk for a while and you'll see what she's getting at.
- ad-hominem 8y agoNot only are your points unrelated, but I'm intimately familiar with message-passing languages and metaprogramming. This article reads like somebody who is just beginning their understanding of computation and is fraught with inappropriate metaphors. Moreover, I understand her point completely and outlined the failures with her analogy above. Ripping out HTML while browsing a site has nothing to do with the "browser as a programming target" - no reasonable user would ever do that and 99% of jQuery scripts targeting websites would break if you drastically alter the HTML structure they depend on.