SharePoint dev here. The problem is that Microsoft attempted to build the product to cover every environment/workload/userbase, and as a result fails pretty miserably at all of them.
-You want a CMS? Use SharePoint!
-How about site for delivering BI dashboards? Use SharePoint!
-Large, mostly static public facing site? Use SharePoint!
That's true! I met Microsoft last year at the start of a large project for a client, and we were asking them to recommend a CMS to run in a .NET environment. They DID suggest Sharepoint. I laughed at them - "you are joking" I said. But they insisted, and we had to add Sharepoint to the shortlist of recommended CMS's just so that the client thought we considered everything their Microsoft salespeople were saying. But it was always a joke at that point.
Generally Objectionable. I think it gets packaged with windows server and exchange server for free (or nearly free) which is probably the only reason people use it.
