In early 2000 Java promised to be write once, everywhere. By the time it was between Windows and Sun.
20 years later we have finally reached this point for business applications, be them in Java, Python, PHP or some other VM based SDK.
The mainstream development future is in Lambdas and other such containerised technologies. If you can run Docker or similar "home" you can also deploy. Our DevOps models have radically changed and not sure if he realises this.
> In early 2000 Java promised to be write once, everywhere.
Latter half of 1990's, by my recollection. The history is well-documented. JDK 1.0 shipped in 1996, and that's when The Java Language Specification was first published also. The "write once, run anywhere" started to be heard soon after.
When I left C++ for managed languages, operating systems and C didn't stop being relevant; what stopped being relevant for me was the grotesque extensions of C dialect desperately trying to be a high level, managed language in increasingly irrational ways.
C++ is still the best tool when my managed languages need some extra native help.
Maybe it will be eventually replaced by Rust one day on my toolbox, but surely not for C.
I left that in 1993, only using it instead of C++ when university professors required me to do so, and on my first job (until they also moved into C++/C#).
20 years later we have finally reached this point for business applications, be them in Java, Python, PHP or some other VM based SDK.
The mainstream development future is in Lambdas and other such containerised technologies. If you can run Docker or similar "home" you can also deploy. Our DevOps models have radically changed and not sure if he realises this.