 So my name is Bob German, and I've been a SharePoint fan since it was called Site Server. Well, I did start with Site Server. I kind of skipped SharePoint 2001. But it's kind of one of the cool things about this is it's the last time they've really changed the user experience or the way you develop for the UX was when .NET came out in 2002. And so I've been there all the way through all the different phases and fits and starts of different ways of doing it. I've spent a fair amount of time. I guess I got involved in it in the first developer kitchen, which was February of 2016, and I've been playing around with it ever since. What I've been trying to do is to develop solutions that will later go into the SharePoint framework. It only recently shipped, so over the last year I've been building solutions for my clients and kind of coaching my team to build things for my clients that we can later pour it in. So there's some rules of the road there of making it self-contained and following certain guidelines to make sure that it will work when you port it over. And I've been pretty pleased with the results. I did a talk here at SPTECON on future proof and was able to demo a couple of things that I had built actually up to two years ago that ported over 95% reuse into the SharePoint framework. Well, I think it's a really important and good thing overall. It's a big change. It's a lot for a lot of us to digest. But if they didn't do it, we'd end up no offense to the Lotus Notes fans, but we'd end up like Lotus Notes. Microsoft has to embrace the cloud and device era with SharePoint or SharePoint will die. It will just fade away. And this is a credible way to do it. The other thing is that over the years they just kept adding new layers on top of what they had and that just made it heavier and heavier and more and more arcane and archaic to actually build anything. And while this may seem unfamiliar to a lot of SharePoint developers, it's actually good to see it be a clean start and not have to carry all that baggage of weird things like, you know, scripting on demand and, you know, XSLT and even JS Link and stuff is looking a little bit long in the tooth at this point. I love what I see up on their roadmap. It'll be interesting to see when it all comes out. It's also great that they're being so open about it, right? So there's a website where you can go and see. Kind of looks like a mini version of their backlog. And I think they're doing all the right things. You know, there's some sort of pain points like the modern libraries and lists. I had a customer who got really badly affected by having their custom actions break. So I'm hoping that they fix that. I'm also hoping for single page applications where we can just really party down, do whatever, you know, the customer needs or really make a unique page experience on top of SharePoint. I guess my favorite part, I'm going to go with TypeScript. I like that it's TypeScript first and that the entire framework is in TypeScript. And it's just, I've become, this really was my introduction to TypeScript. I had looked at it a little bit, but I hadn't started using it every day. And now I feel completely like I'm missing it if I don't have it. If I, you know, I go back to JavaScript and I can do it. In fact, I probably do it more often than not. It's funny, I actually give my clients, if they have, if the client has a, I'm in consulting, if that wasn't obvious. If my client has a developer team, I ask them, you know, I try to talk them into TypeScript, but I give them the opt out because they may not want to have to learn it. But without it, I just feel like I'm not delivering the same level of robustness and it's just not as much fun. Right now, I'm going to go back to those two things that are already on their backlog. I really want something that will replace, you know, custom actions, display templates, that kind of thing. And also something that would allow me to do a single page app. One thing I would change, I think it's not a big change. I would just like to see a lot better documentation. Like trying to figure out how to do things is often an exercise in reverse engineering. And I know that, you know, different versions, if you've been at this and I know you have as long as I have, you know, some versions kind of come out and technical writing is right there and you've got everything laid out. And others, well, you're kind of left on your own and I'm feeling kind of like we're left on our own, which is unfortunate given how big the change is. And we're like looking at blogs. Thank you so much for all your blog articles, Andrew. But just, you know, it's like, why isn't there more up on Microsoft? I think the biggest challenge is the learning curve, is the shift. I mean, I think it's a healthy challenge, although it's a little bit ironic that, you know, one of the reasons that I was told that they shifted to the stack, more of an open source stack, was so they could attract more developers. But what I'm starting to suspect is that you still have to still know kind of what SharePoint is and how it works. You still have to know the object model underneath for making your REST calls or what have you. And you've got to learn TypeScript and you've got to know, you kind of end up wanting to know React. I'm starting to feel like, you know, the product is written in React, all the first-party web parts are written in React. The UI fabric support is better in React. So I'm just starting to feel like I don't want to swim upstream, I'm just going to do React. But all those things, I think, narrow it back down so they widened it out. And now it's narrowed back down again to these people who have this. And this is just maybe not Microsoft, right? It's just the way the web development world is. It's like you can choose, it's like a Chinese menu. Every single item, you can choose a different choice. And so to find somebody with the, with the, or to tool up on all the choices that they've made, I think is a challenge. So enterprise developers are, this is really unfamiliar to most of the people I talk to and how I work with. I think in the future this is going to, this is going to be the, this is the future. I think that it's going to, Microsoft is going to replace every single page or augment with a choice at least for a while. Every single page in SharePoint so that eventually you don't need to see any classic pages at all. And you know, there's, there'll be some, some bumps along the road. There'll be some places like with the modern document libraries when they came out and some things broke. And I think Microsoft learned from that, that they had to maybe give it a little bit more of a soft rollout. But they do kind of push things out a little bit aggressively to try to, I understand they want to drive adoption. But then, you know, it's hard for people to test the things that they've built internally. So my theory is it's going to, it's going to happen. We're going to move completely over to the new model. They will support the classic mode for probably five years or more. Until people literally stop using those pages. And they have the telemetry to, to figure that out. Whatever bumps there are on the road are going to be less than the alternative. Because the alternative is that SharePoint fades away and it would probably get, end up like Lotus Notes. And it would probably be take a half a dozen products to take over all those workloads. And it would be very fragmented. And so, you know, whatever pain anybody who's watching this might be feeling around the learning curve and the transition and realizing that your sites are going to change or, you know, hopefully you'll have some control over it, but they're going to change out from under you. Think about the alternative pain of the whole thing just kind of fading away and having to figure out what to do. You know, it's, I think Microsoft's made the right choice here.