When you say you're 'not able to try MX 2004', enkidu- I assume you're referring to specific problems you've had with the demo version that prevents you from trying it? Obviously the demo's been available for a while now.
As for the reception of DMX 2004, troll around for the reviews- there's many already posted on all the major sites. Sure, I've heard of people having problems with 2004 (complaints always arise faster than kudos- just a fact of the industry), but I've also seen and heard lots of people who aren't having much if any issues with it either. Not to downplay any problems you're having, just giving both sides of the coin here. You may not agree from your personal POV (and I respect that), but it is the case.
As for 'fixing DMX before releasing a new version', I can offer a few insights. For one, there is no such thing as a bug-free software product, from any vendor. Software is always susceptible to environmental differences, third-party conflicts, the list goes on. No software company could make the claim of shipping 'bug-free software' with a straight face. Problems, always arise, and as OS's/third-party tools/utilities are updated, there's always the potential of future unforeseen conflicts as well.
Secondly, the 6.1 updater was released to address the most prevalent and commonly-reported issues with the MX release, and if some of your specific problems weren't addressed in that update, then I do apologize. This can be a double-edged sword, though. If a product team concentrates only fixing every isolated issue they hear about with every release, you have no traction towards new features/functionality. The product stagnates, and realistically, still will never reach the point where every user on every configuration of every OS/platform can say, 'hey- I can't find a single thing wrong with this product anymore'. It's a fine balance to be sure- and honestly, no point of balance will ever satisfy both sides of this argument.
For each release, however- we do make the top issues that are being identified publicly via an 'emerging issues' technote (along with any solutions/workarounds that we may have to accompany them). Sure, this isn't a patch, it isn't an update, but it does give you an idea of what the most frequently-reported problems have been and which of those we can in fact reproduce and verify consistently. Obviously if and when a patch is released, these are the top issues we're looking at for it.
Current 'top issues' technote:
www.macromedia.com/support/dreamweaver/ts/documents/emerging_issues.htmMuch like with product releases, however- we can't talk about patches or updates until they're a known quantity and on the fast-track to release. It's better to give firm answers than simply glad-hand everyone with false hopes of an update that may or may not solve all their problems. Hope you can appreciate the rather tenuous balance there as well.
I'm sure this may not answer all your questions, nor am I the right person TO answer all your questions, but I hope this at least gives a bit more human perspective on the situation, since you seem to have not gotten much individual response elsewhere, for what it's worth. Hopefully any followup to the interview that seems to have irked you will answer whatever questions are remaining.
best!
- Scott
scott fegette
macromedia, inc.
Problems
Impressions
