4,454 karma · joined September 23, 2010
Again, maybe I'm a sore loser, but it definitely feels like a lot of software is becoming increasingly hostile to me, personally because it's being optimized for a presumed average user. I have no beef with this average user and it's globally a totally correct optimization to make stuff work for them as well as possible, but it means that software makes tradeoffs that are inconvenient for me personally.
The most common use case is streamlined by removing options that clutter up the settings menu or banishing the buttons I press a lot into some tertiary menu, or niche features I rely on become unsupported and then get removed (of course with forced auto-updates, because the average user experience is improved by them) to free up developer bandwidth for the core features. And then I end up using a different off-brand window manager with the serial numbers filed off that barely works in general, but works for my specific 'workflow" exactly like I want it.
Of course, at the same time I also benefit from general improvements targeting the average user. It's only about the tradeoffs.
The "free with ads" service will "outcompete" by immediately being in basically-infinite debt, right? Is that really still "competing"?
I guess we can't have nice things because what those websites are traditionally good at isn't profitable. I can't really be surprised that monetizing tumblr proves challenging, when it seems to consist of like half starving artists, half anti-capitalist shitposters, and half young adults talking about fanfic. I remember monetizing blogging being a running joke on the site over a decade ago, and I can't imagine it's gotten easier with, you know, the economic situation impacting those demographics.
Now it just means someone paid some amount of money. They're "verified" in the sense of like verifying the email address you used to sign up with to an olde timey web forum, and maybe that you're probably not an absolutely minimum effort spam/scam bot. However the "verified" checkmark is still basically useless because it doesn't verify an identity or credentials anymore, and it's easy enough for bad actors to get the checkmark to then impersonate some brand or website or whatever, and have their posts get privileged by The Algorithm.
So, previously "verified" status was useful for people to be able to tell that the posts they're reading are really from who they think they're from. Now, "verified" status means that bad actors and bad posters get their posts boosted ahead of normal posts, so the replies to any mildly popular thread are going to be full of attempted scams and tepid takes. It's become completely useless for its original purpose and makes content discovery worse.
Of course it still sucked when some tool decided I needed to update dependencies which all lived on regular Github, but at least our deployment stuff etc still worked.
Worst case you have more data points to draw conclusions from. Status page red, works for me? Hmm, maybe that's why the engineers in the other office are goofing off on Slack. Status page green, I get HTTP 500s? Guess I can't do this thing but maybe other parts of the app still work?
Internal metrics: Healthy
External status check: Healthy
Did ops announce an incident: No
Backend API latency: )`'-.,_)`'-.,_)`'-.,_)`'-.,_)`'-.,_)`'-.,_)`'-.,_)`'-.,_
And when there's disagreement between indicators I can draw my own conclusions.I guess in reality the very existence of a status page is a tenuous compromise between engineers wanting to be helpful towards external engineers, and business interests who would prefer to sweep things under various rugs as much as possible ("what's the point of a website whose entire point is to tell the world that we're currently fucking up?").
The success of this website is that it doesn't have to be successful along the same metrics as substack or reddit or tiktok to fulfill its purpose.
I figure it's more that there's no one-size-fits-all thing. "Normally", that isn't a problem, because you just switch to another program that suits your preferences/takes good care of your brainworms. It just becomes frustrating when companies tie their services to uncustomizable programs (like for instance a website) narrowly designed for their archetypical user persona.
... but beyond that there has to be a better way to do this?? Surely this particular thing has been designed to death a million times. I think with Google Docs, I get to assume everything is saved all the time, so this is the default state that doesn't need to take up space on the screen. In the risky situation where I alt-f4 before the save call returned success or whatever, I get the javascript popup telling me stuff wasn't saved and I can cancel and wait a few seconds. In the other risky situation where the save call just keeps failing for a prolonged amount of time (because my wifi died, usually), I think it says that somewhere in the UI, and it seems like a good enough justification to grab attention to me.
I don't think apps/sites are getting worse about this, it's that they're getting better at optimizing for users who aren't me. It's probably just deeply frustrating/alienating to have to use products that you're not the target audience for (and that's increasingly almost all products).
(To be clear this isn't meant as derision of the 'statistically average user', it's perfectly justified that not everything is built to suit me, the protagonist of reality.)
If you do a thing, find out it isn't what you wanted, and then undo it, while at the same some other process is observing the mutated state, that's potentially a much trickier mental model. If you undo a configuration change and in the meantime a background process has acted on the new configuration, how do you roll that back? Rewinding the timeline is one thing, but maybe throwing out all the work that happened with the wrong configuration is even worse than the status quo.
From the top of my head I am thinking about accidentally changing retention windows or bash history max size where the data loss is super indirect and you'd have to hunt down the undo button for a completely different process, or changing a log format so you end up with a file that's mixed json and plain text logs.
(Of course, "try" presumably applying the changes in a completely synthetic way after the fact could be its entire own can of worms in a very dynamic system if there's a risk changes are applied in the wrong order or skipping some atomicity dance.)
My impression is that exceptions become more and more prevalent as (app?) development practices diverge from the workflow that distros have spent decades optimizing their processes for (ie., apps are developed with package managers that don't map well to distro packaging).
There's a lot of "it's not that hard"s in that post. Of course we all prefer software that just works after being installed with the distro package manager. I don't want to install a container runtime to run grep or netcat or whatever. Meanwhile app developers have to balance their own priorities, it gets complicated, and, I guess increasingly often, "ship X feature to Flatpak users" wins over "make the lives of users/maintainers of Fedora easier". It's just another tradeoff, and sometimes the cost of making do with one version of a library isn't worth it.