Think of it as evolution in action.
I'm wondering what's the temperature in the Phlegethon.
Thou shalt not make non-destructive copies of electrons as they pass over the holy Internet.
Great Hitler's Ghost, he's back.
Laws have to change as technology makes them obsolete. That's not to say that people who have an interest in living in the past won't kick, scream and bribe their congress critters, but eventually they'll lose.
From Heinlein's Life-Line;
There has grown up in the minds of certain groups in this country the notion that because a man or corporation has made a profit out of the public for a number of years, the government and the courts are charged with the duty of guaranteeing such profit in the future, even in the face of changing circumstances and contrary to public interest. This strange doctrine is not supported by statute or common law. Neither individuals nor corporations have any right to come into court and ask that the clock of history be stopped, or turned back.
As soon as they automate politics. That's when politicians will ban it.
Now that we know the NSA can intercept and decrypt any message, doesn't it also mean that they can change the message to whatever they want, re-encrypt it, and pull it out in a court of law as evidence?
If they do, or even if they don't, I can now say they did, and they can't prove they didn't.
Have them debug a z/OS StandAlone dump with IPCS. That'll get their juices flowing.
Don't have one. Been asking for years.
I had two people, one got taken away from me, the other wanted a different career path and moved into a Management position. Currently there's no one assigned to me, and the only other person in the Data Center who can do some of what I do will be retiring next year.
It takes several years of training and hands on experience to become a somewhat useful Systems Programmer.
I'm one of those geezers who's planning to retire in the next 5-10 years, currently with 34 years of zOS Systems Programmer experience behind me. if you want my job you're going to need to know;
How the operating system works
What to do when it doesn't
Data Encryption and security.
Obscure business logic.
Knowing what to do, and more importantly why you MUST do it.
Knowing what NOT to do, and why it's a really bad idea.
Knowing what rules to make.
Knowing when to break the rules, and when not to.
Knowing when to tell Management they're an idiot, and they accept it because of your track record on being right.
Do you get the picture?
I have an entire box of unpunched punch cards that I'm willing to sell, for the right price.
I'm a zOS Systems Programmer and one of my most used resources is the IBM-MAIN mailing list. If you can find one in your field that you can contribute to, your name will become a searchable item.
The average non-technical user couldn't give a rats ass which OS they're using. They want their apps, they want it simple, they don't want to mess with the guts of the computer.