Adobe buys Macromedia.

Posted April 21, 2005

Rothe Blog Macromedia Adobe Join Forces

What a bombshell!

Somehow I managed to be suprised, to the point where I couldn’t explain why I felt sick, and my heart was racing.

Adobe buying Macromedia? But yet, we live in an industry where the shelf life of certain electronics has a maximum of ten years, and that is always shortening. Change is inevitable, I just never would have guess this. Not in a million years. But when I read the stats, I guess it made more sense.

Last year, I read that Macromedia made somewhere in the neighborhood of $370 million. Pretty darn good. But low. Adobe, who owns the print industry, I figured would be a little higher. But to the tune of $1.7 billion in revenue? Wow! That is quite a difference between two companies that I figured were on a level playing field.

When the merger was approved by both boards late Monday, they released statements that involve vague plans on what will be done when the moguls combine, like increasing support for development on a wireless environment and how stockholders came out of the deal. If you want, go and read Macromedia’s release or Adobe’s release. Either way, I was sick to go to Macromedia’s site and see the Flash banner there, which I posted above, about the two “joining” forces.

But obviously my biggest concern, is what will happen with the software. Nothing. At least not for awhile. The merger should wrap up in the fall, like the press release claims.

Adobe does print. But they design their layout programs for web, like print is just like web. And it isn’t. It is all about drag and drop for Adobe, making this poorly coded websites, and it makes me nervous. Let’s run down each program.

Adobe Illustrator vs. Macromedia Freehand

I use Freehand heavily because you can trace something really quick, copy, and drop it into Fireworks, no problem. You can’t do that with Illustrator to Fireworks. But, I will say hands down, that Illustrator is a better program because it is broader and facilitates print better. I have had my problems trying to create complex documents in Freehand for print publications.

Verdict : Adobe WILL drop Freehand. It may incorporate some of it’s automated vector creation tools into Illustrator for the web, but I wouldn’t hold my breath. Will I lament this change? Only briefly.

Adobe Photoshop vs. Macromedia Fireworks

This is not really a logical matchup. Photoshop is this amazing program that you can never learn enough about, it bounds are limitless. Fireworks, is geared specifically to making webpages, and it is an awesome program. Editable raster graphics, easy export options, everything you need to pump out something fast. Photoshop feels just like the situation it was in, an awesome program that had to go back and work in Web tools that just aren’t as easy, and don’t make as much sense.

You may be able to create more detailed masterpieces in Photoshop, so in that case, you should, and then bring them into Fireworks and incorporate them into your design. But these are seperate programs with only a handful of overlapping ideas. Both do their jobs in a great way, and are geared at seperate things.

Verdict : Adobe WILL do away with Fireworks. This is what I fear. They shoudn’t. They should just make it better for web prep, and take all the web crap out of Photoshop, or stop adding more to it. This will be a long change though. I fear they would piss more consumers off by completely ditching this product sooner than later than they would with Freehand. I just hope that if they incorporate it’s features into Photoshop, they make it just like Fireworks.

Adobe GoLive vs. Macromedia Dreamweaver

Dreamweaver has a stranglehold on the market, and this will be an interesting battle to say the least. How long do they develop for both? Do they make their decision swift and just piss everyone off now, or piss them off later?

I have seen GoLive’s capabilities in demostration on the CS Tour. I have even thought about switching (which may now, not be a choice) because of some of the neat features, like zooming in on a layout in development, and making a PDF of the layout in development. Having said that, they claim great support for CSS layout, but that is only if you use “layers” not write div tags from scratch. There is no GUI in GoLive to do that, nor Dreamweaver, but at least Dreamweaver claims display support, not a full CSS building machine. Golive also adds all this extra commented crap for those developers who embrace their drag and drop ideals.

From InDesign to Illustrator, you can drag your layouts into GoLive, and it will insert exterraneous commented code so that the two programs can communicate. Granted you can take that out, everytime you put it in, but then you can’t update the source file and have it make the changes automatically. So a double edged sword that has me asking, “What is the damn point.” Stop making a tool for hack print designers just to offer a crappy service and flood the internet with bloated page design.

Verdict : I just don’t know with this one. I hope they drop GoLive and add all of their good standards compliant type ideas to Dreamweaver. You have to hope that will happen, as the brains behind Macromedia are coming over to Adobe. But the idea of Adobe keeping Dreamweaver just doesn’t seem likely either, so this will be the matchup to watch.

However, not everything is bad and horrible.

Now, all doom and gloom aside, I am pretty pumped to see what they will be able to do with the new Adobe Flash (God that hurts to say that) integrated with the awesome capabilities, and platform independence of PDF’s. I have seen how you can incorporate Flash in PDF’s and I think it is amazing.

Plus, now that I have had time to set, I am a little excited to see what they can do for wireless development, as I see that as a highly technical market, and Adobe does have a way of making everything a little more graphical and user friendly when it comes to development.

Either way, a landmark in my career. I will probably always look back on this entry and laugh, and talk about this as one of my design “war” stories. But only time will tell what they future holds, and I will be right here, to comment on it when it does.