4 ms·

You seem to be very upset about all of this... The nice thing about semantic HTML is that any metadata and structured data is a part of the document itself ins

You seem to be very upset about all of this... The nice thing about semantic HTML is that any metadata and structured data is a part of the document itself instead of hidden away somewhere else through an API. This has its disadvantages (I'd rather interact with an API than scrape a website, even if it's all tidy and semantic) but it absolutely also has advantages. The usual alternative to semantic HTML is not a well-designed API, the alternative tends to be nothing.

etler 13y ago
I write my HTML semantically primarily for myself. It's far easier to read, debug, and develop when the structure makes sense and isn't littered with a dozen nested divs with incredibly complicated class names.
- coldtea 13y ago
  >I write my HTML semantically primarily for myself. It's far easier to read, debug, and develop when the structure makes sense and isn't littered with a dozen nested divs with incredibly complicated class names. Sure, but nobody called for "a dozen nested divs". You can ease the same number of divs, semantically or not. Just make the styling targets are encompassing as they can be.
coldtea 13y ago
>You seem to be very upset about all of this... Which is neither here nor there regarding the validity or not of what I say, and a little rude to boot. >The nice thing about semantic HTML is that any metadata and structured data is a part of the document itself instead of hidden away somewhere else through an API. This has its disadvantages (I'd rather interact with an API than scrape a website, even if it's all tidy and semantic) but it absolutely also has advantages. The usual alternative to semantic HTML is not a well-designed API, the alternative tends to be nothing Which is fine too, since the usual case also is that nobody is consuming the raw html anyway except the browser.

4 ms·

You seem to be very upset about all of this... The nice thing about semantic HTML is that any metadata and structured data is a part of the document itself ins

by stdbrouw 13y ago

etler 13y ago
I write my HTML semantically primarily for myself. It's far easier to read, debug, and develop when the structure makes sense and isn't littered with a dozen nested divs with incredibly complicated class names.
- coldtea 13y ago
  >I write my HTML semantically primarily for myself. It's far easier to read, debug, and develop when the structure makes sense and isn't littered with a dozen nested divs with incredibly complicated class names. Sure, but nobody called for "a dozen nested divs". You can ease the same number of divs, semantically or not. Just make the styling targets are encompassing as they can be.
coldtea 13y ago
>You seem to be very upset about all of this... Which is neither here nor there regarding the validity or not of what I say, and a little rude to boot. >The nice thing about semantic HTML is that any metadata and structured data is a part of the document itself instead of hidden away somewhere else through an API. This has its disadvantages (I'd rather interact with an API than scrape a website, even if it's all tidy and semantic) but it absolutely also has advantages. The usual alternative to semantic HTML is not a well-designed API, the alternative tends to be nothing Which is fine too, since the usual case also is that nobody is consuming the raw html anyway except the browser.