I recently stumbled across an article on informit.com entitled “Five Things Wrong With SharePoint“. Having spent a fair amount of time implementing SharePoint at Talis I thought I’d comment on it here.
According to the article the first thing wrong with SharePoint is “It’s a crappy mish-mash of multiple technologies”. The author says
Once you get past the shock and horror of encountering the alien JavaScript files, to professionally program SharePoint you also have to deal with CSS, HTML, XML, ASP.Net, Visual Studio.Net, and your choice of C# or VB.Net. That doesn’t include dealing with Windows Server 2003, Active Directory, and the wonderful world of IIS.
That’s not what I’d call a crappy miss-mash, each technology has it’s own strengths and I don’t really see how you could create a portal or any other modern web app for that matter, without using more than one technology, but I do take the authors point that SharePoint is relatively difficult to configure and program.
Reason number two is “The development team is playing the Longhorn card”. I guess that should read “Vista Card” but then the article was written back in July. I’m not even sure why waiting for Vista should be considered a bad thing. Updated versions of SharePoint are scheduled for 2006 to coincide with the release of Office 12.
Reason number three is “There are two SharePoint products, which is confusing”. I agree wholeheartedly. Ditch the Services edition or improve the documentation.
Reason number four is “Support for SharePoint is lacking”. Again I agree, it took an awful lot of digging just to find simple information and the books are few and far between.
Finally reason number five is “Microsoft has not stated a strategic direction for SharePoint”. I also agree with this and it will be interesting to see where Microsoft goes with the product.
I’ve grown to quite like SharePoint but I’m not beyond bashing it. My list of five things wrong with SharePoint reads
- SharePoint has poor Active Directory Integration. A surprising amount of features that you would expect to be able to handle through the AD can’t be, and those that can don’t work particularly well.
- Cross-browser compatibility and standards compliance. Why have Mac specific CSS if the pages still don’t render correctly on a Mac?
- No support for Forms based authentication. Why can’t they provide an interface to match Outlook Web Access?
- SharePoint takes over your ISS installation. This makes it more difficult then it should be add websites to ISS that aren’t part of SharePoint.
- Administration is inconsistent and poorly documented. You still have to rely on the command line for many of the admin tasks (stsadm and setupsts), the directory structure is complex and unstructured and the central administration tool is poor.
Only time will tell if Microsoft can fix these problems, in the meantime I’m happy to work with what we’ve got. It’s a damn sight better than the static HTML we had for an Intranet before.