The responsible product owners will already have bounced 18 months prior after tweaking the stats to falsify the customer satisfaction rate and grabbing their bonus on the way out.
Consider that the people who have never have never had to be on-call for a product that results in losses for the company in the event of an outage, and/or have never had to attend an RCA meeting have just as much of a voice in this discussion. Some segments of the software industry don't even have to worry about those sorts of things, and it's easy to get myopic after a while...I doubt that a long time dev at hobbyist-centric wearable manufacturers or audio plugin shops has the same sorts of concerns as someone who has specialized in ad delivery for social media sites.
Allowing only people who have served on call or made concrete contributions to multiple RCAs to have input on the software development process is a wonderful idea!
They profited so thoroughly from building the addiction machine that they sought to lobby for legislation that imposed restrictions on internet usage that will actively and permanently add friction to computing and make the internet as a whole less free, just to try to avoid culpability for their actions. They knew what they were building.
It's a grovel-for-investor-dollars site that we've long pretended is for serious technical discussion. Comments should always be filtered through that lens.
My least favorite of that eras Gerald Genta designs. The original Royal Oak is comparatively far more attractive. Both are outdone by the 222 (different designer though), but it's all subjective.
You could at least disable Active Desktop to dethrottle your PC. Meanwhile, my work W11 PC has a second+ delay for explorer right click and there's nothing I can do about it.
You can actually restore the old right-click menu on W11 with some regedit.
Not ideal in any way, and a setting would have been a much better way to toggle this, but it is an option.
I've found that ( at least for me ) that was caused by some entries doing some checks before showing up. Getting a context menu editor and removing some of them can help.
Doesn't matter, it's a shit user experience and Microsoft's fault for putting the onus on the user to fiddle around at that level, rather than putting a hard, very low limit on how long shell extensions can hold up the context menu before they're banned from it.
> rather than putting a hard, very low limit on how long shell extensions can hold up the context menu before they're banned from it.
Do you want the users to blame Microsoft, all Microsoft employees including catering and cleaning workers, and Gates personally? This is how you make the users blame all the before mentioned but not the culprit.
Oh, I'm not trying to defend Microsoft in any way. Everything they make has been going downhill faster and faster.
Just suggesting a possible way to work around it.
This only lasts until dark patterns can be inserted that disrupt the ease of use that agents are currently providing. If I can't force the end user to watch unskippable ads or trick them into spending money on a service they don't need, what are we even doing?
I recall stuff like the Intel icc compiler being expensive and desirable, and things like client access licenses, hardware licenses (to allow using non-trivial amounts of RAM and multi-processing) and support plans for proprietary OSes being rather expensive. Consulting a SCO Unix price sheet from that era, a license that allowed 150 users and up to 32GB of RAM was $10k.
Prices also varied around OS features used. Vendors loved to nickel-and-dime you (separate *-user client licenses for file services, print services, remote access, etc), generally to drive you towards bigger packages that seemed like a better deal.
reply