Which part of Java is sexy for you?

Like Ajith, for example, likes threads, Jim loves inner classes, Map is crazy about exceptions... What about you?

YOU, my dear. You are the sexiest

Hey, I don't really like inner classes all that much - I just spend (or spent) a lot of time correcting people's misunderstandings of them. I think anonymous classes are the only inner classes I actually use with any regularity. I do use static member classes fairly often, but of course, you weren't talking about those, right?

Hmmm... I think my favorite thing about Java is all the compile-time and runtime checks that get performed to give you an informative error message when you do something wrong.

Hm. Jim, there is nothing to be ashamed about inner classes. Why to deny your obvious passion to them?

Purists may object your connections with Anonymous inner classes, but we know they are much better than static member ones.

I only disliked the Streams/IO part and now recognizing how important they really r? Anyway, Threads r really excellent to think abt!

------------------
Muhammad Ashikuzzaman (Fahim)
Sun Certified Programmer for the Java� 2 Platform
--When you learn something, learn it by heart!

Streams/IO rock!! at this part of the game they seem to be only concept I can grasp

[This message has been edited by Jim Petersen (edited October 27, 2001).]

Map is crazy about exceptions...

Which part of exceptions do you find particularly sexy? The trying part or the catching part ?

[This message has been edited by Petr Igorovich Kurchatov (edited October 27, 2001).]

Without IO there wouldn't be any network programming in java.
They are also so crucial in servlets and in RMI.
Any way coming to your question Map, EJB attracts me a lot.

regds,
Manjunath

Originally posted by Petr Igorovich Kurchatov:
Which part of exceptions do you find particularly sexy? The trying part or the catching part ? [/B]

finally
But this part is optional...

Originally posted by Mapraputa Is:
finally
But this part is optional...

I am too shocked to say anything. I never suspected that you (of all the people) had a dirty mind.

Originally posted by Manjunath Subramanian:
Any way coming to your question Map, EJB attracts me a lot.

This one is too sophisticated for me. The innuendo is too subtle for my feeble brain

. It went wayyyyyy over my head. Would some clever oracle expain this to me ?
[This message has been edited by Petr Igorovich Kurchatov (edited October 28, 2001).]

I like Swing, couz' it'll keeps remind me to practice my golf swing every day...
[This message has been edited by Stevie Kaligis (edited October 28, 2001).]

Originally posted by Jim Yingst:
Hmmm... I think my favorite thing about Java is all the compile-time and runtime checks that get performed to give you an informative error message when you do something wrong.

Objection. Extreme vulgarity.

I second Mr. Kurchatov's opinion. I should admit, I did not understand what Jim is talking about until I saw this

[This message has been edited by Mapraputa Is (edited October 28, 2001).]

Sorry for confusion. Ersin, I am as

at you as Mr. Kurchatov believes that Jim post is "extreme vulgarity"

Did I add more confusion?

Ersin, I am not

at you at all! Please, do not delete your post! It's

!

JSP has to be the sexiest. servlets used to be the sexiest. more generally i like client/server stuff

Hi all!
Just started MIDlets and they really excite me.

[This message has been edited by Danish Shaukat (edited October 28, 2001).]

Back when I was a single-component guy, Collections rocked my world. Now I spend too much time sampling all of her wares. Last week I was on the tails of castor, this and next week, who knows?

Dave.

Multithreading!

The concept of Classloaders is by far the sexiest feature in Java.

Java's security architecture is pretty cool too.

JAR files are very sexy

I like case errors

Multithreading drool
Classloaders llllallalaaaaallalala
Reflection swoon
Changed my mind already, reflection floats my boat.

Dave

I love JUGs

Introspecting components.

JDBC. I love it when I can *connect* to her (the database).
With JDBC, I can scan her through my select queries, scroll up and down her resultset!, I can update and not to mention run "triggers" on her and have access to her stored procedures.
And when I am done with her, I just close the connection!