I can entertain the idea that perhaps typical users don't talk about it online because they're not very tech savvy so they just assume they're doing something wrong when a website or piece of software malfunctions.
But it's simply not possible for nearly all of these software programmers, web developers and tech enthusiasts to not be talking about it online.
Operating systems, desktop software, phone apps, games, firmware & drivers, major corporate websites, banking websites, gov websites, utilities websites... everything.
Over the past 5+ years it has increasingly become the norm for it to be horribly designed, malfunctioning or broken; or only tested on a single device with a single OS/browser of a single version.
Actual humans would not refrain from talking about this programming plague but bots set to not expose DEI-driven destruction absolutely would refrain.
Only during discharge (inception towards death) can there be function (life)...increase implies function expounding during discharge.
Few trick many to believe in exponential increase without expounding, while viewing loss as malfunctioning. In other words...things breaking isn't malfunction; letting things break is.
All (whole) reveals each one (partials) by internal separation, hence discharging functional beings.
Few tempt many together to prevent functional beings from recharging (temporary growth) during discharge (ongoing loss).
An enthusiast follows suggested enthusiasm while seeking confirmation from others along the way. This ignores en/in (within) thus/theos (god); which demands adaptation to origin...not following towards outcome.
Ignorance of reality, based on confirmation bias, permits few to use bots to feed confirmation to many. In return few feed upon the ignorance of many.