I would like to hear some practical comments about how to decide whether a
new application becomes a Winform vs a Webform application.  Would you say
that every app should be, by default, a Winform app unless it positively
cannot be (for some technical reason).  Or vice-versa?
Obviously, Visual Studio could never be a Webform app because it requires a
lot of CPU cycles.
It appears to me that there is a broad sort of continuum in application
characteristics.  Some apps are natural Winform apps (VS Studio), while
others are natural Webform apps (heavy textural content, non-updated).
However, between these two poles, lies most of the rest of the today's apps.
How do you decide which pole the new app should gravitate toward?

Here is a quote from Alan Cooper, just to raise the temperature and get you
started thinking (can you rebut this if you are a Webform afficionado):
"The browser is a red herring; it's a dead end. The idea of having batched
processing inside a very stupid pro?g?ram that's controlled remotely is a
software architecture that was invented about 25 years ago by IBM, and was
abandoned about 20 years ago because it's a bad architecture. We've gone
tremendously retrograde by bringing in web browsers. We have stepped
backward in terms of user interface, capability, and the breadth of our
thinking about what we could do as a civilization. The browser is a very
weak and stupid pro?g?ram because it was written as essentially a master's
thesis inside a university and as an experiment."

Thanks,
Dean Slindee