-
Follow
Oops, something didn't work.
Sign In to be begin to follow this thread
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.Getting "follow" information
Start following this thread
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.Removing your "follow"
Setting up your "follow"
Did you know you can
sign up for email notifications?
-
a !
http://search-engines-web.com/
-
W3bbo
Work hard; increase production; prevent accidents, and be happy.
a ! wrote:
They say they take search engine results into account when calculating these graphics.
...that's enough to tell me not to pay any attention to this.
C# has only been around (properly) 3 years now, of course it's going to appear lower than Java or C++
As for VB... I can see it being replaced with XAML in the next 20 years for "proper" RAD work.
-
Maurits
AKA Matthew van Eerde
Maybe I should play with some PHP...
-
I dont think so. VB.net is just as good as C#. Its like coke and pepsi. People just have their own personal preference, but if you go somwhere and they have only coke and you like pepsi, you can still drink coke and be ok. C#, VB.Net, its all the same...
-
I tend to look at VB.net, Managed C++, and J# as porting languages. If you have an application in VB6, C++, or Java, it's slightly easier (but still a lot of work) to port it from that to the managed equivalent.
I forsee C# staying the predominant language for .NET development. C-Omega might also be of use, but only for small subsets of a project.
-
sakisp
C/C++ and a cup of coffee...
Although I never trusted online statistics, it looks that C# dominates .NET development, something that was expected I believe.
Microsoft did they best they can to push .NET development, even though managed applications are slow and bloated when compared to native ones. However, they call it "the future" development framework. For me, if my applications are going to a higher level because of .NET I'd prefer to use a "higher level" language than C++.
In that case C# is much better choice than VB, J# or others. It is fresh, readable, easy to learn and use, and with unsafe pointers gives more control when is necessary. However, I wouldn't say no to some more native support though
I'm sure that C++/CLI will remain the Windows "system" programming language because of its low level nature, but desktop and web application development is a different story. -
Here we go Again!!!!
(This is just me whinging - I have to get it off my chest)
People, build a bridge and get over it. If the language you are developing works for YOU then go ahead and use it.
I get sick of tied of people starting language wars!!!! I also get really P*ssed off when dudes out there try to tell others of what they language they should or shouldn't be using.
Every language has its pros and cons.
Remember, they are our tools of our trade.
-
C#, J#, and VB.NET are functionally equivalent for 90% of your .NET code. I can't say that for certain with C++/CLI since I haven't worked with it, but I would venture to say that it is too.
They are all being supported for the foreseeable future (2005+9 years for standard MS support of developer products).
Thread Closed
This thread is kinda stale and has been closed but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.