Comments by "" (@diadetediotedio6918) on "Java for the Haters in 100 Seconds" video.

The most happy moment in my job was when I stopped using Java and started using kotlin instead, I never touched the language but just because it is not Java I felt instantly better writting on it than writting the tons of javaplate code
13
@spliterash And what? My problem was never with JVM, my problem was with Java itself, the language syntax sounds like an elder lich trying to make cakes. Also, Kotlin compiles to native code too
5
@lawrencedoliveiro9104 You can specify why they are wrong tho. If your "right answer" is " That’s why “new” is needed: because you can have a class or data field that has the same name as a method, in the same scope .", then just look at Kotlin, it doesn't use the "new" keyword and still can differentiate between these cases, the new keyword is not strictly a requirement for Java to work if they didn't want that way, because the naming patterns of Java are just very clear, types uses PascalCase and methods camelCase.
2
@lawrencedoliveiro9104 New is good for semantical understanding, it separates constructors from methods saying explicitly you want to have a "new instance of type T" instead just "calling method". So writting new Logger() seems more obvious from what it does than just using Logger(), at leas IMHO. Kotlin on other hand go with your thinkering and just uses the T() syntax, for better or worse I think both have their cases
1
 @lawrencedoliveiro9104 Java objects aren't aways on the heap, not defending but Java has something called scape analysis
1