SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Strategies & Market Trends : Gorilla and King Portfolio Candidates

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: mauser96 who wrote (27455)7/7/2000 10:42:02 PM
From: DownSouth  Read Replies (1) of 54805
 
Lucius and shamsee, ya'll just made two posts that sum up the QCOM situation very nicely.

I have kept up with the threads today (and most every other day) in an effort to understand what the heck is going on. My conclusion is that today's early morning "news release" was either a half truth formulated for FUD, or the product of a naive mind. Take a look at this article from a Korean newspaper for a more factual report on what is going on in SK:
(Thanks to tekflyer for posting this on the News Only thread.)

english.joins.com

Here are my conclusions (not from this article, but from all I have been able to glean from SI lately):

1. What we are seeing is a multinational battle for national and corporate position in the coming wireless explosion (3G).
2. The price of QCOM stock will remain very volatile for at least the next 4 months and may remain so for the next 18 months.
3. If QCOM can form the right alliances, blink only at the most opportune times, and defend its IPR outside and in the courts, QCOM will eventually thrive and the value of the company will grow in the coming decade similarly to INTC or CSCO in the decade of the 90's.
4. The FUD, haze, smoke and fire will remain confusing until the alliances and blinking by governments and corporations result in a relatively stable balance of power.
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext