> Most devs I know avoid it like the plague, and only use it to maintain legacy codebases or get CS qualifications. All the customers I have worked with since

> Most devs I know avoid it like the plague, and only use it to maintain legacy codebases or get CS qualifications. All the customers I have worked with since I became a consultant 4 years ago (and a couple of the best companies I worked with in the decade before) used Java or .Net. More specifically one of them was dotnet core and the rest are JVM. And I'm happy with that. Java and Maven means I can focus on the problem and not on all the crazy things people who think they are too clever to use Java do. I mean I have seen a couple of Abstract Factories in Java, but I haven't seen anyone avoiding putting passwords in the source code by writing things like this: rot13(<rot13password>) That is stuff I have found in Python code by the one consultant who was to smart to use Java or .Net.