Again, anecdotal examples: for database class back in my campus we were given a choice of postgreSQL, MySQL, Oracle and MS Sql Sever to use for our projects, and the course instructor personally recommended MySQL. Bear in mind this is was class of computing newbies who have never touched database management before.
When the projects were submitted and graded he asked us why everybody (even the OS X users) ended up choosing SQL Server even though MySQL was the recommended option. The answers:
1) MySQL feels primitive
2) WorkBench cannot compete with SQL Management Studio
Being the only guy on Linux back then I didn't have the chance to try out SQL Server, but having done so recently I can fully see where my coursemates were coming from. People can speak for themselves, you know. Microsoft didn't even have to tout its software; the class made the decision on their own.
What I did like about MySQL though was that I could get lazy with defining CONSTRAINTS. Since MySQL automatically ignores CHECK statements I can purposely choose to ignore any instruction that requires a CHECK statement be set as an attribute or as a table level constraint.