is c# going to stay / take over c++ ?
-
-
just a curious question , with having coded in vb for a while i want to be sure that c# isn't gonna be here today , gone tommorrow. switch(twinsOnWay) { case ("twins on the way"): MessageBox.Show("for mr and mrs dynamic","twins on the way"); break;
I think it's fairly safe to say that C# is certainly going to be around for the long haul... over here in the UK a massive number of companies that I'm aware of are making large investments in moves to .NET and thankfully C#... (unfortunately one or two consultancy reports indicating that the move from VB to VB.NET would be considerably less painful than to C# has really hurt the .NET name in some areas...) I did actually think that MS were going to start moving VC++ into retirement but it looks like they are still investing heavilly in Managed C++ so it's nothing but choice for developers... (MS obviously hedging bets!! :) ) If you look at the roadmap for C# the future looks quite compelling... next stop... generics!!! :) :) ;) :cool: Shaun
-
just a curious question , with having coded in vb for a while i want to be sure that c# isn't gonna be here today , gone tommorrow. switch(twinsOnWay) { case ("twins on the way"): MessageBox.Show("for mr and mrs dynamic","twins on the way"); break;
I am sure we will see VB/Java/C# for ages to come. C# however is the only standardized language of the three langauges. As a C++ programmer, moving to C# is fairly natural. It reminds me of my last major jump in lanaguages in 80's when I moved from Assembler to C. Moving to C++ was not much of a transition. In the early days of C, it seemed bulky and kind of slow since compared to Assembler but it added a lot of RAD development to our world at the time. For many things C was fine, but for some things you had to revert to Assembler where absolute speed was required. At the time, OS's were built with Assembler. Now they are usually built in mostly C/C++. With C#, there is a lot of changes from C++, and it can seem slow for somethings and may require MC++. But in the future more things will move that direction and speed will increase as will computer speed. One thing I am waiting to see happen, since C# is a standard, is a form of C# scripting added to browsers. May not have the entire .NET frameworks, but could still work well to handle client side code. I get turned off having to resort to Javascript when I code client side. I am sure that no person can say that it will remain for sure or not, but the same goes for any language. During the last six months, I have heavily used C# and enjoy it as a language. There are a few things I would change but I can live with them. C# gives you much of the ease that VB programmers have been used to for years without the stigma of being BASIC. As for as .NET is concerned though, it does not matter much which language you use, but the job listings for C# programmers are usually higher. Rocky Moore <><
-
just a curious question , with having coded in vb for a while i want to be sure that c# isn't gonna be here today , gone tommorrow. switch(twinsOnWay) { case ("twins on the way"): MessageBox.Show("for mr and mrs dynamic","twins on the way"); break;
switch(twinsOnWay) { case ("twins on the way"): MessageBox.Show("for mr and mrs dynamic","twins on the way"); break;--->Syntax Error - line4 ( missing } )
There are only 10 types of people in this world....those that understand binary, and those that do not.
-
switch(twinsOnWay) { case ("twins on the way"): MessageBox.Show("for mr and mrs dynamic","twins on the way"); break;--->Syntax Error - line4 ( missing } )
There are only 10 types of people in this world....those that understand binary, and those that do not.