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.
Technology Stocks : Cymer (CYMI)

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: LzzrdKing who wrote (3719)9/28/1997 10:05:00 PM
From: TheSpecialist   of 25960
 
The point about DUV not being around forever is true. However
it will be around for quite some time, with tremendous growth
over the next several years. After DUV (248nm) is 193nm, another
generation of DUV. 193nm will replace 248nm the same way that
248nm is replacing 365nm (i-line) today, the same way that 365nm
replaced 428nm (g-line), and so on. I have been in this industry
long enough to know how and when technologies will change.
I also understand how the semi's and their suppliers interact and
compete.

INFRAS is dead wrong when they say that the industry wants
DESPERATELY to get past DUV. The industry is not going to
throw away a technology just as they are beginning to
implement it after years of R&D. The reason they are aggresively pursuing the post 193nm generation (Next
Generation Lithography) is because of their understanding of
the amount of R&D AND time that is required to make one (or more technologies) viable for insertion 7+ years from now.

It is not your statements of published material that causes you to
get flamed on this thread. It is your editorializing and your "holier
than thou" attitude that gets you flamed. If you wish to use only
one source for your investing that is fine. The investors on this
thread are here to uncover and listen to all information, even
yours. Just state it...don't preach it.

TS

BTW - Most of us here are investors, not traders.
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext