Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

Why is Java so popular

Name: If everybody hates Java 2009-03-02 12:02

The introductory programming course at uni teaches Java, but you don't have to take it if you know a programming language. Should I teach myself python over the summer (I already know the basics) and avoid having to learn Java? Or are the haters just people who are scared of object orientation.

Name: Anonymous 2009-03-04 6:48

>Oh boy this should be fun
Prepared for ignorant shit.

>One quirk of the language, all languages have quirks, doesn't affect anything other than making it a little harder to learn, and its already one of the easiest languages to pick up.

It's not a fucking quirk faggot. Is is a basic design flaw. Instead of efficient primitive types and OO types, the fags should have made efficient OO types.

>No need for private interface methods, perhaps you should learn what polymorphism is and when you should use it.

Fucking faggot, I never said private shit head. There are other access modifiers.

>Another non-issue from a Microsoft fanboi.

Having to handle every single exception type separately. You are obviously a fag who doesn't understand how to write good code. Only enterprise programmers tolerate no exceptions because their language makes it fucking a waste of time to deal with them.

>Empty interfaces uses as annotations.
>This isn't a sentence, you fail.

You obviously failed CS 101. Example: the serializable interface has no members. It is only there to mark the class as being able to serialize. Serializable isn't really a fucking interface then is it fucktard. The sole purpose is to indicate semantics. Also known as a fuckin annotation. Annotations are annotation and interfaces are interfaces. In Java, interfaces are incorrectly used as annotation. You fail at the basics.

>The JVM is always shit.
Blatantly false.

>No performance hit for multi-threaded issues unless you specifically request locking/synchronization features.

Allocating a large amount of unused resources is a fucking performance hit faggot.

>Definitely not a nightmare, all handled automatically, the way C# does it causes just as many issues as type-erasure does.

What fucking issues are there with "the way C# does it"? There are none. Unlike faggy Java, the code for generics in .Net is loaded only once in to memory. There is no reason to load the same fucking instructions multiple times for multiple instances like Java. The single set of instructions will work on all fucking instances. Java loads the same instructions for each instance and then adds its own faggy boxing instructions on top of that. C++'s stupid macro templates are even better than Java's awful way of doing this.

>False, the core syntax of the language has hardly changed at all aside from generics.

I didn't say shit about the faggy Java syntax.

>Ummm, ok.
Multiple dispatch, you have no idea what the fuck it is or why it is so fucking terrible that Java only has single dispatch.


>C# is a java clone that happens to have met with some success because it has Microsoft behind it pushing it.  C# is nearly identical to java with the addition of some ugly language hacks.

J# is the Java clone, and it fixes Java by removing tons of depreciated shit and adding features the JVM will never cope with. C# is just what Java wishes it was. But C# is shit because C syntax is fundamentally shit.

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List