Re: MFC/C++ vs .Net/C#
- From: "Ian Semmel" <anyone@xxxxxxxxxxxxxxxxx>
- Date: Wed, 12 Mar 2008 18:56:11 +0000
"David Ching" <dc@xxxxxxxxxxxxxxxxxxxxxx> wrote in message news:AwEBj.62277$Pv2.19312@xxxxxxxxxxxxxxxxxxxxxxxxxx:
"BobF" <rNfOrSePeAzMe@xxxxxxxxxxx> wrote in message
news:Oo4OOZ8gIHA.5164@xxxxxxxxxxxxxxxxxxxxxxx
>
> Hey gang,
>
> I'm only posting this here because I've seen the light after many
years of
> disparaging comments and snarks against .Net in general and asp.net
> specifically.
>
> Sorry for the past insinuations and ridicule ... this .net stuff
> absolutely rocks! ASP.Net is the way web development should've been
from
> the beginning.
>
> I'm still hitting bumps in the road with C#, but every time I do it's
> because I'm trying to force C#/.Net to do things the way they would be
> done in MFC/C++.
>
> Each time I get back on track life is good again.
>
> I wish I wouldn't have been a holdout for soooo long. I should've
picked
> this up years ago!
>
>
Heh, welcome to the club! :-) Although I think it was only recently
since
VS2005 and .NET 2.0 that .NET started becoming a viable alternative to
C++/MFC. Around that time, downloading and installing the framework
became
more acceptable due to broadband becoming more available, Core Duo's
providing acceptable performance becoming mainstream, WinXP SP2 accepted
as
a minimum OS, etc.
But until now, .NET was still only an optional alternative to C++/MFC.
But
with WPF coming in vogue and only managed code providing a way toward
this
new UI in the future, .NET is truly going to be the only way to write
Windows apps in the coming years.
While ASP.NET does make it easy to write web apps, I still find it a
kludge
compared to using C# to write desktop apps. You still have so much
control
with desktop apps that you have to jump through hoops in ASP.NET. The
.NET
parts of ASP.NET are OK, but you're still stuck with DHTML, CSS,
Javascript,
etc. that it's still a kitchen sink kind of thing.
I think that this is due more to the fact that the whole of the internet is a kludge nowdays.
What started out as a perfectly reasonable way to display static text on a screen via a browser, is now being asked to do things that it was never designed to do.
To achieve this, new technology is being shoe-horned into old, resulting in things like javascript, ViewState and all manner of fluff comprising about 90% of any web page that is downloaded. All of this is there to be able to give the appearance that the web app is reacting like a winforms app.
Unfortunately, I think it is a bit late to start all over again.
.
- References:
- Re: MFC/C++ vs .Net/C#
- From: David Ching
- Re: MFC/C++ vs .Net/C#
- Prev by Date: Re: Process does not contain any programs (???)
- Next by Date: Re: My own fuction: Access Violation error...
- Previous by thread: Re: MFC/C++ vs .Net/C#
- Next by thread: Re: MFC/C++ vs .Net/C#
- Index(es):
Relevant Pages
|
