There was CAD in the 60s, but somewhere they have archives of paper plans for the moon landings. If it tried to use 60s cad I'd probably think it was just a dra

There was CAD in the 60s, but somewhere they have archives of paper plans for the moon landings. If it tried to use 60s cad I'd probably think it was just a drafting tool with some extras, not like modern cad with solvers, parametric modeling, and 3D views. I don't see how I could make a sketch with constraints on a face back then, modern CAD is slightly slow even on my laptop. Deep learning voice recognition didn't exist in 1999, which is the critical tech that makes Assistant usable, along with the fact that there's now Keep to integrate with and IoT to control. It's true that programmers hate users sometimes, but that's not an issue of tech or skill, that's an issue of programming culture is full of people who would like to go back to tech free simple living and mostly see computers as "bicycles for the mind" rather than "A UI layer for everything manmade we interact with" or "somewhat independent robots". They're in it for the exploration of thought, not because they want paying taxes to be fully automated. But it's the managers and UI designers, and the small percent of programmers that don't hate tech, who actually direct a lot of the experience. Bash is basically incapable of making anything I'd want as a user, because it's not good for managing insane amounts of complexity. It's a tool for directly controlling a computer and using it as a passive tool. Modern languages are tools for essentially using the computer almost as a manager more than an employee, and for creating new models of interaction that the machine is better able to always have your back with. If I want a block to be 35mm tall in total, but there's terraced layers and curves and stuff, I set a constraint. I don't have to worry about the math. I'm not just virtually building stuff like a digital simulation of wood, I'm doing something completely synthetic, that was made up by someone who figured out a model for interacting that puts as much of the hard parts in the CPU instead of in the brain. It can't just be one way "I tell the machine what to do" interaction or the whole thing is limited to my own ability just like paper. It can't be text based or anything else that requires mental translation, or I'd just have an extra task in addition to doing the whole design myself. Modern software's solution is to create a way to think about the task that is inherently something suited for both humans and machines, and then to teach the user that way. Bash is freeform, it says "think how you want then translate it to what machines know". It's great if you want control, not great for computer-led experiences. Sadly it doesn't seem like we are designing many new paradigms of interaction, but I blame lack of interest rather than lack of tech ability. Programmers think about the functionality first, rather than about the interaction model, because they like ideas and dislike software used in the real world when a pencil could have done instead. We do have building codes. Unit tests, memory safe languages, design patterns, DRY, reuse... It's just that lots of devs don't like them.