This thread is made of java-manager/consultant/spamspeak and brainblock.
>>40
I see some words. Some of them are in english even. Good! After failing several synapses, I finally managed to read it through. And then I LOL'ed - for Sage's sake
Name:
Anonymous2006-06-29 6:09
I'm >>40
How do I successfully trolled all of you by copypasting text from Java web sights?
Name:
Anonymous2006-06-29 19:19 (sage)
Enterprise JavaSpam increased the amount of spam we could produce by 200%!
Name:
Anonymous2006-07-01 2:08 (sage)
System.out.println("WRYYYYYYYYYYYYYYYYYYYY");
Name:
Anonymous2006-07-01 19:05
>EVERY Java programmer has to know?
That you should search for useful libraries/frameworks before starting any project. Students tend to pick up the bad habit of writing everything themselves when that never actually happens in the real world of Java programming.
Name:
Anonymous2006-07-01 19:49 (sage)
>>47
In the real world of Java programming, you glue crap that doesn't with other crap together to get an even bigger pile of shit. The wonderful insights you get at being both a manager and programmer at a pro-Java company. It doesn't matter they're rewriting shit, the only difference is they wasted time producing a new pile of shit instead of wasting time making different piles of shit work into a bigger one.
Name:
Anonymous2006-07-01 20:00
Java's so bad that I'm often tempted to reinvent the wheel. I can quite sympathise with those students.
Of course, now I refuse to touch the language. Problem solved.
Name:
Anonymous2006-07-01 20:32
>>49
I'm enterprising my progamming knowledge into any language but Java
Name:
Anonymous2006-07-02 11:06
Reinventing the wheel is often quicker and easier than learning how to use a generic factory factory to build generic wheel factories which must then be subclassed to provide a wheel that does sorta what you want it to.
Java is made of fail and forcing OO down your throat even when something else would work better.
Name:
Anonymous2006-07-02 22:23 (sage)
OO is nice.
Java sucks because it's garbage collected (explicit destruction FTW).
Name:
Anonymous2006-07-03 0:05
OO is nice for some things, but designing a language specifically to make non-OO programming difficult and then telling people to use it for EVERYTHING is very wrong.
Name:
Anonymous2006-07-03 0:23
So OO and Structured programming going together is normal?
>>56
Of course. Use the best tool for every job. I'd also say add lists, hashes and some functional programming when it's more comfortable too.
Modern, good languages, unlike Java, support several different paradigms and don't assrape you with one of them.
Name:
Anonymous2006-07-03 13:06
OO is nice.
GC is nice.
Java does both badly.
Smalltalk is superior.
Name:
Anonymous2006-07-03 19:23
Relying on garbage collection makes me feel dirty.
Name:
Anonymous2006-07-03 19:46
Code should consist of what it's supposed to do, not all the memory management necessary to make it do it. That shit should be automatic.
Name:
Anonymous2006-07-04 5:36
If you're doing memory management and not working in some operating system component or performance-critical application, library or driver, you're doing it wrong.
Name:
Anonymous2006-07-04 8:06
If your application is well-designed, memory management will be minimal and will only appear in logical places. It makes code more readable by showing when you're done with some object (which the programmer always knows better than the GC).
Name:
Anonymous2006-07-04 8:54 (sage)
Java does both badly.
That sums it up.
Name:
Anonymous2006-07-04 10:23 (sage)
Java bad.
Summed it up for real this time.
Name:
Anonymous2006-07-05 10:05
>>62
Still obsessed with that? Most of us (at least the ones who staretd with low-level languages) had a "OMG, garbage collectors are a waste of resources; I know better and it's really simple" stage, until we go tired of wasting our time dealing with data structures for the 23412354th time and then realized we can concentrate on what we need to get done if we use a garbage collector.
I really don't think that there's a one single thing that every programmer needs to know. I mean, there are a plethora of things that are obviously necessary to be a good coder...
Name:
Anonymous2006-07-06 7:37 (sage)
>>67
Of course, but if there is any one thing that EVERY programmer needs to know in addition to other things, it's >>64
Name:
Anonymous2006-07-06 23:45 (sage)
I had to learn Java for a warmup assignment in a class, even though the rest of the class was in C++. Had to make a multiplayer game with the www.gamegardens.com framework. What I learned about Java is that it makes me want to kill myself and I never want to see it again.