Re: Up to date MFC Book
- From: "Tom Serface" <tserface@xxxxxxx>
- Date: Thu, 31 Aug 2006 11:09:01 -0700
Well... the C# team seems to be doing a better job of marketing and
propaganda. You mentioned that C# is easier (it is in fact) so if you just
want to do .NET you would likely use it because more of the Visual Studio
supports it and it's easier to get started and use. So I think the argument
is more around how many totally .NET applications are possible.
If you could use C# for .NET or native (as you suggested) then I think there
would be question.
Tom
"Daniel James" <wastebasket@xxxxxxxxxxxxxxxx> wrote in message
news:VA.00000ed3.6763736b@xxxxxxxxxxxxxxxxxxx
In article news:<1156946072.593052.264530@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
My take: you need C++ to write unmanaged code. I don't buy the hype that
most code can/should be managed. I see a good argument for maybe 30% of
applications to be managed, and most of those should be in Java for
portability reasons. Another (finger in the air) 20%-40% could equally
well
be managed or native, and the rest (for one reason or another) are better
as native code.
So, your typical programmer needs to be able to write C++ to do the tasks
that are best done native. As he can use that language to write the CLI
stuff too -- and as C++/CLI is the most powerful of the managed languages
he will certainly not be losing out -- why would he have any need to learn
anything else?
The answer, of course, is that he'll need Java to write code that has to
run in a JVM (e.g. to fit into those ghastly Java-based application
architectures that the Java world keeps spawning), he'll need something
like Python (or maybe perl, or ...) for the things that those languages do
better ... but he won't need C#.
The bottom line is that C# is a nice little language, but there's nothing
you can do in C# that you can't do at least as well in other languages,
and
there are times when you can't use C# because you have to write code that
can't assume the presence of a CLI.
If I could write a program in C# and compile it to generate either native
or managed (CLI) code by changing a combobox in the IDE I would see some
point in C#. If I could also compile it to generate standard Java bytecode
that will run in Sun's JVM that would be nice. At the moment it does
nothing for me apart from being easier to learn than something I already
know how to use and that does the job better.
Cheers,
Daniel.
.
- Follow-Ups:
- Re: Up to date MFC Book
- From: Ajay Kalra
- Re: Up to date MFC Book
- References:
- Up to date MFC Book
- From: AB
- Re: Up to date MFC Book
- From: David Wilkinson
- Re: Up to date MFC Book
- From: Ajay Kalra
- Re: Up to date MFC Book
- From: David Ching
- Re: Up to date MFC Book
- From: Ajay Kalra
- Re: Up to date MFC Book
- From: David Ching
- Re: Up to date MFC Book
- From: Tom Serface
- Re: Up to date MFC Book
- From: David Ching
- Re: Up to date MFC Book
- From: Ajay Kalra
- Re: Up to date MFC Book
- From: Ajay Kalra
- Re: Up to date MFC Book
- From: Daniel James
- Up to date MFC Book
- Prev by Date: Re: We are all arguing about the wrong thing!!! (was: Should Globally Needed Objects be Members in Main Frame, Application, or be Global? )
- Next by Date: Re: Should Globally Needed Objects be Members in Main Frame, Application, or be Global?
- Previous by thread: Re: Up to date MFC Book
- Next by thread: Re: Up to date MFC Book
- Index(es):
Relevant Pages
|
Loading