This week's AW&ST: apparently THAAD will have some ABM (as in anti- *ICBM*) capability.

"Scott Ferrin" wrote in message
...

That depends. How long is THAAD suppose to be in service? Who's to
say China wouldn't try to hit a staging area with an ICBM?

Where? You'd have to posit China lobbing an ICBM at a target being used
by
the US during a third-party operation? I don't think that is realistic
enough to worry about--somewhere in the same category as say, "Protect
against RN Trident attack against US target". As to staging areas where
we
would be operating against the PRC, maybe Australia? But that is in IRBM
range. Anything in their own periphery they could hit with a shorter
range
missile. Which IMO takes you back to the "only US-proper targets have to
be
defended from ICBM".

Hard to say. Let's not forget two things: 1. China isn't the only
country out there of questionable status who is trying to develope
ICBMs (Iran, India, etc.)

So what? I have seen nobody (other than you) postulate any potential ICBM
threat to US forces deployed outside the US; the ICBM threat is being
considered against the US proper.

and 2. THAAD isn't the result of a "we
need terminal defenses against ICBMs for the entire US" but a theater
defense missile *that happens to have some anti-ICBM capability*.

And we do need a defense capability against TBM's for contingency forces--no
argument there. But again, nobody is claiming there is an ICBM threat
against deployed US forces, are they?


snip



http://www.orbital.com/MissileDefens...tors/KEI/index.
html



I don't do the "go to links" bit unless it looks like it is something
worth
bothering with--a sysnopsis of the pertinent info is usually given with
the
link.


Too good for it or does it strain your brain too much? My guess is
you want an abstract with the link so you can not go to it anyway and
still pretend like you did.

No, I just find playing a simple "battle of links", with no abstract, a bit
tedious and basically lazy on the part of the naked-link poster. Now look
here, paisan--I have tried to be reasonably nice to you, to include
acknowledging that I did misinterpret some of your earlier postings in this
thread and apologizing for same. Why don't you make the same effort towards
civility that I have?

Just on this thread there have been
numerous times in which you have missed what has been written or saw a
big paragraph so didn't read it at all. And it shows. My point in
providing those links (if you've read this far) is to enlighten you on
the BPI issue. Where's the harm in going to the link and reading? It
can only help you have a better undertanding of a subject you
apparently take an interest in.

OK, enough is enough. You got an apology, so what the hell else you want is
beyond me. I suggest you read Orvil's post and take heed--he apparently
knows quite a bit more about this than either you or some AvLeak writer (and
more than me as well). You'll note that his conclusions are generally in
linne with what I have been telling you. If you want to conduct further
discussion of topics, be energetic enough to at least indicate what your
links are saying and provide them "for further reference", and get off your
high horse, OK?

Adios.

Brooks

snip

No, I just find playing a simple "battle of links", with no abstract, a bit
tedious and basically lazy on the part of the naked-link poster.


Why the hell would I want to retype the thing when all you have to do
is click once and get the whole thing? And a quick glance at the link
and context should tell you what the thing is going to be about
anyway. If you want to talk laziness "too hard to click on a link"
takes the cake.





Now look
here, paisan--I have tried to be reasonably nice to you, to include
acknowledging that I did misinterpret some of your earlier postings in this
thread and apologizing for same. Why don't you make the same effort towards
civility that I have?


I was. The part that gets irritating is when you go off on some
tangent simply because you didn't bother to read what was written in
the first place. Everybody goofs up sometimes so I cut you some slack
when you went off on the anti-ICBM tangent. Then you turn right
around and go off on the "three or four times the range" tangent and I
have to go and RE-iterrate what I've already written simply because
you didn't take the time to catch it the first time around. Get's old
after a while.





Just on this thread there have been
numerous times in which you have missed what has been written or saw a
big paragraph so didn't read it at all. And it shows. My point in
providing those links (if you've read this far) is to enlighten you on
the BPI issue. Where's the harm in going to the link and reading? It
can only help you have a better undertanding of a subject you
apparently take an interest in.

OK, enough is enough. You got an apology, so what the hell else you want is
beyond me.

I'd be happy if you'd just read the post before haring off on some
tangent. Is that too much to ask?





I suggest you read Orvil's post and take heed--he apparently
knows quite a bit more about this than either you or some AvLeak writer (and
more than me as well). You'll note that his conclusions are generally in
linne with what I have been telling you. If you want to conduct further
discussion of topics, be energetic enough to at least indicate what your
links are saying and provide them "for further reference", and get off your
high horse, OK?

Not on a high horse. I wouldn't expect anybody to write a synopsis of
a link (that's WHY they provided a link). Most people read faster
than they type and I'd rather just click on the link than read a
synopsis and STILL click on the link. If you're too good to click on
a link then by all means continue on in ignorance.

"Scott Ferrin" wrote in message
...


snip


Now look
here, paisan--I have tried to be reasonably nice to you, to include
acknowledging that I did misinterpret some of your earlier postings in
this
thread and apologizing for same. Why don't you make the same effort
towards
civility that I have?


I was. The part that gets irritating is when you go off on some
tangent simply because you didn't bother to read what was written in
the first place. Everybody goofs up sometimes so I cut you some slack
when you went off on the anti-ICBM tangent.

Considering you *started* this thread with the *ICBM * bit (look at the
freakin' subject line you came up with, for gosh sakes), it is not that hard
to imagine someone thinking along those lines.

Then you turn right
around and go off on the "three or four times the range" tangent and I
have to go and RE-iterrate what I've already written simply because
you didn't take the time to catch it the first time around. Get's old
after a while.

Look, you got an apology. be gracious about it, for gosh sakes.

snip

I'd be happy if you'd just read the post before haring off on some
tangent. Is that too much to ask?

Yes. It is when you don't have the common courtesy of telling a guy what the
cite says in some form or other. I have had folks give blind links that
resulted in thirty-page pdf documents. If you are too lazy to wade through
the site and summarize what is there, why should you expect others to do it
for you?


I suggest you read Orvil's post and take heed--he apparently
knows quite a bit more about this than either you or some AvLeak writer
(and
more than me as well). You'll note that his conclusions are generally in
linne with what I have been telling you. If you want to conduct further
discussion of topics, be energetic enough to at least indicate what your
links are saying and provide them "for further reference", and get off
your
high horse, OK?

Not on a high horse. I wouldn't expect anybody to write a synopsis of
a link (that's WHY they provided a link).

That is you, this is me.

Most people read faster
than they type and I'd rather just click on the link than read a
synopsis and STILL click on the link. If you're too good to click on
a link then by all means continue on in ignorance.

Not too good, just don't enjoy the usual
search-through-the-weeds-to-try-and-figure-out-what-the-guy-means when a
blind link is provided. I am truly sorry you don't like that, but I am
doubtful I'll lose any sleep over it.

Brooks

I'd be happy if you'd just read the post before haring off on some
tangent. Is that too much to ask?

Yes. It is when you don't have the common courtesy of telling a guy what the
cite says in some form or other.


I'm not talking about reading the link. I'm talking about reading
what I wrote. If you're going to comment on it I'd think you'd at
least want to know what it is you're commenting on.



I have had folks give blind links that
resulted in thirty-page pdf documents. If you are too lazy to wade through
the site and summarize what is there, why should you expect others to do it
for you?


I suggest you read Orvil's post and take heed--he apparently
knows quite a bit more about this than either you or some AvLeak writer
(and
more than me as well). You'll note that his conclusions are generally in
linne with what I have been telling you. If you want to conduct further
discussion of topics, be energetic enough to at least indicate what your
links are saying and provide them "for further reference", and get off
your
high horse, OK?

Not on a high horse. I wouldn't expect anybody to write a synopsis of
a link (that's WHY they provided a link).

That is you, this is me.

Most people read faster
than they type and I'd rather just click on the link than read a
synopsis and STILL click on the link. If you're too good to click on
a link then by all means continue on in ignorance.

Not too good, just don't enjoy the usual
search-through-the-weeds-to-try-and-figure-out-what-the-guy-means when a
blind link is provided.


In the first case you were talking about problems with BPI and I said
in effect "here's a link to a pdf that discusses the problem in
detail". It wasn't even to support any point, it was just a "hey you
might find this interesting since we're on the subject". I couldn't
find a link so I posted it to my ftp. I'd have thought you be
interested in learning more on the topic.





I am truly sorry you don't like that, but I am
doubtful I'll lose any sleep over it.

I wouldn't think you would. On the other hand there is so much crap
to wade through on the net I'd think you be interested when someone
posts links to a few gold nuggets.