I'll summarize:
It's annoying that dB is often used as a physical unit without the necessary suffix.
It's annoying that the suffix seems quite random for most units
It's annoying that the factor for power differs from the factor for voltage, etc.
It's slightly annoying that it's usually decibel instead of Bel.
> However, we all agree that dBs are really useful.
Which part of the article was that again? I was surprised to see that conclusion as summary because it's not what the takeaway seemed like to me, so went back to the article and I don't see this mentioned, perhaps I'm overlooking it because I didn't do a careful read a second time
Well, we have seen something like this failing about six years ago.
Let's see whether
- there is a new killer-use-case or
- technology has advanced enough to make it less cumbersome or
- Apple can generate enough hype around it to make it work on its own.
SemBr author here. I chose SHOULD NOT for this rule for a couple reasons: First, as an affordance for text with ambiguous or unknown meaning. Second, as a hedge against introducing new meaning unintentionally.
Adding a semantic line break inherently changes the relationship between words, and we can't always be sure about the intended meaning of text. If this were MUST NOT, then any modification would risk violating the spec.
Then again, this may be my own, idiosyncratic reading of RFC 2119. If you'd like to discuss this further, feel free to open an issue on the GitHub repo here: https://github.com/sembr/specification/issues
I completely agree.
Using one line per sentence (and soemtime more lines when the sentence is longer)
makes it way easier to structure the text.
Markdown and are perfectly able to fit the text to the device you are reading on.
It also makes version control and diffs more usable.
However, I can also agree that this style might be not suitable for non-technical writing.
