Macromedia never really got (some of) Macromedia tools either. I used to work on Fireworks. I don't mean I was using it; I was building it. It was always a red-headed stepchild, though. It went through as many near-death experiences as Apple, though the outside world never heard about it. It was the only product being built in Texas, a result of MM's strategy of growing by acquisition and spinning off products to avoid antitrust problems, and one day Macromedia closed down the whole office to cut costs and laid off everyone who wouldn't move to Silicon Valley. A few (very few) came up, but since they were now here in Tech Mecca, most no longer wanted to be on the career-limiting Fireworks team anymore. People on other teams doing cosmetic cross-product UI synchronization gave Fireworks the same cosmetic makeover to make it appear to still be alive, so upgrades were sold, and eventually it gathered a few new devs and muddled through.
It always had a passionate user base, which was always very small. It, like a font editor, a sound editor, and several other products that were canceled just didn't belong in a big company, but it always just barely survived the "product layoffs"--but just barely. My guess is that the CTO, Kevin Lynch (now at Apple) was personally fond of it and wouldn't let it die but couldn't afford to feed it or pay any attention to it, either. It should have been given to a small, lifestyle software company that would have loved it, cared for it, and lived well off its meager sales.
The big problem was that the Web devs who paid for software always had Photoshop, and most assumed that anything that Fireworks could do, Photoshop could, too, so why buy and learn another photo editor? Before they acquired Macromedia, Adobe always used to spread this FUD, and after the acquisition, they couldn't afford to say anything different about such a small product.
Oh, well. This is now an opportunity for someone much smaller than Adobe to create Fireworks II for that small, passionate market.