Why are all Java programs overengineered?
>>54500775
hello world is like 20 lines of code, wtf
Because java is shit that only retards use.
>>54500775
I like that he's just running htop.
Because no one actually uses java, not even java developers
>>54500794
It's enterprise ready
>>54500946
That's not true. He's obviously running his IDE. You can tell from the red CPU bars.
>>54500775
J2EE
>>54501198
KEK
>>54500775
Because OOP is terrible and leads to terrible designs.
>>54500775
Overengineering is the fault of the programmer, not the language.
>>54500775
why is he running htop?
>>54500775
BEANS FACTORY
it's funny how Go is more maintainable than java
>>54503380
>>54501256
You can write good OOP programs, you just have to be good at programming
>>54501256
>>54503417
OOP is a tool
You have to be a good programmer (read EXPERIENCED) to know where to apply it
>>54503658
What's the alternative to OOP for big projects?
>>54503780
GOTO segfault
>>54500794
It's 5 lines
public class HelloWorld {
public static void main(String [] args) {
System.out.println("Hello world");
}
}
>>54503346
why not?
Because java is organized and designed after decades of being used in massively overengineered projects.
It is, in every possible way, obscenely verbose. It's part of the reason C# has been exploding in popularity: It has all the ease of use and modularity of Java but is actually condensed and organized by a sane person.
>>54500775
Because Java is a language for industry. It was intended to take the large-application advantages of OOP, give it cross-platform abilities, and remove the difficulty presented by C/C++'s resource management.
Along with Java came best practices and patterns. Why? Partly to reduce the amount of time wasted by new programmers in discovering the same flawed systems that more experienced programmers already tried, but mostly to make programmers into interchangeable cogs in a system.
The over-engineering of Java is a direct consequence of the industry's attempt to make you into a replaceable cog.
