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.
Gold/Mining/Energy : T.ITE: iTech Capital (TSE)

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: marcos who wrote (1137)10/15/1999 3:28:00 PM
From: Crazy Canuck  Read Replies (2) of 5053
 
>>i guess you saw Swami's link ... oooo scarey eh -<<

This post is not directed at you Marcos. It is just me venting.

In my opinion this is about as scary as going to the dentist to get a tooth filled!!! Dammit, it is something that has to be done so we should just get it over with!

Let's let the market finish this correction and bounce off of either 9400 or 9600 - and then we can get on with life. In my opinion we needed this correction. Corrections (no matter how violent) are part of how the market functions. We have listening to the "when will it hit" babble for months on end now. I am soooo tired of listening to everyone expressing nervousness and fear.

If an investor has their money in good stocks, with great fundamentals, then I believe that they really don't have anything to worry about. By the way, did you notice the strength in volume of JDX (98,500 shares traded today so far) with a solid price gain. Compare this stock's performance to many of the other more widely known stocks that have been crucified today. Early next week the trend will no doubt continue, but when the dust clears it should be clear sailing again - for the investors who hold stock in good companies.

I can tell you that I will be sleeping well this weekend after seeing how well JDX held up today. Granted the day is not over yet, but it sure was encouraging.

Crazy Canuk
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext