Java review

Good:

- 5 year olds should be able to learn how to make multithreaded applications
- Cross platform
- Great development tools (IDEs and such)
- You don't have to make/download amounts of libraries to develop great and helpful apps, the standard library is huge

Bad:

- Memory hog
- Java programmers: Herppppp Derpppp, internal char array?? nooo, its a string, what internal char array?? what is that
- No function pointers
- No operator overloading
- Everything is a reference, unless you implement Cloneable, sorry, i prefer "&"
- No #define

>>39,44
1. SWT, ha ha ha ha ha ha ha ha, yeah it looks "exactly like a native app" put together by a monkey.  There's a reason no sane developers are using Java on the desktop as of 2010 with the sole exception of... the people writing Eclipse.  It's also a goddamn pain to use, especially compared to Cocoa or .NET.  RIP, Java GUI toolkits.

2. JNI, funny joke.  Take a look at .NET native interface or Haskell FFI to see how it's done in a way that makes actual sense and works the way you want.  Just look at JNI code: you have to write all this messy C glue to stick it together.  What did .NET and Haskell FFI get right that Java got wrong?  In these cases, the glue code is written in Haskell or some .NET language, where it actually makes sense and you don't have to jump through a bunch of hoops just to avoid screwing with the runtime.  In particular, if you need to pass a NUL-terminated string to a C function, you can do that pretty easily in both C# and Haskell without writing any additional C code.

3. It's kind of embarrassing that the Java folks say, "No, don't do operator overloading" and yet they overload the addition operator to concatenate strings.  It doesn't make any sense.  And what about quaternions?  Multivectors?  Versors?  Groups?  These are things for which you'd want to overload operators

>>42
Recommend ibuprofen to control inflammation, and stay at home to avoid infecting others.