News for hackers. Stuff that matters.
Re:Don't write just in plain text (longevity vs. authenticity) by mro_name on Wednesday March 02, 2022 @09:34AM (#30527729)
> no one will understand

that's a bit harsh.

And frankly, I don't understand 100% english either, but still we use it to communicate.

Re:Don't write just in plain text (longevity vs. authenticity) by bbarnett on Wednesday March 02, 2022 @10:42AM (#30528557)
The point isn't that you can learn it, but instead, having to learn it by examining it in depth, always wondering if there are things not used yet (does the doc you look at, only show part of the standard in its formatting? Imagine a doc not using a tag, but the tag is in other docs...), and then, writing code to covert it.

Standards exist for a reason.

We already have issues with people not understanding specs, and writing data out of spec, even with that spec in RFC's!

Re:Don't write just in plain text (longevity vs. authenticity) by mro_name on Wednesday March 02, 2022 @11:58AM (#30529539)
my favourite is the spec that was changed after the fact:

Applications using this syntax may choose, for the sake of readability, to specify a full-date and full-time separated by (say) a space character.

https://datatracker.ietf.org/doc/html/rfc3339#section-5.6

But what harm does it to restrict oneself to a few html tags?