Re: Future of MFC?
- From: Ajay Kalra <ajaykalra@xxxxxxxxx>
- Date: Sat, 22 Sep 2007 10:53:34 -0700
On Sep 22, 1:03 pm, Daniel James <wastebas...@xxxxxxxxxxxxxxxx> wrote:
In article
<news:355E980A-39B9-4F69-ADDA-A7438BE701FA@xxxxxxxxxxxxx>, Ajay
Kalra wrote:
For regular development, unless you have legacy code, there is no
reason to not use .Net.
You could say that ... but, then again, there is no reason *TO* use
NET.
Actually there are several. Productivity alone is sufficient. Finding
labor is another. Complexity, software pattern implementation, tool
integration in IDE etc are many more.
It provides one of a number of frameworks that one can use to
develop applications, but it's FAR from being the only one, and it's
only moderately good.
It has its drawbacks so does MFC. Its however significantly better for
most dev tasks.
Its significantly better than MFC/C++ for regular use.
It's good at some things that MFC is not so good at ... but it has
its own drawbacks too.
Like what?
I'd choose MFC over .NET any day if I was
just writing a standard desktop application.
Why?
Where .NET really comes
into its own is when you need to deploy binaries onto disparate
hardware platforms and where your applications are going to be
untrusted and must run in a sandbox ... and frankly you might as
well use Java for those.
Why? Have you used Java for anything UI related? Java on MSFT
platforms?
.NET is a technically slightly better
solution than Java, but it doesn't have the market penetration (and
the market is not going to benefit from being split between two
inetrmediate-code platforms).
Says who? You are making it between Java and .Net. I dont care about
Java. We were talking about MFC and .Net.
I only recall one or two ads for C++/MFC while C#/.Net is almost
ubiquitous.
Don't judge things by advertising, that's just stupid!
Excuse me. I hire people. I did MFC for 10+ years. I have been
doing .Net for over a year. I should know the difference. MSFT
advetisement mean nothing to me. Reality is what matters.
Like any vendor, MS advertises the things that are new -- the things
that they think people don't know about -- far more than that things
that are already well-known. What's the point in telling people
things they know already?
Meaning what? Keep in mind that not everyone is gullible to believe
what someone says.
We are developing a high performance trading app(wall street, security
trading) using C# .Net. It has now come on its own. It was a rewrite
of a MFC/C++ app. Its still not there on performance level maninly
because we havent spend cycles on it. However dev time on this app is
over a factor of 2-3 over a C++ app. We have found the bottlenecks and
are now sure how to address it. Comparing the two environments, I
see .Net as by far the most productive. Things which MFC developer
worries about are not even a thought. You jump straight to business
logic. It costs far less to have the same functionality in .Net than
MFC. Even cheaper to maintain it.
---
Ajay
.
- Follow-Ups:
- Re: Future of MFC?
- From: Daniel James
- Re: Future of MFC?
- From: David Lowndes
- Re: Future of MFC?
- References:
- Future of MFC?
- From: Duncan Smith
- Re: Future of MFC?
- From: Tom Serface
- Re: Future of MFC?
- From: David Ching
- Re: Future of MFC?
- From: Tom Serface
- Re: Future of MFC?
- From: Ajay Kalra
- Re: Future of MFC?
- From: Tom Serface
- Re: Future of MFC?
- From: Daniel James
- Future of MFC?
- Prev by Date: Re: Future of MFC?
- Next by Date: Re: Future of MFC?
- Previous by thread: Re: Future of MFC?
- Next by thread: Re: Future of MFC?
- Index(es):
Relevant Pages
|