|
 I agree with you.
Most of people participating in vote must be working with .NET or excited with .NET framework.
What ever b the result on this site... C++ will remain most important language in future.
Anand
The chosen one...
|
|
|
|
|
I think importance of C++ or C# are more a matter of domains where they would be of better use rather than raw power or that stuff.
It seems C++ is targetted towards the development of device-drivers and high-performance apps, whereas C# more towards the usual to advanced Windows APPs and of course with ASP.NET.
There's no doubt that C# lets u develop apps much simpler and faster than C++. So how could C++ be important here? And of course vice versa 
Happy programming,
Rakesh Rajan
|
|
|
|
|
Rakesh Rajan wrote:
There's no doubt that C# lets u develop apps much simpler and faster than C++.
 Isn't there?
|
|
|
|
|
In many respects, I don't think so...do u?
Rakesh Rajan
|
|
|
|
|
I use both C++ and C#, and generally I don't see much diferrence in productivity. In fact, I would say that C++ tends to be somewhat more productive language, especially when it comes to resource handling. And operator == in C# is definitelly brain damaged. In Java it means checking for identity, in C++ it is checking for equality, but in C# it can be any of those. You need to look at the documentation to find out.
One thing I really like about C# is the explicit control of method overriding (new and override keywords).
|
|
|
|
|
It seems you are talking in the microscopic sense. I was talking about the productivity in the outset - the big picture. When you think about general applications, using C# to code is usually faster than developing it in C++. The case is different in different domains though.
Rakesh Rajan
|
|
|
|
|
Rakesh Rajan wrote:
It seems C++ is targetted towards the development of device-drivers and high-performance apps, whereas C# more towards the usual to advanced Windows APPs and of course with ASP.NET.
I have found that most of the time, an experienced C++ programmer can create a much better "advanced Windows App" than a similarly experienced C# programmer. While that is a huge over-generalization, it does seem to follow that less experienced programmers are initially drawn to VB and C# because of their simplicity. However, you eventually run into a wall in those languages (e.g. when memory management becomes an important issue) and C++ becomes the way to go.
All 3 languages have their uses though.
"If you decide to become a software engineer, you are signing up to have a 1/2" piece of silicon tell you exactly how stupid you really are for 8 hours a day, 5 days a week"
|
|
|
|
|
anandparanjpe wrote:
Most of people participating in vote must be working with .NET or excited with .NET framework
That, or they have never had to develope an application what initially runs in Windows, but also has to be protable to Mac or *Nix.
"If you decide to become a software engineer, you are signing up to have a 1/2" piece of silicon tell you exactly how stupid you really are for 8 hours a day, 5 days a week"
|
|
|
|
|
Hehe, C# ahead with one vote !!
|
|
|
|
|
And here I was thinking I was being outrageously funny...
cheers,
Chris Maunder
|
|
|
|
|
Yes, Perl can be ugly, it is not as glamarous as many other languages... but for a general purpose scripting language (for Windows or any other OS), it is the way to go.
We don't distribute any Perl apps, but we do use them in-house quite frequently.
It sure beats programming with batch files. 
If your nose runs and your feet smell, then you're built upside down.
|
|
|
|
|
|
I know its not cool but SQL is at the top of the employers most wanted list 
|
|
|
|
|
More generally spoken, they want profound Database knowledge.
And no one seems to care for .NET here. But maybe that is because I am into scientific computing, not 'lifestyle'-computing.
Who is 'General Failure'? And why is he reading my harddisk?!?
|
|
|
|
|
It's just a file format with a lot of hype;)
|
|
|
|
|
Anonymous wrote:
It's just a file format with a lot of hype
Just like C#! 
The magic to 'sharp'en C++ is in the CLR - not in the language.
Who is 'General Failure'? And why is he reading my harddisk?!?
|
|
|
|
|
You're right, although it is a format that is quite flexible and useful, so I marked it anyway.
If your nose runs and your feet smell, then you're built upside down.
|
|
|
|
|
That would make XML very interesting.
|
|
|
|
|
That is not completely correct. Since they lumped pretty much anything that uses XML under that umbrella, that includes WSH, which is a scripting language (well, actually a set of scripting languages).
If you want to get down to it, what is the difference between an XML file and a C++ source file? They are both text files that follow a certain syntax.
"If you decide to become a software engineer, you are signing up to have a 1/2" piece of silicon tell you exactly how stupid you really are for 8 hours a day, 5 days a week"
|
|
|
|
|
The overall technology is pretty interesting though, even if some of the implementation borders on the silly.
|
|
|
|
|
It may be a file format alright...but hype? I think there is solid use in XML.
|
|
|
|
|
In Microsoft's opinion the future is in managed code, in whatever flavor your prefer. Here's a quote from the Longhorn FAQ at WinSuperSite[^]:
Q: So what's changing from a developer's standpoint?
A: In the technology generations leading up to Longhorn, Microsoft has been moving to a .NET-based managed code environment, and the Longhorn generation will finally mark a clean split with the Win32 APIs of the past. That is, Win32 will be in maintenance mode, and all new development will occur with managed .NET APIs.
|
|
|
|
|
If you look at the free text comments you will see many people have a different opinion than MS about "managed code"
|
|
|
|
|
I guess it all comes down to what platform(s) you want to write code for.
If you're part of the crowd that likes to make your money from developing for Windows, the writing certainly seems to be on the proverbial wall, and the decision seems to have been made for you already.
Time will tell of course, and if the direction were to change it wouldn't be the first backflip we've seen 
|
|
|
|
|
Furty wrote:
If you're part of the crowd that likes to make your money from developing for Windows, the writing certainly seems to be on the proverbial wall, and the decision seems to have been made for you already.
Assuming Longhorn ever ships...  
Yes, it does seem like managed code will be essential for Longhorn and future OSes... but right now, 100% of the customer base is *not* running Longhorn, since it isn't out yet.
If your nose runs and your feet smell, then you're built upside down.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
