There's a middle term, and you can avoid dryness with tones other than condescension. While I always read Rachel's posts whenever they come up because they're jam packed with wisdom, I always find them a bit off-putting.
if i could put a point on it, it would be the implied entitlement and absence of gratitude. Sure, this architecture is not 100% efficient. But step back for a moment, take a breath and consider the number of human-hours spent to get it where it is today. Consider how many people are busting their humps, many volunteers, to keep improving it. We arw not _owed_ any of this. Just the miracle of elastic server config and multicore processors... Buying into the pessimistic viewpoint is dangerous: When these issues get improved, will we feel grateful and adequate? or will we find new flaws and get snarky about them?
Anyway, what i do really like abt this post is it shows the chain of technical details across the call chain. it connects together info on dozens of man pages, etc. I also appreciate how it points out the inefficiency is quite convenient for service providers.
> Consider how many people are busting their humps, many volunteers, to keep improving it.
I think criticism about gratitude is strange when the author is pretty clearly coming from the standpoint that it was a bad idea to use this in the first place (and, to be fair and with regards to Python specifically, I tend towards that standpoint myself) that labor begins to look like it's being set on fire. No Purple Hearts for self-inflicted wounds and all that.
