I don't know if using AngularJS or any similar JS framework to get a full SPA experience is fruitful in DNN's current architecture which is based on WebForms. It sounds like hammering a square wedge into a round hole. A SPA app just means all user interactions and updates will result in quick DOM updates based on getting just the data for these elements without regetting the whole page and its elements again. Even one can mimic a SPA effect using an UpdatePanel, although it's not very efficient.
As an ASP.NET developer, I would like to see DNN move completely away from WebForms. Maybe not so good news for current module developers but in order for DNN to move forward and have a more active development community, DNN to use the modern web and Microsoft stacks. I bet there are companies who ignore DNN thinking it's based on antiquated technology. Whether this makes sense technically is irrelevant. Perception is what matters. Same thing for developers. New .NET developers are not going to be exited to work on DNN once they know it's based on WebForms instead of MVC.
I am a full time developer in a job which is not DNN related at all and would like to work in my day job and on DNN in my spare time using the same set of technologies. That means ASP.NET MVC, HTML5, lots of Javascript, a popular JS framework like Angular, RESTful/WebAPI services, Bootstrap, rwd techniques... etc. These are the hot skills these days in the .NET world. If I search a job site like dice.com in my city for ASP.NET, WebForms is hardly mentioned. AngularJS is very hot these days. Actually if I say I don't know MVC, I probably won't be able to get any good job. Therefore it makes no sense for me as a developer who wants to keep his skills up to date to still be using WebForms. Also makes no sense for me to split my time between WebForms and MVC. I want to be an expert in MVC instead of being jack of all trades, master of none.
Therefore I am really looking forward when DNN goes to a full MVC platform but being able to build modules in ASP.NET MVC is still very beneficial.
Also the move to MVC hopefully will flush out the old crappy modules from the store. I have installed tens of commercial modules from the store and noticed a common pattern; poor UI/UX experience. Lots of them (non popular ones) just have a bunch of form elements placed on the page with little organization and poor workflow.
The reset will force the module developers to rethink the design of their modules and work on new implementations which work better in modern browsers. Working in mobile devices is an example.
Whenever I see a web app with lots of text & hints explaining what the user needs to do next or what a form element is about, I know the developer hasn't thought the app through. In general developers make bad UI designers. Very few developers are really good at both and developers tend to not hire UI designers because they think they can do it themselves. Sure it's easy to place links, tabs & form elements.. etc on a web. To make the app look polished, professional, easy to use and navigate and where things are easily discoverable is another set of non development skills.
I want to totally through away my WebForms knowledge even though it took me many years to acquire it and embrace the new ones. For the simple reason it will make it easier for me to find a new better job any time.
The wealth of DNN store and the opportunities it offers is what is what makes DNN exciting for me. I want DNN to be an opportunity for me to learn and apply new skills by creating modules which I can sell and support, where users find my work useful and beneficial.
Looking forward to a brighter DNN future.