4 ms·
> from a language point of view, HTML is a markup language, it 'must' have no logic or processing. Client-side includes are not "processing". HTML already has
by naasking 1y ago
> from a language point of view, HTML is a markup language, it 'must' have no logic or processing.
Client-side includes are not "processing". HTML already has frames and iframes which do this, just in a worse way, so we'd be better off.
- somethingsome 1y agoI understand your point, but I still think it is bad from the point of view of language paradigms[1]. Iframes should have not been created in the first place.. You are changing the purpose of the language while it was not made for it. (yes in my view I interpret includes as a basic procedure) [1] http://www.info.ucl.ac.be/people/PVR/paradigmsDIAGRAMeng201.pdf http://www.info.ucl.ac.be/people/PVR/paradigmsDIAGRAMeng201....
- naasking 1y agoThere is nothing procedural about includes. In fact, it first appeared before HTML even became popular in Xanadu, called transclusion: https://en.wikipedia.org/wiki/Transclusion https://en.wikipedia.org/wiki/Transclusion