rysiek ✅ is a user on mastodon.social. You can follow them or interact with them if you have an account anywhere in the fediverse. If you don't, you can sign up here.

so I'm reading through the Mac Plus manual, and I'm struck by how alien some of these concepts must have been.

They have multiple pages devoted to how to use a mouse.

On the other hand, the OS has a very consistent workflow and design language and methodology. They can explain complicated, abstract concepts in simple ways because they are consistent.

Apple of 1985 did a lot of things worth admiring (and a lot of shit, but that's another story.)

This kind of well produced, very well written, very thorough software manual, one that doesn't make assumptions about what knowledge you're bringing to the table, is sorely missing from modern software.

I'd pay $20-30 to have manuals like this for many pieces of modern software.

(OTOH, those pieces of software would need to be more well designed, and more consistent in their design language, in order for a manual like this to be at all useful.)

It's revealing of the state of the industry at large that software manuals don't exist anymore, and that documentation is often an afterthought.

It's elitist, IMO.

The books that I got with my Atari 400 (hand me downs in the mid nineties, I can't comment on what shipped with the system originally) were super thurrough, and also written at novices.

They didn't assume people knew about computers (because no one did) and they didn't assume people would just 'figure it out' (because no one would.)

I had all manner of books on computers when I was a kid, and very few of them were hard to understand, even as an 8 year old.

I had books from the 80s written at an elementary or middle school level that better explained complex computing concepts than the textbooks I had to study in college.

I'm not kidding. I lead a study group, because I was basically sleeping through the classes and some of my friends were struggling. So I lead a study group to help out.

I brought in these books I had read when I was a kid, xeroxed off copies of the relevant illustrations and explanations for everyone.

The effect this had on the average grades in the class was so pronounced that my teacher asked me what I had done.

I brought him the same books, and he looked shocked.

You know that slightly wistful, vaguely watery look people get in their eyes when something they care about is done really well, but in a way that makes a lot of effort they expend useless?

It was that. He started hunting down vintage copies online, and incorporating them in to his lectures.

And, like, I get that I was a weird kid. I read reference books and maps and stuff for fun.

But I struggled through the bland and boring books because I'd seen how useful reference books could be, and I'd learned that mostly through these very thoughtful books on computers.

When I get settled in to the new house, I'll pull out those books and take some pictures. I imagine many of them are on Archive.org already.

My point is (and has been, for weeks) that we are ignoring the users.

We used to care about users. We wanted users to adopt hardware and software. We wanted users to be productive and secure.

Vendors cared about the user experience.

Now, everything is user hostile. Everything is trying to screw you, or spy on you, or just isn't engineered with your safety in mind.

We, you and I, have a chance to fix this. We, you and I, can rebuild and repair.

We can:
- Make user friendly (not user hostile) devices and software
- Write documentation
- Refuse to buy tech that *we* can render safe to use, but that the average user can't
- Support people that do things correctly financially whenever possible.

We can 'vote with our dollar'

We can write to our congresscritters about the DMCA (a law that is wielded by the likes of Lexmark and John Deere and Microsoft to keep their devices user hostile by rendering it illegal to install your own software.)

We can normalize the idea that reading documentation is sometimes required, and in the process, help folks bridge the gap in computer literacy.

I own several kindles, for example. I've bought them all used, so I don't feel bad about owning them, but I wouldn't buy one new.

I purchase cheap used android devices, root them, and give them to friends in need. I write documentation. I build dumb simple scripts to automate common computer tasks for people that need to perform those tasks, and only those tasks, and are uninterested in performing any other tasks.

And yeah, part of this goes back to #deletefacebook

Facebook is user hostile.

But it's larger than that.

Modern Windows, MacOS, and even Ubuntu have some user hostile behaviors baked in.

And in the FOSS world the only real successful business model has been "give away the software, sell the support" which means that their is an incentive in FOSS to keep the documentation technical and complicated.

RTFM culture is user hostile behavior.

@ajroach42 I mostly agree with that, however there are some instances of "community supported" business models. Like (wait for it) Mastodon.

I think the problem is also partially on the side of users -- we're all so deeply conditioned to not pay for stuff unless we have to that it's hard for community-driven projects to get enough monetary support from the community itself.

This has to change, and is slowly changing. Which is good.

Point is, it's not just on the projects, but on all of us.

rysiek ✅ @rysiek

@ajroach42 in other words: we need to learn to financially support projects that are important to us even if they have no way of twisting our arm to make us pay.

That way they will not have to twist our arm to get enough financial support to survive and thrive.

We're all in this together.

· Web · 3 · 5