I’m trying to do some Sharepoint (WSS/MOSS) 2007 development, mostly advanced custom forms …. .
I’m little bit flustrated and right now I think (feel) that SHAREPOINT SUCKS.

It’s so … overcomplicated … unclear … strange.
Sharepoint Designer is so unfriendly tool.

I’m … angry and typed ‘Sharepoint sucks’ into google:

• http://furuknap.blogspot.com/2009/10/sharepoint-sucks-and-heres-why-part-1.html 
• http://furuknap.blogspot.com/2009/10/sharepoint-sucks-and-heres-why-part-2.html 

  Customers are easily impressed and sold when a salesperson, whether that person is a consultant or a bone-fide seller, demonstrate how easy it is to hack together a working proof-of-concept.
  When a real architect or developer enters the project,
  customers are shocked to learn that developing a SharePoint solution is nothing different from any other software development project and is a lot more expensive than the impression left by the sales process.

  When shit hits the fan, blame is easily placed, but the customer is still left without what they want. So, the customer is asked, again, to adjust their requirements to meet the solution.

• http://www.realsoftwaredevelopment.com/why-sharepoint-portal-server-is-terrible/ 
• http://sheehantu.wordpress.com/2008/02/01/sharepoint-sucks/ – & comments
• And finally post from 2005 about SPS 2003. It’s like a prophet :-):
  Five Things wrong with Sharepoint: http://www.informit.com/articles/article.aspx?p=391848 
• AND FINALLY: http://vtimashkov.wordpress.com/sharepoint-disadvantages/  - good technical list of SPS bugs & stupidity.
• AND FINAL FINAL FINAL (comment from here): Heh :-)
  Let me just say this, as primarily a BI guy who has become responsible for essentially a sharepoint frontend of reporting services.  I have spent the better part of a week trying to migrate our current production environment to a different dev server with a fresh sharepoint install.  I have run into more errors then I can count, and tried multiple sharepoint tools to try to accomplish this.  I have posted multiple times to the Sharepoint MSDN message boards with not even a single response other than myself practically begging for some advice.  For probably the first time in my life in IT I am looking at a situation where I have no clue how to successfully do what seems like a pretty typical task, and I see no hope in sight.  Hence my frustration and typing in Sharepoint sucks into google just for fun, and I stumble upon this.
  
• !!!! sharepoint-not-the-social-answer !!!!!!  http://www.jimgoings.com/2008/03/sharepoint-not-the-social-answer/
  When we migrated from SharePoint 2003 to 2007 ……..
  …… You know what we had in the end? A freakin’ glorified file server. ……
  …………
  One of the comments:

  I know one guy (and I know people in 20+ contries that work with IT), that can handle all the needed aspects of running and developing Sharepoint. The list of knowledge you must have to develop and maintain this application, without stepping on a “land mine” is huge! This means you will have to have more IT personnel to end up with something that in the end, will not resolve anything. Cost goes up, frustration goes up, and resolutions does not exist.

  Instead of Sharepoint, build custom applications for the processes you can not cover with “out of the shelf” software, and instead put up a couple wiki pages, and a good search engine along with a good document handling system. Yes, you will end up with more than one application, but at least you will not end up with cahos.
  

• http://enterknowl.blogspot.com/2008/10/sharepoint-summit.html

--------------------------

And Opposing voice:

• http://weblogs.asp.net/bsimser/archive/2009/09/29/sharepoint-fud-spreading-far-wide-and-fast.aspx