post

Macromedia Shwag

Macromedia Shwag: I haven’t been icluded on this because I have never attended a Macromedia event like Max or TodCon or any other but, since I’ve participated in several betas in the last few years I have received a few Macromedia items:

  • 2 car visor CD holders
  • 1 small travel alarm clock with the Macromedia logo on it
  • 1 great looking notebook

It’s not much but I though I’d share anyway… ;-) I’m really jealous of the people who got t-shirts, caps and stuff to wear because I would wear them proudly myself. Maybe I’ll finally get one of those before the Macromedia name disapears…

post

Adobe, Macromedia & Fireworks

There has been a lot of discussion in blogs and newsgroups following the recent closing of the transaction for the acquisition of Macromedia by Adobe. I have been reading a lot about it in the last few days, official words and commentary alike and there’s one thing that’s really been bugging me in many of the coments I’ve seen.

There’s a lot of people who seem to be confused about what Fireworkis is or what it can do. They speculate that Fireworks is doomed because it’s not as “strong” as Photoshop or worse, because it “competes” with ImageReady. Both statements are dead wrong.

First of all, Fireworks is fundamentally different in nature than both Photoshop and ImageReady as it is a true vector based application (not a raster application with awkward vector features tacked on like Photoshop…). Fireworks’ bitmap tools indeed do not have the depth of Photoshop’s but it doesn’t have the same purpose either. Fireworks was designed for the creation of Web graphics only. It does not have Photoshop’s print heritage. There is really no direct comparison between the two apps other than they their sharing some functionality and both are used to create Web sites graphics (although I really can’t think why anyone would subject themselves to the tedium of laying out a Web site in Photoshop…).

Secondly, comparing Fireworks with ImageReady makes even less sense despite what many people seem to think. ImageReady is really nothing more than a glorified slicing, optimizing and exporting tool and while those tasks are certainly part of what Fireworks does they’re only a fraction of its functionality. Fireworks is first and foremost a creative tool whith which you design site layouts and graphics, not a mere “slicing and dicing” tool used after the “real” work gets done in a more sophisticated application like Photoshop or Illustrator.

With Fireworks there is no middle man, you create then slice then optimize and preview graphics right within the same integrated and efficient interface with precise and flexible vector as well great bitmap tools. Regardless of the innacurate information some are spreading about Fireworks and beyond all the speculation surrounding the acquisition and plans for specific products, I choose to hope that Adobe will be smart enough to recognize the unique nature of Fireworks and keep it around and develop it further. Fireworks really should have a future and deserves better recognition than what it got under Macromedia’s inept marketing efforts on its behalf…

post

MXDJ on Adobe vs Macromedia

The April 2005 version of the MX Developer’s Journal (www.mxdj.com) was released yesterday and I just had a peek through it. About the entire first half of the issue was devoted to the recently announced acquisition of Macromedia by Adobe and I have two problems with that.

First. Until the acquisition is official and approved by all concerned parties, no one will know what this entails for the direction of the new augmented Adobe or the future of existing products from either companies. Any discussion on those issues is pure speculation at this point and as a MXDJ subscriber, I would expect the magazine to offer real content to its readers and not 22 pages of pure conjecture on a situation that is still up in the air.

I usually look forward to every new issue of the MXDJ because its content is usually informative, useful and practical. The first half of the April issue is none of that. The acquisition is very big news in our industry so I didn’t expect the MXDJ to completely ignore it but, until the transaction becomes official and actual announcements are made about the larger company’s direction or specific products’ future, a simple editorial would have been enough IMO. I didn’t appreciate having half the issue “wasted” on this topic but then again, this is somewhat a minor issue.

Secondly, and what is even more problematic for me is the tone and content of the actual articles. I had the distinct impression while I was reading them that I was being subjected to an exercise in spin because of all the comments beingso one sided and positive. Don’t get me wrong, I am a very optimistic person by nature and this acquisition might be the greatest news ever for existing Macromedia customers in the end, but we just don’t know enough yet to have an informed opinion and pass judgment on the transaction.

But that’s not the main thing. My point is that there are real issues of concern surrounding this transaction and MXDJ chose to gloss over any potential negative effects on existing customers of both companies but especially Macromedia customers. Without falling into wild speculations about the future of specific products myself, the main concern I have at this point is about the difference in corporate cultures between the two companies. Why should that be cause for worry? One of the most level headed and compelling comments I’ve read on the acquisition is this blog entry by John Gruber at Daring Fireball. Go read it, I’ll wait.

That blog entry really hit home for me. After the acquisition, Macromedia’s company culture is at best bound to be heavily diluted and at worst it might completely disappear. Adobe is the larger company here and the one doing the buying so its decision makers will certainly have more say in the direction of the post acquisition corporation and that worries me, no matter what positive spin the Macromedia community pundits try to put on the news.

post

More On Adobe vs Macromedia…

I’ve been reading quite a bit about the recently announced Adobe acqusition of Macromedia and, beyond all the speculation about the future of specific products, the one thing that’s starting to hit me hard is the disapearance of the Macromedia brand.

Many people speak of this as a merger but it is not a merger, it’s an acquisition of a smaller company by a bigger company and it has very different implications than a merger. When and if the deal goes through, the Macromedia brand will disappear for good and only Adobe will remain. One of the things I’m afraid of is that the company culture of Macromedia might disappear with the name and brand and to me this is very bad news. Few software vendors have instilled in me the kind of loyalty that Macromedia has and certainly no other companies of such a large size.     I not only love their products but they have an openness towards their customers that is unrivaled in the industry IMO. Almost all of their key employees have blogs and keep open channels of communication with the user community. There is no such openness at Adobe that I can see. What I hope is that some of a lot of Macromedia’s corporate culture seeps into the new Adobe…    

The second thing that bothers me about this acquisition is that Adobe is a company that so obviously does NOT "get" the Web. That’s probably why they are buying Macromedia who’s the undisputed leader in Web design and development tools as well as RIAs and online user experience with products such as Dreamweaver, Flash, Flex and ColdFusion. I know that Adobe is not stupid and we can only hope that they come to rely on the human resources expertise of the company they just bought to make decisions about future product development.     What I really hate is having to wait to see how things evolve without knowing if my main software tools will survive the process.

post

The Day After

I’m posting this both as a test as I’m trying to resolve some problems with my blogging software but also to post a link to a good summary of reactions and official statements about the pending Adobe-Macromedia merger announced yesterday. Jason Kottke has posted this summary and I wanted to link it here so that I can come back to it later.