(Part II continued) 
 
OK, so maybe the client will buy this logic and decide to stay w/ something 
like 'C' but that only eleiminates the problems "C++" might cause - it does 
nothing for the hardware problems w/ Intel processors.
 
BTW, if you have a source for the information you supplied in your msg, I 
sure would like to have it.  I might need it to pursuade a client. :) 
Unfortunately , I do not remember my source.  :(
Further, where are the benefits to people like me - consultants who usually 
do this kind of work.  Where is the demand for follow-on work that makes 
getting involved in RT apps worth while?  
 
What do people like me do if the next RT apps demand is 2 years after the end 
of the first one?  Employers now-a-days virtually still demand - even with 
the un-employment rate being less than 5% in general and around 3% in the 
Boston Metro arena?
OPPS, how crass of me to want to stay employed.  :)
 
Where's the 'beef'. :)
 
Thanks to you stimulating my ass'y language juices - almost dried up over the 
last ten years or so - I think I will be even more cautious in regard to 
taking on such contracts.  
 
Aside:  Two years ago Hugh's Communication couldn't find anyone who could 
still do machine language and was delighted that they found me; but not 
delighted enough to hire me at the very high rates I demanded.  I couldn't 
have cared less.  Most companies are business 
'jokes' IMHO.  They can't afford the people who have the job skills 
they demand.  So they do without - what else.  It seems to me that out of 
every 100 job requirements being given to contract firms - according to the 
recruiters I talk to in the NE Region - only five (5) percent are being 
filled.  The companies can't find the people they claim they need at the 
prices they can afford.  It seems the only real jobs out there that companies 
can afford are the for people with 3 - 5 years of experience.  
 
In RT embedded apps job requirements the same is true based on my experience. 
 
 
I think I will stick w/ my database and network stuff - unless or until Cobol 
and RPG start paying $150/hour for the Y2K problem - or more.  Don't laugh 
yet.  Some recruiters told me that Cobol and RPG programmers are demanding 
$150 - 200/hour.  Of course they aren't getting it - *yet*.  But as the Y2K 
problem looms close and the corp execs can now *see* that inpentrable wall - 
the year 2000 - who knows what these desperate decison makers(I say this with 
tongue in cheek) will do - besides 'crash and burn'.  Recruiters tell me the 
Cobol pgmers are ROFL when they hear that they, the recruiters, are not 
seeing any demand - yet.
 
Con't give up your daytime C++ job just yet but who wouldn't want to make 
more than the $45 - $55/hour rate common now for C++ pgmers - hmmmm?  By my 
calculations, based on 1986 dollars, has the buying 
power of $22.50 - 27.50/hour.
 
Sorry I got carried away a bit.  Thanks again for the warning.
Regards, -= Lou =-
---
---------------