L
Lawrence D'Oliveiro
What part of "not written in Java" do you have a problem with?
I don’t. What’s the problem?
What part of "not written in Java" do you have a problem with?
Esmond Pitt said:You posted, I responded. If you don't want responses, don't post.
Lawrence said:Funny, you were the one saying you were fed up with responding, and yet here
you are again, after more punishment.
Lawrence said:For pointing out that your Emperor has no clothes?
I don’t. What’s the problem?
You are a frikkin idiot, Larry. You are a schmuck. Why don't you just
leave the planet, dolt? You are a worthless, pathetic excuse for a human
being with all the intellect of a slime mold.
For being a complete idiot, Larry. You are a putz. You are a despicable
and nasty piece of work. You seem to derive pleasure from being a
complete and utter asshole, a job at which you clearly have an immense
talent. I really hope you wake up to what a complete waste of protoplasm
you actually are, Larry. You have no purpose on this planet and no one
at all likes you, not even your mother. Everyone who knows about you
laughs at you, Larry.
You are a frikkin idiot, ..... You are a schmuck. Why don't you just leave
the planet, dolt? You are a worthless, pathetic excuse for a human being with
all the intellect of a slime mold.
.... ...Whereas I recognize the technical and engineering reasons for requiring
the deeply nested long directory names, I also have to say I agree that
they can be a pain in the butt, on two counts:
You sound like the landlord in my local pub.
I find it interesting that the convention is to use directory
hierarchies (e.g. com/sun/xml/internal) rather than a single directory
(e.g. com.sun.xml.internal). I wonder why they did that. Was it purely
pragmatic (e.g. some architectures might not support multiple dots in
a directory name), or was it to provide the illusion of a hierarchical
package namespace?
I wish Java _did_ provide a hierarchical package structure, e.g. a
package-private member in com.acme would be visible in com.acme.widget.
Whereas I recognize the technical and engineering reasons for requiring
the deeply nested long directory names, I also have to say I agree that
they can be a pain in the butt, on two counts:
1. Typing long directory names or click-click-clicking to deeply-nested
folders is a pain, and will be required if you aren't using an IDE
like NetBeans or Eclipse -- and if you are, you just have the
package/class hierarchy to click-click-click through to get to
particular source files, instead, though at least you'll usually be
working in one small area at a time, and when there are compiler
errors or stack traces you can usually click in an IDE to jump
directly from the message to a suspect line in a source file.
Of course, the one-public-class-per-file thing (which has the same
engineering reasons) then becomes annoying when it leads to a tab
explosion in your editor.
Yeah, I have been on the wrong end of that rant many a time my own self,
laddie.
At least I hardly ever get it from the man in the mirror any more.
I can assure you I never had any of the problems you speak of. Then
again, I'm not developing on a Windows box.
Non sequitur.
3x+rav4gan said:Perhaps you get it from that man too infrequently, Lew.
Indeed, or perhaps still all too frequently. How about you, O Anonymous
One? Does the man without the courage to post his name feel completely
unembarrassed by his own behavior?
Not quite.
I haz shellz.
Yes.
Though you're hardly one to talk when you are posting using only a small part
of your own name, Lew.
Lew Bloch, you troll.
Now go crawl back under your rock, maggot.
Plonk, BTW.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.