Re: .NET
- From: "Richard Foersom" <r.nojunk.foersom@xxxxxxxxxxxxx>
- Date: 29 Aug 2005 17:43:09 -0700
> That's not the point. The point was that he was arguing "Microsoft
> didn't drop anything and rush to port Office to .NET - therefor it
> must suck as a development platform". That argument was flawed - an
> existing system that works fine doesn't benefit from being switched
> to ANY other development platform - no matter how cool. Keeping it
> the way it is involved 0$ cost, while porting it by definition does
> involve a cost (again, no matter how cool and efficient the system
> is) it's a no-brainer.
No Marc, your argument with Delphi and MFC were wrong. It would be a
major scoop for Borland and big defeat for Microsoft if it was ever
discovered that a wellknown Microsoft application was written in
Delphi, rather than in one of Microsofts own tools. If Microsoft
themselfes do not use the tools they are hawking the most, you as an
outside developer have reason to be precautious.
Lets take good ole Vicious Basic as an example. How many major MS
applications was/is written in that bugger? VB itself was written in C
by C programmers, and to me it looks like they did not care much for
the overall outcome. The smart guys avoided VB, and selected Delphi or
Visual C++ instead, but great many people would just take MS marketing
talk as godspell and use VB.
Eventually MS would completely break backwards compatibility between
VB6 and VB.net. Do you really think this would have happend this way if
a major MS applications like PowerPoint and Excel were written in VB6?
With MFC Microsoft gave the world a second class GUI framework, while
they actually used another home grown framework for their most
important applications (MS Office). With MFC, Visual C++ became as
visual as wearing sunglasses indoor at night.
AFAIK MS office on Windows started well before MFC was made. Later
keeping the two different was probably seen as a competetive advantage,
because it would require more effort for an outside company to make an
application that could compete with MS office.
AFAIK Visual studio (as in VC++6) is the most wellknown MS application
that uses MFC.
What is the future for MFC nowadays? None?
So the fact that when MS use their own development tools and
frameworks, tells you that you can have some belief in quality and
longviety of the tools. When they do not you have reason to worry.
Marc please tell, which major applications have Microsoft written with
C# in dot-net?
Doei RIF
.
- Follow-Ups:
- References:
- Prev by Date: Re: News reader
- Next by Date: Re: D2005 is great! VS 2003 is crap!
- Previous by thread: Re: .NET
- Next by thread: Re: .NET
- Index(es):
Relevant Pages
|
