 So my name is Mark Rackley and I am the Chief Strategy Officer for Paid Group at SharePoint Consulting firm out of Cincinnati, Ohio. So my background as a SharePoint developer goes back to the early days in 2007, so not quite the 2003 days like the old fossils, but in 2007. And from there I did a lot of web part development, you know, the feature development that she would do in Visual Studio. And then from there I actually moved into client side development, actually back in SharePoint 2007 because of some limitations we had with a client doing development in SharePoint. So I've been using the SharePoint framework since towards the end of 2016, that's when I first started playing with it and getting my hands on it and digging around. So I'm still considering myself fairly new to the framework. My impression of the SharePoint framework today is that I think Microsoft is heading in the right direction. I think their concepts for the SharePoint framework, allowing people to create their customizations and get them out of doing content editor web part customizations for some parts at some point, it's a good way to go. I think it's the right path and I think it's kind of the natural evolution of the way people are already developing in SharePoint today. So my thoughts on the roadmap for the framework is that, you know, I really like how open Microsoft is first and foremost. I like how they're taking our feedback and making sure that they cover a lot of the topics and a lot of our concerns. So I like where the roadmap is heading. I like a lot of the features that they're adding. I'm looking forward to being able to do more than just a client web part. I'm looking forward to taking advantage of things that we're missing today that hopefully are coming soon like custom actions and those sort of features that have been critical to us in the past but are currently not in the modern experience. So I'm looking forward to getting to those features back in the modern experience. The one thing I would add to the SharePoint framework today and I've given this one a lot of thought. I think that the thing I would like to see is more examples that are not React based, right? I think that they do, Microsoft, the team uses a lot of React for everything they're doing and a lot of the examples in React. And coming from my side of the house where you may not necessarily embrace a framework or no React, they say you don't have to use React. You can use any framework you want. Well, I'd like to see some more examples where they're not using React so that we can get those people in the framework faster faster. The one thing I would change about the SharePoint framework is probably this is going to get me in trouble with a lot of my server developer friends would be the use of TypeScript. And the way how embedded TypeScript is into it. And I think this leads to a fallen question of the biggest problems people are going to have with it. So I'll kind of defer the rest of my response to that question. But yeah, I wish that there was not such a dependency on TypeScript. That's an interesting question. So the biggest challenge with the SharePoint framework, I think, for a lot of developers is going to be understanding TypeScript. Because we have this huge world of JavaScript developers that maybe don't have traditional training in development. They don't have degrees in development. They don't know what an interface is. They don't understand the concept of classes. And when you throw something like TypeScript at them, it's going to make their heads explode because they just can't wrap their heads around it. So the future of the framework. I mean, I can talk about where I hope it goes. Because I don't think anybody really knows where it goes. There's so many opinions out there. I know people are concerned that they can't use Angular right now in the framework. And they think that that's going to hurt it. Some people think it's such a departure from the way .NET Devs work that it may not be, you know, successful. Like the lack of Visual Studio tooling. People are saying, well, that's going to kill it. I hope that's now what happens. I hope that they continue to invest in it. Continue to add features so that the client-side developers out there can build that skill set and start developing more enterprise grade functionality and web parts and connections and, you know, web hooks and all those things to create some really world-class applications where they're just not throwing script on a page and hoping it doesn't break anything. So I hope that that investment continues and we just make it easier to do our job. For anybody who's thinking about getting into the SharePoint framework, the best advice I can give them from someone, you know, I've been writing code for years. I've been doing, I've done .NET code, I've done Java, I've done C sharp, that's part of .NET. But I've done a lot of development and still jumping into the framework, I was at a loss because it is such a big change. And so I kind of had to just break things and then reach out to people who knew things to get the answers. So I would highly recommend that people actually do training. I've heard that there's a website called Voitanos. They have a Mastering the SharePoint framework course. So I would definitely don't expect because you're a great developer that you can pick this up, right? Actually invest in some training. It's going to make your life a lot easier in the long term.