 My name is Eric Overfield, President Founder of Pixelmol, as well as Office, Servers and Services MVP. I've been developing SharePoint in about 2007, 2008, really though focusing on SharePoint 2011. Mainly, I've been on the front-end side of SharePoint, so really working with master pages, page layouts, et cetera, a little bit of some web part stuff later on and now just fully into SharePoint. Started working in the SharePoint framework, I first saw some of the beta bits about June of last year, got really excited, it was pretty cool. Since then, I've been playing with it more when it came out in preview, definitely got involved in public preview, absolutely. Now with GA, spend as much time with it as I can, it's a pretty cool technology that I'm excited to be working with. The framework today is in pretty good shape, I like what they went out with GA, I'm really happy they started with web parts, there's a lot of gaps, there are some things missing, but right now, no, I like it, I'm glad they got it out finally into the public general availability, so we'll see where it goes. I like where Microsoft is saying they're going to be taking the framework, it's going to grow significantly, I expect, there's going to be the major model we're going to use to customize SharePoint, so all in all, I'm kind of happy with where they plan to take it, we'll have to wait and see, I'm sure there's going to be, ask me in three to six months and I might have some new ideas about where they might have been taking it, but if they can deliver what they said, it'll be good. It's got to be client-side rendering, I'm really excited to see that Microsoft made that leap from the server-side rendering side to the client side, it's where the web has been moving for a couple years now, I've been trying to move a lot of my clients there and I'm glad to see that Microsoft's making that a first-class citizen, shall I say, where they're taking it and they're going to say, hey, this is the new way they're going to be providing an interface on top of SharePoint. Only one thing I'd add, huh? Well, we'll see, I mean, right now, there's only web part, so there's a lot more that I want to see, basically, I'd like to see the entire interface of SharePoint move to, shall we say, the SharePoint framework, which they've sort of been saying they've been hitting at, we'll have to see if that happens or not, there's still that roadmap that I think might change a lot, so generally though, I'd love to see the framework expand, I'd like to see more than just web parts, of course, I'd like to see a lot more control of the interface happen within the framework itself. Right now, what I'd really like to see changed is the tool chain, the tool chain itself being really how things can get compiled when you're building it. This is not the biggest deal, a lot of people are freaking out over this, it's okay, it's all this code, it's like 900 megs, I think, on a bill just to be able to build a web part, but your web part's small, it's just a couple K, that's okay that it's small, but I wish they would tighten that up, and secondly, along that, I really think they need to be shrink wrapping this or providing a shrink wrap ability where we can have a web part that is tied into very specific dependencies that won't change on us if we said, hey, this web part needs these dependencies. The current challenge I see right now is general, it's not adoption, it's learning what this new tool chain is all about, in particular, I'm seeing a lot of resistance with TypeScript, which is the primary language that builds, that you use to build your web parts, TypeScript is that ability to, it's a subset, in a sense, shall we say, of JavaScript that allows you to build in a more typed methodology that then gets transpiled to JavaScript, and .NET developers don't get that, they don't understand that whole methodology, I mean, even though it's sort of built for them, it's totally new and totally weird, so that adoption, that learning what the tool chain is all about, learning what Node.js is, and how that works with NPM, and then how WebPacks gets put together is a huge challenge for a lot of people. That I'm not concerned about long term, I think we'll get it. The more I teach people how to use it, they're like, oh, cool, I like this, this makes sense, and I'm sure we'll see some really good adoption. Predicting the future is rough with Microsoft, and let's be direct on that one. Six months, 12 months, we're pretty set, SharePoint framework's coming out, they have a roadmap that's pretty short term, all of their new interfaces, the modern UI is all built basically on top of this tool chain, so we know that the framework short term, six, 12 months, is set. Past that, I would love to see the framework be the thing for the next three to five to eight years. I mean, I can't predict anything past that, who knows where web development's going to go. I think client-side rendering is the way for the future. Five, 10 years, will the framework be it? That depends on adoption, that depends upon how Microsoft releases the framework, and don't get me wrong, what they're trying to do is hard, it's not easy, I've been telling everybody I can that we can't expect them to have a perfect product instantly. They need more resources, I think the direct answer to that. So, 18 months, 24 months, I hope that the framework is widely accepted, I hope it is widely adopted, I hope that it is the new framework, the new methodology we'll develop for many years, so that this is not going to be just the fourth of five different development technologies, this will be the fourth for a long time. It will change, we know that, that's okay, is this going to be something worth learning? Absolutely, I really hope it is. I just would not be, I'm not going to risk me trying to say what's going to happen in the next 18 to 24 months, because I really just don't know. My first advice has got to be, get started now. There's no reason to wait, the framework is out there, there is really good videos to get started today. Busiest way I know is you go to github.com slash SharePoint slash PNP, they've got a whole bunch of examples, they have this JavaScript special interest group that they've been building even more examples on the framework. There's no reason to wait. Okay, so now that you said I'm going to do this, I'm going to go download the tool chain and get started, now what do you need to do? You're going to need to learn TypeScript. My first two hours of TypeScript is kind of like, what, and I like, I have a pretty good JavaScript programmer, I feel. TypeScript was different. As soon as I got over that hurdle, that two hours hurdle, got it, makes sense. Don't be scared of TypeScript. We've always had these new models, this has always happened, there's always change. If you're a program, you're not willing to change, then you would be stuck in cobalt and you didn't go anywhere. So it's okay to learn a new tool chain, it's okay to learn a new tool set, don't be scared. I do believe the framework will be well worth your time and effort if you get started and you jump in and then just reblogs, get training, go to YouTube, there's so much good material out there, no reason to not get started today.