[clug] Think Pieces

[jhock at iinet.net.au]

I don't think that it's hard to do. In the past I've developed thousands of HTML pages and interfaces. Some hand produced, some by code. Everyone of those were valid HTML.

I would develop a valid HTML static page and then the dynamic stuff would be fitted into the nested areas of that HTML. As long as the dynamic stuff was valid HTML then it would be valid when inserted into the nests. Not hard at all in my opinion and decades of experience. 


On 11 July 2021 12:43:02 am AEST, Sam Couter <sam at couter.id.au> wrote:
>So a whole bunch of stuff about an immature industry here. One root
>cause
>of these problems is that in software we're still learning what we're
>doing. Everything is uncertain for lots of reasons, we've only been at
>it
>seriously for a few decades and the complexity of what we do is insane
>compared to the average office building. Maybe we'll never have it
>worked
>out as well as civil engineering is because of that complexity.
>
>Anyway, one specific thing stuck out to me:
>
>On Sat, 10 Jul 2021, 12:10 jhock--- wrote:
>
>> All the developers have to do is validate their HTML and it's a
>disgrace
>> that developers expect otherwise.
>>
>
>This is harder than it seems - the HTML is usually generated so any
>part of
>it may come and go based on application state and user actions. You'd
>pretty much have to manipulate output in a DOM and serialise that to
>get it
>right every time. And if you're doing that, the browser already has a
>DOM
>so why not manipulate that instead of delivering any HTML at all? Use
>the
>modern tools available, e.g. Vue.js, React or Angular.