Re:Write HTML Right
by Spivak on Friday June 10, 2022 @11:51AM
(#31695836)
Except for the fact that native apps also use SGML or XML inspired markup for their layout engines. A tree of heterogeneous objects maps extremely well to how people think about UI.
[ Parent
| on HN ]
Re:Write HTML Right
by WillusFredus on Friday June 10, 2022 @12:15PM
(#31696154)
I agree that a tree structure can work well for mapping UIs, but HTML does not. It was specifically design as a textual markup language. Its role has been expanded, but it has been done so poorly.
What really needs to happen it a separation of HTML from UI markup elements. HTML will be used solely for textual markup and a new markup language can be used for UIs. This would allow us to return to a proper separation of concerns.
Re:Write HTML Right
by ryanbrunner on Friday June 10, 2022 @02:14PM
(#31697560)
Sure, but that's an argument for creating new paradigms for having instantly available non-downloaded "apps". Right now, if you want a lot of what a webapp offers (100% cross-compatibility with any platform, instant updates, online syncing for free), you're basically stuck with HTML / Javascript.
Re:Write HTML Right
by TedDoesntTalk on Friday June 10, 2022 @02:47PM
(#31697958)
> What really needs to happen it a separation of HTML from UI markup elements
Do you mean CSS? Using <b>, <I>, <strong>, etc has been “bad form” for a while (maybe not strong though)
Re:Write HTML Right
by frosted-flakes on Saturday June 11, 2022 @11:25AM
(#31705179)
<strong> and <em> are the recommended ways to semantically bold and italicize text. <b> and <i> don't have any semantics and can still be used where it makes sense.