The only way I can see this happening is if we simulated beings are considered to have minimal consciousness, like we view ants in our simulation. Therefore, our (simulated) pain and suffering is immaterial to the simulators.
Most of us have escaped the constraints imposed by Hollerith cards.
In Java, in addition to writing a functional program, you have to build an extensive type system. That's half the work, and yet it's not really programming... it's documentation and runtime error prevention.
Same thing is going on right now with TypeScript. Are custom types worth the bother? I'm on the fence. For quick and dirty stuff, types get in the way. For more complex applications, types can be very very useful (and also have a very very difficult inheritance chain to follow). Thats why, when programming in Java, you really need an IDE to do the bookkeeping for you.
(I really liked Groovy, where I could mix and match typed and untyped approaches within the same application. Too bad about all that reflection though.)
I'm Generation Jones
I was a long time C++/Java/Groovy programmer, who by circumstance wound up writing JavaScript for browsers and NodeJS.
When I'm not forced to use objects, I tend not to use them except where abstraction/encapsulation simplifies maintenance. Looking back on it now, there was a huge amount of time wasted in designing and maintaining types and interfaces, and refactoring of same.
Generics in Java are/were a disaster: I have seen casts used to break the declarations, because the declarations were wrong. And it was all to solve the RARE problem of inserting/reading the wrong type from a collection!
Types are not so important that you need to be forced to use them. Sometimes a little slop in the system is allowable, depending on whether you're writing website code or financial.
As the financial sector has shown, there's more money to be made shuffling virtual paper around than there is in actually making useful things.
The universe was created yesterday. All your memories are implanted. You are a brain in a bottle.
I have worked for decades, for companies tiny and huge. I have a github account. I write articles about cutting edge techs. You give me some abstract problem to solve that has no bearing on what I do every day. You don't need me, I don't need you.
My first reaction is "Why?" to these types of questions. I work for a small company now: they have things that need to be done. Coding in large enterprises tends to be "coding in the small", with little creativity required and everything spelled out for you.
To be fair, Java is not as bad as COBOL. But I would rather be writing apps than designing elaborate type systems.
If I poke it, does it not bleed?
Anything other than machine instructions is not a programming language.
Wuss.
npm modules?
But not as dead as SNOBOL
Waste not, get your budget cut next year.
