[SippinLean]

>So your screen-reader enumeration of the document structure is unpolluted by the physical layout which is stored in a separate data structure in a separate language. And that's... good, I guess?

Yes, that's very good.

You don't have source order independence with <table> either.

[BigJono]

Why do we want source order independence?

I'm seeing a worrying trend in front-end dev towards things that are "nicer" to "read" but more difficult to actually reason about. I don't understand what benefit we're gaining for removing the relationship between the order of the source code and the order things are rendered. All I see is a negative (it's more difficult to find the place to make an edit later on).

As the other guy said: "Meanwhile I see that native app development continues, as it has for like 30 years now, to shamelessly put UI components directly into hierarchies based on physical layout. And they still haven't tripped over the paradigm."

[SippinLean]

>Why do we want source order independence?

For when things change, for when we want to reorder content without scripting. Why would having it as an option not be preferred?

[douche]

Eh, they just reproduce paradigms from 30 years ago on the native app side, as the JS crowd does.