Inline CSS works better in a component world

Re:Inline CSS works better in a component world by IfOnlyYouKnew on Thursday August 20, 2020 @05:26AM (#24221471)

The latest possible start date for components on the web was when PHP/fi (or whatever it was called) allowed you to ```include``` other files.

Realistically, people were probably doing the same with perl scripts before that.

And any definition of component is going to find it hard to exclude standard html elements, other than by specifying that it's users being able to define new ones, and not just browser vendors.

Incidentally, CSS was the original implementations of user-defined components: it allows defining certain behaviours once, for a "class" or group of similar elements, then using it repeatedly.

[ Parent | on HN ]

Re:Inline CSS works better in a component world by FreeHugs on Thursday August 20, 2020 @06:21AM (#24221753)

I don't think that is the type of "component" the author means when he writes about a "component world". He constantly talks about his argument applies to "modern web apps".

I don't have the feeling that what he really means with "Inline CSS works better in a component world" is "Inline CSS is the better choice since the 90s".

[ Parent | on HN ]

Re:Inline CSS works better in a component world by j-krieger on Thursday August 20, 2020 @05:53AM (#24221592)

I remember when we loaded xml into a buffer in c and replaced template tags with search and replace.

[ Parent | on HN ]