Joe said:
Twisted, are you seriously still convinced that somebody is
manipulating Google Groups to limit your postings? It's not just your
total posts; as I've said before, it is the short time period between
them that causes it to be blocked.
That's ridiculous. Of course there is a short time period between them
-- people tend to read and post news in a single hourlong session (or
thereabouts) rather than trickle their usenet activity out over a full
day. So it's a perfectly normal activity pattern to do a whole lot of
fetches and posts at intervals as short as five minutes (posts) or <1
(fetches) for a few tens of minutes, and then nothing for as much as 24
hours, and so on and so forth. If that activity pattern triggered a
block, then
a) It would mean the people running the show at Google were complete
retards and
b) I'd encounter this far, far more often.
It's frustrating, yes, but still better than paying
for separate Usenet access, isn't it?
Except that I *am* paying for separate Usenet access; I'm just not
*receiving* it anymore. As I'm sure I mentioned earlier in the thread,
my ISP stopped providing usenet access (to any of its customers,
apparently nationwide) but they did not reduce my monthly bill at all,
which means that whatever portion of that covered their costs is now
just going straight into their pockets.
Needless to say, the ISP in question is on its way out, but the shoddy
state of north american broadband competition means that this actually
requires I move. At this time, I've had one showing and zero offers on
my house, so the move may not happen for a few months yet ...
(No, I didn't actually put my house up for sale just because by ISP did
something shoddy. There are a number of factors prompting the decision.
ISP misbehavior is one of the less significant of these factors.)
You claim that your message was immediately met with hostility and "Why
the hell are you doing it THAT way!?" type responses, and challenges to
your IQ. Let's review.
Hasn't that already been done -- by *me*? Or did you not read that part
of the thread? (I'm not surprised.)
* You posted your original question, asking about bundling the
application icon with the app.
* Larry Barowski replied, suggesting the usual method of
Class.getResource()
I shall note here that by the time he did so I was already done
implementing the method I'd discovered via further googling, and busily
tweaking the icon itself in photoshop after a successful test.
* Mark Rafn replied, clarifying the notion of a URL, and further
expanded on the example of Class.getResource().
To which I'd later point out that I'd meant "internet URL" by "URL" and
was covering file URLs under "file on the local hard drive" separately.
I might have been clearer in the original post on that point; likewise
he might have read a bit more before jumping on that use of "URL",
whereupon my separate treatment (and non-neglecting) of the local
storage option would have become apparent to him.
So far, you've had two helpful replies without a hint of sarcasm or
hostility.
No; that only started once I posted what I'd discovered using google to
the thread.
* Patricia Shanahan simply asked what the advantage was of your
approach you decided on over the getResource approach.
She had already misunderstood something if I'd decided on the approach
used "over" anything; at the time I implemented it, I had yet to become
aware of the other. See above. However, misunderstanding isn't a
serious crime. (It has been known to lead up to one mind you.)
The implication that she found "my" approach (which is another
misunderstanding; I don't claim any originality but conversely the
approach I encountered and ended up using carries the cachet of having
been described by a Sun developer-oriented article, a point that seems
to be ignored by everyone else in this sorry mess of a debate) to be
questionable. At this point, there's at least a hint of trouble
brewing.
* Mark Rafn again reiterated the getResource approach. While he did
capitalize MUCH (Wouldn't it be MUCH easier), it's clear this was for
emphasis on the word 'much' and not to be yelling at you.
Despite which, the implication is "Why the ****?!" and therefore "Are
you a moron?!". At this point, the downhill slide is apparent. And my
own posts prior to that point appear to be without serious fault. If
there was a flaw, it was a clarity issue surrounding the use of "URL"
in the very first post, and *that* did *not* explode into a huge
controversy.
Your reply to Patricia has a very condescending tone:
I do?
She asked "what are the advantages..." and I answered that question by
listing five possible reasons. Was this somehow wrong? (If you think
so, I shall make it clear that I don't agree.)
In fact, this is another potential point of hypocrisy. Someone earlier
criticized me for *not* answering tangential-at-best questions put to
me here. Now here is an example of where I *do* answer one, and you
criticize me for *that*. Apparently if I do I'll be attacked for it,
and if I don't I'll be attacked for that, so it's already too late for
me to avoid being attacked the moment someone *asks* a tangential
question.
That can't be right...at least, not "right" in the sense of "just"...
However, a couple of messages later, Andrew Thompson replied again,
with more helpful advice for you,
about finding the user's home directory, mentions Java Web Start, and
touches a bit on the advantage
of getResource
Fascinating, although the user's home directory is clearly
inappropriate for an application icon.
[snip some]
I'm not claiming that every response was hostile. Only some of them
were, but that just goes to show that an otherwise useful debate,
discussion, or entire forum can end up dominated by the behavior of a
few loudmouths (and anyone that ends up forced to keep rebutting the
loudmouths).
This is, curiously, reminiscent of a related claim about Usenet: that
about 50% of the traffic is now composed of spam and the cancels
negating the spam. OTOH, most users don't see either, whereas here the
insults and their "cancels" drown pretty much everything else out.
Next up, I enter the fray. I made a small, admittedly sarcastic post
asking why you think learning Ant is a bad thing.
http://groups-beta.google.com/group/comp.lang.java.programmer/msg/5f66b204966b0e8d
Which presupposed that I even did.
I think one recurring misunderstanding is to misinterpret "not now" as
"not ever". So if I suggest that I either have too much on my plate or
no use for it at the present time, some people take that incorrectly to
mean that I have rejected it outright as *ever* being useful, and since
such a thing *would* itself be incorrect, they then launch all
missiles. Unfortunately, at a target that's actually innocent...
Daniel Pitts replies. He is challenging your approach a bit, but it
does not come across as hostile or sarcastic. States his opinion that
"It Just Works(tm)" is a bad approach to software...
Well, you know what they say about opinions. Like assholes, everyone's
got one and they all stink.
I'd agree if what he'd objected to was an attitude of "it doesn't
matter if you don't understand why, so long as it works", but what I'd
actually expressed was more along the lines of "a surefire method is
superior to something that only probably works". In the specific
instance in question, the icon "works" with the same certainty that a
string constant works, rather than depending on some kind of delicate
I/O operation to succeed. The icon might therefore be best off where it
is, or externalized under the same circumstances where a string
constant might be, such as if it's to be localizable or customizable in
some other way. I doubt that there's anything to object to in that
assessment.
I don't recall responding specifically to that, but in case anyone's
wondering, I think it likely that the array constant would be bulkier
in the source code. Up to three digits per character in the string
constant makes it potentially 3x the size, more since every byte value
would be comma-separated vs. characters grouped into strings. So say 4x
the size.
You complain about bashing - which hasn't happened, just disagreement
and **GASP** discussion of why your approach might not be best.
Really? First of all, if I mentioned bashing it was because there was
bashing. (Unless, of course, you mean to call me a liar, on top of
everything else that I've been called lately.) Certainly at the time I
felt rather put-upon, having suddenly found that I was expected to
either defend my code or rewrite it (or at least defend it or look
foolish). I chose to defend it, and, frustratingly, instead of my
reasons being accepted and everyone getting on with their lives, people
just continued to question me and imply that I was doing something
wrong or stupid!
In the posting in question, also, I was referring to two additional
threads that contained (at the time) even more overt
bashings-in-progress. (Only one of those is still active, though it
remains hostile at this time, and in the meantime this thread rapidly
worsened until it became easily the worst of the bunch for "bashing".)
A pattern in which everything I said was being subjected to unasked-for
and unwanted scrutiny and criticism had become evident, and it was that
whole pattern that I attacked as being rude, unreasonable, and
unsolicited. Just because I ask some narrowly-specific question about a
particular small aspect of a project does NOT mean that I welcome a
broad-based inquest into every detail of the entire project in
question, or that I am looking for some sort of general critical
review; I'd like the specific question answered and that's all and I'd
like any judgmentalism checked at the goddam door first; just answer
the question in a neutral manner please.
Unfortunately, this wish of mine, expressed then and expressed again
just now, is clearly either lost on just about everyone participating
in the "debate" here or actually being wilfully disregarded. The former
suggests a serious reading comprehension problem (which is odd --
surely anyone who considers himself or herself qualified to answer
Java-related questions here must have the necessary skills in that area
to read the API documentation, at least?) and the latter is outright
disrespectful and rude.
The thing that has most "set me off" though has certainly been the
posts that have let a judgmental opinion shine through rather than
maintaining a professionally neutral demeanor.
You mention the replies are universally hostile-toned. There were maybe
two replies up to this point that had a sarcastic or mildly hostile
intent. Not universally.
Up to that point there had been many that were judgmental. Most of the
truly hostile toned posts had arisen in two other threads up to that
point, but as I'm sure you'll agree, this one swiftly followed them
into the depths of the selfsame toilet-bowl. And went on to set some
sort of goddam record.
And of course from there, it gets ugly very quickly. Twisted, you are
the one that turned this thread into an ugly argument, so don't try to
put the blame on the rest of us.
Incorrect. I responded harshly to a continued pattern of judgmental
responses, and to outright bashing happening in two other threads.
Perhaps I should have separately responded in those threads and kept it
in proportion, in each of the threads, to the worst offense committed
in that particular one. Perhaps. Regardless, as soon as the first
judgmental attitude was permitted to show through in someone's posting,
it was already too late. As long as a neutral discussion of *software
code* was going on, things were peachy. As soon as it became about a
*person* and whether or not they were <insert judgment here>, it became
impossible to avoid a serious argument, since that person then
necessarily had to entrench their position and rebut the judgmental
content in followups, lest they otherwise be perceived as accepting the
wrongful judgments.
[Large amount of quoted material with no further original material
snipped]