They give multiple examples of general situations where APIs violate these rules (without naming names). And they explain the bad things that happen when you violate the rule.
I think this blog post will be useful to cite in bug reports when an API is making your life hell because it violates the principle, and you need to convince the developer that this is even a bug to begin with. Because you know the dev will want to close the issue with “works as designed”.
This “design principle” seems so obvious I’m not even sure why an article/blog post was required to explicitly say it.
They give multiple examples of general situations where APIs violate these rules (without naming names). And they explain the bad things that happen when you violate the rule.
I think this blog post will be useful to cite in bug reports when an API is making your life hell because it violates the principle, and you need to convince the developer that this is even a bug to begin with. Because you know the dev will want to close the issue with “works as designed”.
The implicit point (which perhaps they should have stated explicitly) is how often people violate this principle, sometimes without even realizing it.
I know (okay, I suspect) they’re trying to cover a short, simple point…
they just do it in a pretty… dense and clunky way.
this feels very… windows documentation -ish.
it’s 5 short paragraphs….
5 poorly written, dense, clunky paragraphs.
given your obvious skills you should write a better post.