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

- No cudders

No function pointers
But you can make a function reference through the use of Reflection.

No operator overloading
No #define
Nothing of value is lost.

I do agree, however, with your char array versus String point, mostly.  "Mostly," in that I believe Java made a poor decision in making the basic String type that is likely to be returned by methods immutable.  Immutability should have been a well-touted feature, not the product.

Another issue is get and set properties, which would solve all the language's cumbersome boxing/un-boxing issues.

All languages have great Dev tools if you know how to google

Most languages can be multi platform unless you make them platform specific

std is bloated

5 year olds that don't understand anything isn't a good thing

ONE WORD THE FORCED .EQUALS OF STRINGS. THREAD OVER.

ONE WORD THE FORCED (COBOL|OOP)IZATION OF CODE. THREAD OVER.

Citing ``cross-platform'' as being an advantage of Java over other programming languages is a great way to advertise you don't actually know any other programming languages.

Good:
It's an ENTERPRISE LEVEL PROFESSIONAL, ROBUST, SCALABLE, CROSS-PLATFORMING AND OBJECT-ORIENTED STRONGLY STATICALLY TYPED PROGRAMMING LANGUAGE.

Memory hog
its a VM language, there is no executable

Java programmers: Herppppp Derpppp, internal char array?? nooo, its a string, what internal char array?? what is that
buffer overflows anyone??

No function pointers
again....ITS A VM LANGUAGE, memory does not directly map to hardware memory

No operator overloading
not something you want in enterprise programming

Everything is a reference, unless you implement Cloneable, sorry, i prefer "&"
everything is Object Oriented, oh and did I mention that its a VM LANGUAGE

No #define
a preprocessor is not part of the compiler and is none to create/harbour very hard to find bugs

in conclusion:
just because you failed at Sepples, dont think that someone is going to turn Java into an idiot-proof Sepples for you

correction:
and is none to create/harbour very hard to find bugs
and its known to create

>>9
IHBT

>>11
IHBT
ITS A VM LANGUAGE.
I think he's not trolling.

Everything is a reference, unless you implement Cloneable, sorry, i prefer "&"
And and its iterators are not cloneable! What the fuck is that?

No operator overloading
not something you want in enterprise programming
IHBT

>>9
Bad:
- It's a VM language

>>1: Nah.

Good, from I LOVE THIS to GOOD:
- Cross platform.
- Batteries included.
- Module system.
- Good VMs available.

Bad, from most annoying to annoying:
- No real functional programming support.
- No first-class functions.
- No decent lambdas.
- Statements and expressions (why this difference, you fucking pieces of FORTRAN shit?).
- No operator overloading. I can overload equals but not +, why, faggots? What's so different between the symbol "add" and the symbol "+"? Stupid idiots, if you had done any Lisp you'd understand.
- Static and explicit typing; shitty generics. As a result, we have nurupo too.
- ENTERPRISE multi-tier mission-critical turnkey professional scalable five-nines HA standard library (and third party libraries); really abhorrent and blasphemously queer and unproductive.
- No native syntax for cudders, dictionaries, etc.
- Formal OO bullshit: interfaces, visibility, final, etc.; keep it simple faggots.
- Java has got no macro system (nor C has a decent one), but then again languages outside Lisp don't.
- Not homoiconic.

>>15
Java does not have a Module system

also try Clojure

Bad:
- BLOAT.

>>15
Batteries included.
Batteries?

No first-class functions
And they are not necessary.

I can overload equals but not +, why, faggots?
If primitives weren't so useful, there's a chance Java would have done away with them and we'd never see a +-/*% again.  Additionally, the only non-primitive that uses any of those operators is String and they only use +. So you basically have a language that is designed to be devoid of your precious primitive datatype operators.  Overloading only add() and not + is a deterrent against people misunderstanding the language.

As a result, we have nurupo too
In an object oriented language of any kind, I argue the concept behind a null pointer error is impossible to completely deprecate away.  Besides, nurupo is cute.

No native syntax for cudders, dictionaries, etc.
We do have native dictionary syntax.  Maybe it's not your "grandfather's holy dictionary syntax," but it is dictionary syntax.
Also, your car and cdr in Java is contained within the class method System.arraycopy().

This thread is full of flaming faggots.

Additionally, the only non-primitive that uses any of those operators is String and they only use +

Irony is strong in that. String should not used + for concatenation. Strings+Concatenation is not group, not field. It's monoid and therefore should use · operator. For the science, bitches.

>>20
I can't type `·' in less than 2 key strokes.

>>15
You are a real `faggot'.

>>15 here

>>16
Not a true module system, but the class dynamic linking is good enough for me. Well, almost anything will be enough as long as it's not the piece of shit multi-step [meta]configuring, compiling, library mongling, linking and the whole toolchains used in C and C++.

Clojure would be my language of choice on the JVM.

>>17
Yes, I said so (standard library ENTERPRISE).

>>18
Batteries included means the standard library is useful to get things done, i.e. unlike C.

First class functions are necessary unless you're some sort of Fortran faggot.

What you call operators are just functions (or "methods"), only they use infix syntax in your language. The fact you can overload some and you cannot overload some others is ridiculous, especially when they have some supposedly claimed to be syntax advantage (or wait, should we trash away infix syntax and use pure M- or S-expressions?). "+" means "add"; and writing a method "add" is not any bit least (or more) confusing than writing a "+" method, and there's nothing to misunderstand from using "+" versus any other kind of method. Nothing you can do will stop idiots from writing idiotic code; every attempt to thwart idiocy tends to bother good programmers when writing good code.

In an object oriented language of any kind, I argue the concept behind a null pointer error is impossible to completely deprecate away.

HIBT? Any decent, dynamically typed object-oriented language doesn't have nurupo. Python doesn't, for example; for special cases you use other, regular values like None (which is an object and has its methods, responds to reflection, etc.).

We do have native dictionary syntax.

What's Java's dictionary syntax?

>>18

http://i.imgur.com/mRmL5.png

>>24
>>uberlol

>>25
>>

>>24
Wow, that text rendering is horrible.  How can you read that shit?

>>27
Are you blind? Are you wearing Glasses? Are you OLD?

Of course you are, ``Faggot''

What is PHPSESSID ?

>>27
I actually sit at the proper distance from the monitor. I don't keep my nose glued to it.

>>29
It's PHP's way to keep track of sessions, and there's nothing wrong with that per se.

Sun just used to push their ENTERPRISE Java Server pages alot, saying it's the OHMYGOD BEST THING EVER.

Now why would Sun use PHP, instead of their OHMYGOD SO AWESOME Java Server Pages?

>>27
It looks like Linux in freetard mode (lol subpixel antialiasing and hinting are patented lol)

Don't worry, you won't ever see such a shit on a real OS.

>>32
Fuck off, ``Faggot''

Bad:
It isn't Dis

>>31
all that means is that someone linked to the page with ?PHPSESSID at the end.

Example:
http://dis.4chan.org/read/prog/1289588972/31?IsRetarded=Yes

>>35
Are you trying to say that Google appended 'PHPSESSID...' to the output?

everyone put on your tinfoil hats, Google is plotting to overthrow... something/someone!

Things Java got right:
- Fast JIT compilation
- Pretty good bytecode language
- Lots of good VM research which will also benefit better languages
- Immutability for Strings. Although it'd be nice if they had some kind of Immutable marker interface and a type system that knew how to handle it LOL JASKAL
- No operator overloading
- No preprocessor

Things Java got wrong:
- Nothing functional
- Forcing programmers to distinguish between scalars and objects, when the language implementors should've worried about this instead. Also == and switch should work on Strings.
- Generics are fucking useless, a compile-time stopgap solution which delivers a lot of complexity and very little benefit. Almost worse than templates in Sepples.
- Standard library is too big
- J2EE and everything around it need to be killed as quickly as possible

>>37
Things Java got right:
- Fast JIT compilation
- Pretty good bytecode language
WHBT

- No operator overloading

How is that a good thing?

Things Java got wrong:
- Generics are fucking useless, a compile-time stopgap solution which delivers a lot of complexity and very little benefit. Almost worse than templates in Sepples.

Generics are indeed useless, in both Java and C#. Templates in C++, however, are not (Unless you're one of those Faggots that don't understand templates).

I think C# (at least on windows cuz honestly who gives a fuck about linux) is shit loads better then java.

1. Java has this shitty UI that looks like something from a 1990's kid movie.
2. C# has built in shit to work with native code. Java trys to act like it it doesn't exist.
3. OPERATOR OVERLOADING OMG /faint

>>39
Nobody uses C# on linux, but it's still better than Java. 'cause Java sucks, of course.