So I agree with your point but I think you missed the point of the previous point. However, correctness isn't limited to: "Did I adhere exactly to the mathematical definition of what I am trying to implement?"(in your case a shadow). But did my code match my intention or specification. No one will write a game, see it chug along at 2 frames and say "Well, at least that shadows nice..." Part of the spec, whether it is written or not, is the expectation that a game will run at a playable frame rate. Therefore, the slow implementation does not conform to a programmer's definition of correctness.
Instead, I think the previous poster was implying that some tools and languages have subtle behavior that make it easy to make mistakes.
E.g. If my language allows things like (where = is assignment):
if (debug = true) { //do some expensive computation, or some other thing that was not intended }
Then it might lead to fewer correct programs.

And sorry, I misread the username. I realize you did not complain about imports. You did however compare Java to assembler. Which seems to imply that you haven't written either (incidentally I have also written assembler but only in school for an old Motorola 8080 so it doesn't really count).

Lol, I have used many programming languages. I started on C/C++ and used those professionally. I have used Java and Scala professionally. I have used Python, Perl, and PHP professionally. God knows how many languages I have tinkered with. I use C# to program in Unity for fun. I wrote OCaml in school, do I need to go on. My work is literally on research into programming languages. Yes, Java's standard library has plenty of rough edges (compare Scala's collections to Java's, its mind blowing how much easier to use they are). Every time I use Python's it feels worse.

To start: Intellij. Not Eclipse. Second, you complained about imports. It's a non-issue. They can both be added and hidden by the IDE and usually take only a cursory verification. Furthermore, you can customize the way in which imports are added and how they are suggested. It's such a trivial thing it makes me feel like you've never done modern development.

The elitism here is staggering. Are you kidding me? The entirety of Computer Science and Software Engineering is enormous. You're trying to boil it down to systems/performance.

Yes because again, we are all Facebook looking to reduce rack space. You took a series of problems that require high performance and generalized it to ALL of computing. It's just not true. I know plenty of people who write programs that run on asymmetric hardware. There are plenty of times a JIT or AOT compiling is going to outperform anyone but an expert. Yes, there is a performance trade-off that is often made for using a GC language that you recoup in reduced engineering effort. It is much easier to get programs right with what is usually an inconsequential performance penalty. Yes, there can be LARGE penalties for misunderstanding your underlying hardware, OS, etc... But that's, again, not unique to Java. But in practice, there are plenty of companies with large scale Java systems that perform well and can be modified much more quickly by worrying about the business logic at hand rather than the hardware underneath.

Do you use an IDE? Easy to set auto imports correctly and then just hit Alt-Enter to import it's suggestion (or flip through the list of a correct one). If Java feels like you're writing assembler than you're doing it wrong.

You're right. Java is massively successful because it's unproductive. That's why it's one of the most used languages on the planet because people can't get things done.

Oh and I forgot, isn't the OpenJDK implementation mostly Java with Native calls where necessary?

Sounds like poor management, poor hiring, and poor technical leads.

Yes somehow without firm understanding of these concepts people can code a huge amount of useful code. Many programs require no knowledge of any of this. I cut my teeth on C/C++ but now do mostly Java. Is it easy to write poorly performing code in Java? Sure but the same is true for every language. If you need to squeeze top performance out of something, you hire a person who knows how to write performant code. This is true in ANY language. Day to day, we would waste an enormous amount of time if this is what our programmers were thinking about.

Because that is something I will ever have to do. I mean, if only there were stable, well-made OS's out there. We could all stop worrying about this. But I get it, having an understanding of what the OS does is important and your right. CS grads and serious programmers should have real-world and academic experience writing low level code. That said, you're blowing it way out of proportion.

Hmm, I seem to recall a concept called abstraction. It let's you get work done without having to worry about inconsequential details. However, being close to hardware is not nearly as important as it use to be. We're not all writing graphics drivers here or writing a realtime mobile apps.

"Whoosh," is the sound you hear over your head. What's the point of Java? Why do people use it vs why do people use C/C++ vs. Java? Sometimes you need to be closer to hardware. This is one of those times. Therefore, you wouldn't use Java.