Developing Development Standards

Recently, a number of clients, technical and business alike have asked about the future of SharePoint development.  where is it going, is it falling behind...

We've answered these questions more by introspection than direction from anywhere else.  As a business we changed the way we develop about 12-18 months ago, we did this as a reaction to other, non-SharePoint, projects we were working on in an appreciation of the maturity of frameworks such as AngularJS and toolsets like Telerik - the integration between which is seamless and simple.

It's good to see that the decision we made wasn't a diversion from the norm and that even the developing standards are following a similar route.  Here are a couple of links that will help describe where this is going and help understand the technical aspects of developing in this vein.

Framework Developer:
dev.office.com/blogs/sharepoint-framework-developer-preview-release

Framework Client Webpart
dev.office.com/blogs/building-simple-sharepoint-framework-client-web-part

One thing we also find exiting here is that as developers, we will be able to develop SharePoint applications (complex ones) without the need of a full on SharePoint implementation on the development machine.