Timeline for SharePoint development past and "future": how to keep calm?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 3, 2017 at 6:30 | comment | added | eirikb | CSOM is the best thing to happen to the platform., I couldn't agree more, and for JavaScript the JSOM counterpart. I don't think the REST api is "there" yet, since it is lacking in features (e.g., Taxonomy). | |
| Feb 1, 2017 at 13:17 | comment | added | James Love | MSFT don't give a crap how efficient we are as solution architects, as long as they can continue to sell licences it's up to us to design around it. | |
| Feb 1, 2017 at 10:46 | comment | added | Evariste | Yup... so it means we are less efficient than 10 years ago... am I too conservative if I say this is not a progress? | |
| Feb 1, 2017 at 10:42 | comment | added | James Love | Agreed. There are lots of bits of the SharePoint API that are amazing for enterprise applications - Timer Jobs, Content Databases, security model, authentication system, claims providers. All in the one package. But now in the cloud, if you want timer jobs, you have schedule a console app or upload it to an Azure WebJob. You have no choice with authentication or content databases. The customisability has definitely shrunk. | |
| Feb 1, 2017 at 10:39 | comment | added | Evariste | SharePoint used to be good to quickly develop applications by providing a high-level framework (data storage with permissions and versioning, authentication, list views, customizable pages, search, upgrade management...) [Speaking of upgrades: have you tried to upgrade an add-in? Do you think the user experience is great?] If SharePoint is not considered anymore as a platform to host custom applications: let's just move to pure ASP.NET, with associated costs. | |
| Feb 1, 2017 at 10:39 | comment | added | Evariste | "given how often SharePoint changes as a platform" --> That's my point, it should not change that often. Enterprises look for stability. Also, with the "old-fashion" model, I easily built applications for SharePoint 2007 that are still working and maintained. They've been upgraded to SharePoint 2010 and then 2013 without much troubles (most troubles actually came from UI cutomizations, not business applications). | |
| Feb 1, 2017 at 10:27 | history | answered | James Love | CC BY-SA 3.0 |