1. Its easy to code. It is more important to have knowledge of the specific APIs than to actually know how to program and have the mindset of a programmer. Of course, people who don't have that mindset will probably write horrible Java code, but it'll still work, and they'll still get paid.
2. It encourages retarded ENTERPRISE concepts, such as "business logic layers" and 14 extend/implement keywords on a single line.
Name:
Anonymous2007-09-28 20:37 ID:nZt4hEFW
>>5
It's easy to code lowest-common-denominator ZOMG OBJECTS code. But try to do something elegant and you'll be forever mired in a turing tarpit of methods.
Its easy to code.
I disagree. The reason why I don't like Java is that it's a pain in the butt. Okay, great, it's not C++, but it still has a bad case of ugly.
Boilerplate isn't "easy to use". It wavers somewhere between "useless" and "mind-numbing". I have better things to do than to fight a brain-damaged language.
Name:
Anonymous2007-09-28 22:32 ID:64SFczXB
I actually sort of like Java. What I don't like is its memory usage, Swing, the way some common functionality requires creating and messing with a dozen objects, the verbosity of callbacks, and various other small things. But at least it's fairly easy to write portable code in.
If something really fits OO well, just needs some simple imperative code, or banging up a GUI, Java is actually pretty good for it. The libraries kick ass, too.
Name:
Anonymous2007-09-29 3:31 ID:TRB/avD+
/prog/ are still stupid teenagers so they hate java
The libraries kick ass, too.
Actually, the libraries are one of the big beefs I have with Java. They're sprawling messes created by people who have no idea how to design an API. Being filled with ancient half-baked buggy shit doesn't help either.
Sun likes to jump on the newest trend, while not quite completing whatever uglies it was they were working on before.
Name:
Anonymous2007-09-29 4:20 ID:vPHp1CW6
Too many letters.
Name:
Anonymous2007-09-29 8:30 ID:apGKmWpf
66correct quotes99
Name:
Anonymous2007-09-29 8:31 ID:apGKmWpf
66correct quotes99
Name:
Anonymous2007-09-29 8:32 ID:apGKmWpf
66correct quotes99
Name:
Anonymous2007-09-29 8:34 ID:k1Rkyom/
>>22
stop using faggot quotes >>23
stop using faggot quotes >>24
stop using faggot quotes
Its a pain in the butt for a real programmer who would be more productive in a language not full of seemingly useless boilerplate code.
For someone who doesn't have a programmer's mindset, who couldn't code for crap in another language, the pages upon pages of useless templated code are a godsend.
Name:
Anonymous2007-09-30 20:27 ID:LDAECk4U
The names are way too fucking verbose. And CamelCaseIsReallyAnnoying
Name:
Anonymous2007-09-30 21:59 ID:COjmnKcn
>>20
Like what packages? I've heard all these complaints, but everything I've used all over the java libs have been very orthogonal and interoperating.
Name:
Anonymous2007-10-01 11:24 ID:wmqT+8Wg
>>5
>retarded ENTERPRISE concepts, such as "business logic layers"
How is abstraction retarded, you faggot?
Name:
Anonymous2007-10-01 13:00 ID:VXe5ksUu
>>29
Abstraction is not an end in itself. Besides, "business rules" don't exist unless you're using a rules-based language like Prolog.
Abstraction is a good idea if used correctly. If used incorrectly, its worse than no abstraction at all. The above Mythical Business Layer article is a great example.
The current ENTERPRISE ideology these days seems to state that any abstraction is good abstraction, regardless of structure or purpose.
Name:
Anonymous2007-10-01 16:09 ID:2C0eTfMx
>>31
LOL. That article is a complete monster fail. Just read the comments. Pretty much anyone who can spell and isn't stuck in the webmasters behind disagrees with it.