Ok, but it won't have that responsive feel about it. Straight mvc is boring
imho. I really liked angular 1 - not so much angular 4.

On 2 Apr 2017 9:57 AM, "Greg Keogh" <gfke...@gmail.com> wrote:

> Folks, I've been reading the results of search for things like "SPA vs
> ASP.NET" and "why use SPA" etc etc. I have come to the conclusion that JS
> driven SPAs are not all they're cracked up to be, and the cons outweigh the
> pros. I'd even go so far as to say that SPAs are a fad, and even worse,
> that they're the misguided use of languages (JS) and hacks (async http) in
> inappropriate ways.
>
> I'm going to write a demo ASP.NET MVC app for the boss, and it will be a
> hybrid that a lot of articles hint that is the best way to go. JS scripting
> will be involved, but only in libraries that use it internally, and I'll
> only use it to create popular UI illusions like menus and dialogs. So after
> all my pondering and reading it looks like going back to a classic ASP.NET
> MVC based hybrid is best for me.
>
> *Greg K*
>

Reply via email to