the rate of unhinged software convolution has made getting any worthwhile information about a new software update, other than "It's here! & Update NOW!", increasingly difficult. and god damn you, believe me, if there is one god damn thing i can speak authoritatively on, it is the physical and psychological motivations driving someone to embark on the asinine and joyless task of writing software. i'll explain:
there's essentially only a handful of software update descriptions types:
3252.5236.213476243572_A -> 38525.5.1256.7835462453_AC (thanks, but i understood this is the newer version due to how time works. i don't care to hear the particularities of which versioning scheme philosophy you prefer after reading some other nimrod's 90,000 hackernews/medium essay on)
We have changed a lot of words in our various terms of services/private policies/etc as we do every week (🤨)
Security Update (subtext: haha holy FUCK dude don't even wait to download this, run to unplug your router right now, you're already probably boned)
Security Update (subtext: our poorly written client software is interacting badly with our poorly written backend software in a way that is making the datacenter very, very hot. an executive, understanding none of of the explanations for why their AWS bill has extra digits at the bottom, will frame this is as Client Problem to excuse any shortcomings attributable to them and also get you to download the update right goddamn now)
libchickenconfmgr StructObjThing{} deprecation in favor of AbstractOOPThing subtypes interfacing scheme (words that have value to like three people like me, and meaning to an already-pretty-small subset of cursed individuals writing software for a living)
none are helpful, why even write 'em? people will land on this conclusion, and eventually it will become policy not to include detailed update information. and that will lead to a bleak computer future
there's an old image that paints the picture of why & how that will occur beautfully, i can't find it, so you'll have to settle for a description, but it is a photo of a computer monitor with the windows pre-boot update screen, progress bar, and text reading "You don't need to know or understand what your the computer device is doing, how long it will take, or why your inputs were ignored while a countdown ominously popped up until the reboot preceding this update.” i'll leave it as an exercise to the reader to connect the dots
the people enacting these policies won't do it with premeditation. they will shamble through their job boorishly until the idea of not including software update information has already implemented itself naturally, and only then will they realize the utility it gives them. internally, they will think it was all premeditated, because they think they are patrick bateman or the joker or some shit
origamiaround
dededos
romaincrisis
snowghoul
vaporwave
blakekathryn
gummygunk
jacobvanloon
baratheonpilled
