OK, following my previous post:
- I stepped back from this SharePoint forum for a few weeks.
- I tried to dig into the SPFx framework with a good faith. After all, add-ins were crappy (almost MS words), so could not be worse (spoiler: wrong!).
Here are my first actual feedbacks on SPFx:
- First, while you could install only Visual Studio to have a "all-in-one" tool to develop, you now have to setup: NodeJS (mind the version!), Gulp, Yeoman, Yeoman SharePoint generator (mind the version), Visual Studio Code.
- Visual Studio code is far from being as powerful as Visual Studio: to be convinced, only consider the very basic search tool.
And you constantly have to switch between VS Code and a cmd prompt. VS Code is much more like a Notepad++ than an actual modern IDE.
- To create a simple Hello World template project, you need to run yeoman @microsoft/SharePoint and wait... 10 minutes! Back in the old days, it was a matter of 3 clicks and 10 seconds.
- A simple Hello World project is... 230MB of files. 230MB to display "HelloWorld". It's heavier than a complete .NET installation!
- A lot of different config files to deal with, located at different places, and with different formats.
Now you have to store files outside SharePoint. Where? Not Microsoft's problem. Ho, of course, you can use Azure (i.e. create an account, don't forget to pay for it, etc.)
- Even simple problems like "how do I rename a Web part" are problematic.
- How to package common code between multiple Web parts to a separate bundle? An old classic question we should have an answer to for ages, you think? Ugh, not that simple apparently.
- We've heard for years that JSOM is the way to go, so, obviously, it's easy to integrate it to SPFx... hum... not that sure actually.
- How many proficient C# developers do you know?
But as we have a word for all this mess ("toolchain"), everything is under control.
So here's my actual question: what can we build with SPFx, apart from 1990's state-of-the-art weather widgets?