Re: MFC future?



Obsolete? I don't think so. It is the IL concept that is obsolete. ILs
are an unnecessary layer of indirection and all ILs assume the
programmer wants less control than the developer of the IL and their
accompanying libraries. Well, that's just not the case. As the lowly
programmer becomes smarter, he wants more control. I saw this when
programmers went from C to Pascal and then back to C as they remembered
the power C gave them (eg, IIRC, Pascal had 7 operators vs. C's 42).
UCSD's p-code came and went. Java IL had its problems with 'write once,
debug many'. Any bets on how long .NET's IL will last? There is
something wrong with an architecture (ie, having an IL) that assumes
that a particular set of developers (of that IL) think they can predict
the bounds of my programming targets. I don't buy it. If I want
simplicity, I encapsulate. If I want help encapsulating, I use trusted
libraries including MFC. Want automatic garbage collection? This was
one of the major campaign slogans for using Java. There are many
flavors of garbage collection and there are libraries for each. To make
my point, would you choose a programming language today (with an IL)
for your next development project based on how hard it is to deal with
memory leaks in C++? I didn't think so.
RT

Nishant Sivakumar wrote:
> Hey Tom
>
> Kids probably look at MFC devs and think, "Man, how uncool can people get?"
> or something like that. Us obsolete old men have to continue MFCing though
> *sigh*
>
> --
> Regards,
> Nish [VC++ MVP]
>
>
> "Tom Serface" <tserface@xxxxxxx> wrote in message
> news:%23pbkjcc9FHA.1420@xxxxxxxxxxxxxxxxxxxxxxx
> > Yikes, here we go again :o)
> >
> > These articles are interesting:
> >
> > http://msdn.microsoft.com/visualc/whidbey/mfc2005/default.aspx
> > http://blogs.msdn.com/texblog/archive/2005/06/10/428143.aspx
> > http://www.codeguru.com/forum/archive/index.php/t-184715.html
> > http://discuss.fogcreek.com/joelonsoftware/default.asp?cmd=show&ixPost=35562
> >
> > Tom
> >
> > "NewbProgrammer" <paul_kiefer@xxxxxxxxxxx> wrote in message
> > news:1133363897.273228.83080@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> >> I'm a home programmer who occasionally does programming for work using
> >> MFCs. I have not yet had a chance to look at VS 2005. Are there
> >> changes to MFCs? It seems Microsoft is heavily pushing .NET. Is MFC
> >> slowly being phased out? (Do I finally have to learn .NET?) Any
> >> guidance from the professionals out there?
> >> Thanks,
> >> Paul
> >>
> >
> >

.



Relevant Pages

  • Re: Need Disassember Soffware
    ... The programmer has been gone with no ... I like this obsolete software very much that I should ... Another commercial option is the DOS disassembler Sourcer. ... Michael Brown ...
    (comp.lang.asm.x86)
  • Re: Nice asp.net Work Log application
    ... custom login stuff is obsolete. ... So true, but one thing that has made me a better programmer, is to know ... what goes on under the hood. ... it isn't obsolete if you plan on making the website using ...
    (borland.public.delphi.non-technical)
  • Re: use vs require
    ... "require" is older way of including modules, why not just make it obsolete. ... The most important skill a programmer can have is the ability to read. ...
    (perl.beginners)
  • Re: C#--is it growing? Or saturated? (Charles Petzold does C#)
    ... tools/languages to use. ...  Jobs like that can lead to a programmer being obsolete, trapped, ... and otherwise unemployable stat. ... danger of becoming obsolete. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: MFC Interview Tests
    ... I've been programming in MFC since 1993 and I've never written an application using the database interface. ... IMO you may be better off giving candidates a real life example and putting them at a computer for an hour with access to the internet and see how they approach the problem. ... If it were me I'd be looking for a programmer, ... void Parse ...
    (microsoft.public.vc.mfc)

Quantcast