No, that's what normal business applications looked like in the 90s. This is what web pages looked like in the 90s.

It makes me suspicious that you weren't around in the 90s. That's not what web application UIs looked like.

I've tried. For some reason, now my car won't start.

About 40,000 people die in car accidents every year, in the US alone. It's one of those things that I keep pointing out because people keep seeming to fail to realize how many people that is. When people say, "We can't have solar power because it'll kill a thousand birds!" or "We can't have freedom (i.e. NSA spying and CIA torture is ok!) because otherwise we might have another 9/11, which killed a thousands of people!"

40,000 people die every year due to car accidents. Nobody is talking about giving up cars.

Before we allow AI on the road, we'll need to have some kind of regulation on how the AI works, and who has what level of liability. This is a debate that will need to happen, and laws will need to be made. For example, if an avoidable crash occurs due to a fault in the AI, I would assume that the manufacturer would have some level of liability. It doesn't make sense to put that responsibility on a human passenger who was using the car as directed. On the other hand, if the same crash is caused by tampering performed by the owner of the car, then it seems that the owner would be liable.

As far as I know, even these simple laws don't explicitly exist yet.

Normal cars also make it easier to commit terrorist acts and other crimes. So what? I mean, yes, let's consider whether we want to take special safeguards and regulations regarding AI cars, but this shouldn't be something to go crazy worrying about.

Yes, I agree completely. I do kind of hate coming back from vacation to a huge inbox, but on the other hand, I do things like emailing someone saying, "I know you're on vacation and I don't want you to do anything now, but I know I'll forget if I don't send this now. When you get back..."

Oh, I wouldn't be surprised at all. I've worked in IT support for a couple of decades now, and I know exactly how that goes.

There are two things about that though. First, it's a bit of a fringe case. You have to consider the question, "How many people of that sort are in my target audience?" If the answer is "a lot", then you should think about writing documentation for them specifically, and find a way separate it out from other documentation for those who are more comfortable using a computer. Otherwise, people who know what they're doing are going to be frustrated searching through 100 pages of inane instructions to find actual information.

Second, people like that often also won't read the documentation. If they do, they won't understand it, or else won't feel confident that they understand it. At a certain point, you have to either provide those people with IT support personnel that they can call (your older relative has you). At the very least, you need to provide them with simple step-by-step instructions that never vary, where they don't even need to understand what they're doing. Like "In order to do [x], press the power button on your computer to turn it on (it's located in the top-right-hand corner of the box under your desk). It will flash some things on the screen for a while. Wait for it to ask for a password, and then type 'hunter2'. Wait 2 minutes. Then find the blue "E" on your screen, with "Internet Explorer" written under it. It will be the third little picture on the screen, all the way to the left..."

I've had to write instructions like that before, and some people need it to be that simple. But obviously a web application vendor can't take responsibility for that level of instruction. Even something like Dropbox, which is designed to be extremely simple, has to assume some level of competency.

He gave us both the word "crap" and "ballcock"? What a guy.

See there, you're talking about *actually* unwanted programs. If a program is potentially unwanted, then it's not currently unwanted. It just might become unwanted in the future.

It's not the features that you stare at with no idea what they do that cause a problem. As you say, a quick look at the manual can help to sort that out (though it does add to the overall cognitive load). It's all the potentially subtle things that you don't even realise are features and so never look up and don't realise that, contrary to first inspection, the code is actually doing something subtly different to what you expect.

I think you mean something like "unwittingly installed program" then. You could knowingly install an application and still retain the potential for not-wanting it.

I know it's started becoming a common terminology, but I don't really like the terms "Potentially Unwanted Program" and "Potentially Unwanted Application". Any program/application is *potentially* unwanted. Whenever someone starts talking about PUP/PUA, I can never figure out where they're drawing the line.

I'm not aware of Odoo, so I'm only speaking generally, but generally speaking, having a simple/intuitive product does *reduce* the need to documentation. For example, I don't need documentation to tell me that I can open a Word document by going to "File", selecting "Open", and then going to "Computer", "Browse"....

Now, come to think of it, the process for even something as simple as that has gotten needlessly complicated. WTF is Microsoft doing these days?

Back on subject, yeah, if you open files by going to an obvious menu button that says, "Open File...", then I don't think you really need to document that. You only need to document the features that aren't completely blindingly obvious.

The need for documentation can also be reduced by having a good help/support system. If you have a procedure for doing something unusual and complicated that's undocumented, you had better have someone standing by that I can call/chat/email who can help me out. And even still, that stuff should be documented at least well enough that you can train your support staff.

If you don't have good support and something is not completely obvious, then yes, it should be documented.

Well originally, the US was set up to be closer to this. The difference was, instead of being "picked from a lottery", they were elected in small elections all over the country. It was (is) called the Electoral College. Senators for each state also used to be elected by the state's legislature, rather than by popular vote.

Unfortunately (or perhaps fortunately, depending on your viewpoint), we changed all that to move closer to a direct democracy. People get angry about the Electoral College every once in a while and propose getting rid of it and moving to a direct popular vote, but I don't see that happening anytime soon.

I think this is tied somewhat to the issue of the issue of self-driving cars. Part of the problem with flying cars is the question of, who do we trust to fly them? What's the process of licensing people to drive/pilot these things? Do we trust people not to fly over protected airspace? Do we trust people not to fly into buildings? Along with everything else, driving/piloting a vehicle designed both for driving and flying might very well be more complicated than learning to drive and learning to fly combined.

However, if you can have self-driving cars, and you can make a self-flying driving car (including take-off and landing), then you could have the whole thing controlled by a computer guided system, adhering to restrictions to traffic and air traffic. Along with everything else, you could have restrictions that say, "When you're in NYC, the car knows that it needs to drive because airspace is restricted. Once you drive X miles outside the city, you can take to the air along certain restricted routes, following certain procedures." All of that could be controlled with computers, disallowing various kinds of abuses.

Of course, that assumes that we have sufficient systems for safe autonomous driving/flight. It also assumes that everything is coded well enough to prevent people from hacking the car to allow them to break the rules. It also assumed that people will be ok with being restricted and tracked. Finally, it assumes that, when you've put all these restrictions in place, you haven't made the idea so un-fun that people don't want a flying car anymore.