3 ms·

So given the popularity of tailwind I can conclude with confidence, that semantic movement has failed. HTML does not need semantics (because every big site is a

• tipiirai 3y ago
  The article is not about "thinking semantics". It's about making leaner and faster websites, and writing less code to achieve the same thing.
• rhdunn 3y ago
  It will depend on what templating framework the websites are using. Server-side rendering frameworks can allow users to write semantic components -- e.g. `<menu-button>` -- that get expanded to HTML markup, which will often be realized as many divs. This is often necessary to be able to properly style things like select controls or create more complex UI/markup. Tailwind is useful in this case, or with things like react and vue where the layout can be specified once in the component templates. If hand-writing the classes, the semantic model makes sense as it allows you to remain consistent in what styles get applied.
• e12e 3y ago
  CSS and HTML is great for documents - not so great for applications. Most sites end up implementing their own navigation UI/UX at a minimum (an application) - many end up as more applications. For an example of "documents", see eg: https://edwardtufte.github.io/tufte-css/ https://edwardtufte.github.io/tufte-css/ Or https://alistapart.com/article/building-books-with-css3/ https://alistapart.com/article/building-books-with-css3/