Because of backwards compatibility, HTML+CSS makes it cumbersome to use the simplest ways to layout things. And it's also confusing because the oldest ways are

Because of backwards compatibility, HTML+CSS makes it cumbersome to use the simplest ways to layout things. And it's also confusing because the oldest ways are still very much valid. You have to make divs (or semantic equivalents that I'm not sure are used anymore), and then mark them as different kinds of displays using CSS, with multiple sublanguages for multiple properties. Compare that to QML Quick Layouts[1], GTK containers [2] or winui controls [3] where you just instantiate whatever kind of display with the container you want in a single model using qml/GTK Builder XML/XAML and be done with it. [1] https://doc.qt.io/qt-5/qtquicklayouts-index.html https://doc.qt.io/qt-5/qtquicklayouts-index.html [2] https://developer.gnome.org/gtk3/stable/GtkContainer.html#GtkContainer.object-hierarchy https://developer.gnome.org/gtk3/stable/GtkContainer.html#Gt... [3] https://docs.microsoft.com/en-us/windows/winui/api/microsoft.ui.xaml.controls?view=winui-3.0-preview https://docs.microsoft.com/en-us/windows/winui/api/microsoft...