C/C++ unmanaged constructs a bad choice?

According to James Gosling, who pioneered Java, yes.

http://asia.cnet.com/enterprise/infrastructure/0,39035812,39216563,00.htm

I will say he has a valid point and that has been the mean and ways application failure, hacked, system hang occurs... but with the .Net Managed Environment this has changed tremendously and i believe people at microsoft did infact address this.

I do agree, but I think the unmanaged portion will take more time...

Having an unmanaged portion in the C++ environment will complicate matters... its either you go managed or unmanaged cos having both in a project will just let loose all the devils of errors and of course beauty sleep and others....

hmmm.... but then again, if you only keep manged or unmanaged, you are not really utilizing what .net is offering you...
as far as the error is concerned, you gotta be carefull right?

i agree whole heartedly... but then again another question will come to mind are we living in a perfect world with all the time we want... another thing will be not about being careful but more of communication... project teams are sometimes big and during integration is when all the problems come by... do you have any time left by then? just a though

Time my friend, is one thing no developer has...
But that is not the point, in the first place if you choose to work with unmanaged code, its a choice you make. So then you know that you need extra time, cause the developers are of course going to take longer time working with unmanaged code. What I am trying to establish is : if you chose to work with unmanaged code, you should already be aware of the time factor.
Cheers!

Well i will agree with your statements but then again you did highlight developer do not have time... and to factor in the use of unmanaged code with a managed application for an n-tier system will basically be time consuming whether you cater time to it or not... look at the current circumstances, you have to develop projects using Java, .Net and MFC alone sometimes the schedule for the release of the project just get extended... let alone using unmanaged code in the project...
cheers

IMHO, we are goin around in circles...
Lets conclude this...
Correct me if I am wrong...

Whatever the case, if ther is a need of unmanaged code
There is a price to pay.

Right?

well exactly... i think we both know the risk that we are indulging in... anyway it was a nice discussion thou

Yup.. there is no end to it...