This sounds as if you're mostly hearing the most common opinions. That's only half of the story.
You should probably also listen to individual stories and bug reports. As a solution, you could mark users internally that provide useful bug reports and give more visibility to other reports from those users. This way you wouldn't drown in common, loud & noisy feedback.
Thanks for the very interesting presentation! A couple of thoughts:
Please don't use averages for latencies. Please use percentiles. Search for "gil tene latency" if you don't know what I'm talking about.
While the Insider program works great for some things, it doesn't work for some others. I often feel that my detailed feedback is overwhelmed by 14'583 people shouting "KAITICHIZTAN NEEDS OFFLINE MAPS!!!1!!!" and things like that. Do you consider the long tail of feedback? It sometimes feels that no one pays attention to feedback with few upvotes.
Recent builds have very few BSODs and crashes. On the other hand, "brownouts" ("Resuming..." forever on mobile builds, broken rendering on desktop, broken scaling on desktop, lack of UI polish, ...) appear to happen more often. There are soo many issues that I wouldn't know where to start reporting. Do you have ideas on how to address this problem?
I hope that you don't treat the feedback from all users the same. Some users put much more effort into good bug reports than others.
I'm really looking forward to Shared Nothing Storage Spaces. With the addition of rebalancing it looks like the perfect solution.
I think one of the last questions was misunderstood. I believe the question was: Why would anyone deploy "traditional" storage spaces when Shared Nothing Storage Spaces will become available? (i.e. "What are the disadvantages of SNSS compared to traditional SS?")
Wow, thanks for discussing my question ("[09:53] Surface Type Cover is touchy")!
The weird thing is that we're all having this problem with different keyboards (Touch- and Type Cover). So far I haven't met a single person that hasn't had this problem. All updates, including optional, are installed. Anand Lal Shimpi even mentioned the problem in his recent review of the Surface Pro 3:
"There are also times when the keyboard and/or trackpad will stop responding. In some situations only certain aspects of the Type Cover won't work. For example right now I can't seem to get two finger scrolling or any other trackpad gestures to work. This is a problem I've seen on every single Surface since its release, although the problem itself seems to have gotten better over the years. Thankfully unlike previous implementations, detaching/reattaching the cover is usually enough to fix things."
Great session (presentation & content). Would love to hear more about .Net native from him. Specifically if life's easier for the optimizer when dealing with IL. Can more/other optimization be performed? I'm asking because pointers (in C/C++) make many optimizations quite difficult.