3 ms·
> Is this something that we, the developers and designers and UX specialists, should seek to change? Well, it's something we already have changed. The earliest
by smoldesu 6y ago
> Is this something that we, the developers and designers and UX specialists, should seek to change?
Well, it's something we already have changed. The earliest models of computing were based around manipulating data with different tools that had express purposes. We eventually implemented abstraction over those tools, though, and the real question is how far we want to take that abstraction. As the author suggests, most users treat software like a black box that can either work or fail. The more variables we introduce to the situation, the more likely it is for the end user to screw things up. Somewhere along the line an engineer somewhere said "fuck it", and we decided to abstract the data away from the user to limit their liability. Our penance for that decision is the "magic" conjecture most people come to when they see Bluetooth or ML in action: the user is no longer drunk or high, they're outright dead. Most people (and programs) can't differentiate between a client-side and a server-side error, so how should they be able to tell the difference between a bad question and a bad answer?
In direct response to your question, my answer is "I don't know". My greatest hope is that one day our data will be interoperable through a number of user shells that offer a toolkit to the user rather than a toybox. It's very wishful thinking, but I don't know how we're going to progress the status quo of personal computing without that flexibility. The state of social media these days is almost universally considered miserable (see: doomscrolling), so something's gotta give. It's not going to be paid "super follows", and it's not going to be another short-form video sharing app. The next step in empowering the user is giving them the tools to rise up against developers, so I suppose the answer to "should we fix this" is rather personal.