I mostly try to avoid Sharepoint, but I see it used all over the place.
IMO, It is mostly just a mix of document repository (SVN) and custom website with permissions linked to active directory. However, organizations that can't roll their own intranet site worth a damm can often setup a SharePoint site that meets most of their needs. It supports customization through both plugins and custom code which is how MS get's their long term lock-in. For companies that can maintain say a talented Ruby on Rail's team there is little benefit but where the 'programming team' mostly slings excel macro's SharePoint can still get stuff done.
It's a slippery road to re-implement Sharepoint capabilities using Rails.
It's a typical buy vs build scenario. From my understanding, it's not difficult to integrate other enterprise apps to Sharepoint and make a dashboard.
You can probably do that with a bunch of Rails people but if the platform provides a decent "Portal" capabilities out of the box with minimum modification, why build from scratch?
The alternative is to install MediaWiki, WordPress, some sort of CMS perhaps, some sort of Portal (LifeRay?), some sort of document management system that supports versioning and decent web UI, integrate a bunch of services using custom web-app. That's a lot of infrastructure to deal with.
IMO, It is mostly just a mix of document repository (SVN) and custom website with permissions linked to active directory. However, organizations that can't roll their own intranet site worth a damm can often setup a SharePoint site that meets most of their needs. It supports customization through both plugins and custom code which is how MS get's their long term lock-in. For companies that can maintain say a talented Ruby on Rail's team there is little benefit but where the 'programming team' mostly slings excel macro's SharePoint can still get stuff done.