Re: Position of MS regarding the future C++ Standard
William DePalo [MVP VC++] wrote:
"Nemanja Trifunovic" <ntrifunovic@hotmail.com> wrote in message
news:1160273999.316942.288020@e3g2000cwe.googlegroups.com...
William DePalo [MVP VC++] wrote:
what you get is a world in which it is not likely that C++
to be the first choice for new projects.
IMHO, there is still no replacement for C++. People who are
abandoning it for C#/VB/Java/whatever were simply using C++ for
wrong kind of projects (mostly internal or "enterprise" data centric
applications). For system programming, real-time apps, high
performance computing, CAD,... C++ is still the language of choice.
I agree with you. Had I written "most new projects" as I should have,
I think we might be in agreement as I don't think that the types of
applications that you mention amount to most of them.
It depends on who's writing them. A new geometry modelling system,
no matter when you start it, will not really be feasible to write in
C#, trust me. And it's not because C# is incapable of it (although
I just don't know whether it in fact is), it's mostly because those
who are going to write a new geometry modeling system don't give
a damn about C#. They know C and C++ and they're not going to bail
out and switch to a fad language all of a sudden.
As for utilities, plug-ins, web nonsense, ten years ago it was Java,
five years ago it was Python, now it's C#... It will be another one
in five years to talk about, mark my word. I am not saying C# will
vanish into oblivion (with MS backing it's hard to imagine that it
might happen), but it'll become "just one of them", and there will be
something new and shiny and everybody will start asking these questions
again.
Besides "most new projects" is just as nebulous as saying nothing.
Most new projects *I* create (including web nonsense or utilities or
plug-ins) are in C++, simply because I am most comfortable in C++.
On the other hand if Intel can really manage to get 80 core machines
to go mainstream
http://news.com.com/Intel+pledges+80+cores+in+five+years/2100-1006_3-6119618.html
then it will hardly matter how much more performant C++ is over C#.
You'd like to think that, wouldn't you? In fact, applications that
have already been written to work on many CPUs will work just as well,
and the means to create parallel code (and the compilers) will also
develop with the rise of multi-core processors. The number of CPUs
does not really control how fast operations are performed. It all
depends on what operations there are and how many of them there are.
Scalability is essential, but it doesn't matter what language you use,
it matters how you use it.
If multithreading is not used properly, applications written in C#
will simply collect garbage 79 times faster on 80 CPUs than on 1 CPU.
Is there any gain in that? Definitely. Is it substantial?
What I'm afraid the most is that the OS has to be made capable of
handling many CPUs, and if it isn't done right, all the time will be
spent pushing the thread around between processors, like balls in
a pinball machine, and it won't matter what language your program
is written it, they all will work slow (instead of all working at the
same relative speed as before, as they should).
V
--
Please remove capital 'A's when replying by e-mail
I do not respond to top-posted replies, please don't ask