Let me start off by stating that I love Dreamweaver, well, I *loved* it. Frankly, I'm disappointed by Macromedia. Frustrated by it's about face from the community and the apparent lack of concern about the effects it's mergers and acquisitions has had on it's image. Turn on the wayback machine and I'll show you why:
1996 - Learn to hand code html a university departmental webiste and a national professional organization
1997 - Learn to use Gonet Communications GoLive (!) on a Umax SuperMac (!!!)
1998 - Develop my first corporate website using FrontPage 98 and Liquid Motion (does anyone remember this app?) Later after much resistance, make the switch to Macromedia Dreamweaver, Flash and Director.
1999 - Develop my first application in Elemental Drumbeat 2.0.
2000 - Make the switch to Drumbeat 2000 (all roads lead to Macromedia)
2000 thru 2003 - Avid, satisfied, and productive use of Macromedia studio.
In 2001, Macromedia completed a merger with Allaire, the maker of Cold Fusion, and over the next couple of years, the synergy of the products became stronger. This may have been good for developing the Cold Fusion market. What also happened during the subsequent years was a continued effort to force users into the Cold Fusion camp. All the while, Macromedia’s support site included fewer and fewer practical examples in PHP and ASP developers.
So, in Internet years, it's fair to label me a long term, loyal customer. I frequently recommend Macromedia to customers and integrated lots of sites with Contribute. That said, somewhere along the line, Microsoft started to catch my attention again. Mostly because the things I wanted to do weren't documented (although certainly possible) in the Macromedia Studio package.
Then the Adobe announcement came out. And designers and developers who have ideologically been at odds for YEARS will now buying software from the same company. How does this bode for innovation and competition needless to say pricing?
In my opinion, since the Allaire merger, Macromedia has consistently been more aggressive with it's pricing model, selling developer toolkits and providing fewer and fewer free examples to customers.
What really drew me to Macromedia was the extensive community support for their applications. In my Director days, I frequently leveraged the newsgroups to get advice and code samples. Community is what made Macromedia great, but looking at those newsgroups today, the community sounds like they are feeling like Macromedia has left them high and dry. Now, I gave up on Macromedia Tech Support years ago, and it was chiefly because it cost me money to actually get help, and it rarely got me anywhere.
Rick Segal made a posting last week that encapsulates just how out of touch Macromedia is right now. It's worth reading to see how treating your community poorly can be exacerbated by limiting your openness with and transparency to that community.
At this point, I get what I need out of MX 2004, and until I see a compelling reason to upgrade, I won't. Instead, I'll be looking a lot harder at the competition, which believe it or not could be Microsoft with the addition of Sparkle and Acrylic. Visual Studio 2005 Express for Web Developers is also going to be a real player if Microsoft can do a better job at getting the word out.