Re: C++ vs. C#
After working on a bunch of "web applications" I find them very difficult to
develop, maintain, and test. There are also lots of security restrictions
if you host them in a web browser (unless you download and install ActiveX
or some other sort of local executable and then you may as well install on
the client). I also think the Doc/View model still has some life in it.
The sad part is that the model was not documented well so many people, even
after living in that paradigm for years, still don't understand how it
works. It so easy to use MFC without understand all about how it works,
that you often don't take advantage of features that can be used or
extended.
Tom
"David Ching" <dc@remove-this.dcsoft.com> wrote in message
news:D79ACD6D-EFC3-4B3A-8445-53FAD3DE3C5A@microsoft.com...
"Joseph M. Newcomer" <newcomer@flounder.com> wrote in message
news:bddtu41hehh26sgpjrgsauilicfbukmqtk@4ax.com...
But the CView does not need to be the same CView as a "fat app". It
could be a CView that
used a preprocessed representation (I used CHTMLView as a simplifying
example). So the
question is, who preps the data for the CView? If the CView has to be
large and bulky and
smart, talking to a doc that is large and bulky and smart, they you have
a fat app. If
you host a CView that does very simple things to data that is in a
CDocument whose sole
purpose is to download preprocessed data from the server, you can have a
very thin app.
Make it a COM server and it will run in a browser.
Perhaps, but then it seems the only reason for using MFC is for the
doc/view model and there are easier, more webbish ways of achieving that.
-- David