This made me realize how much I miss Freehand which was way better and easier then AI. Now Adobe kills another superior piece of software made by Macromedia. On the other hand, Flash still lives strong. Go figure.
Adobe is going to kill Fireworks
61–70 of 107 posts
Re: Adobe is going to kill Fireworks
#62Often times I feel like I'm in the minority, but I rarely use Fireworks for anything. Perhaps I'm just more comfortable in Photoshop, but I often found that Fireworks didn't fit my workflow. I've read a ton of articles on how/why I should use Fireworks for web design. Perhaps somebody could inform me on what I'm missing.
Re: Adobe is going to kill Fireworks
#63Could Inkscape advocate Adobe to let Fireworks live to help SVG grow?
Re: Adobe is going to kill Fireworks
#64The perfect combination of vector and bitmap editing. I love Fireworks. My guess is that Adobe just couldn't figure out how to make it better. It was already pretty much all it needed to be by about Fireworks MX. And it remains, to this day, a very different codebase. User-friendly but quite powerful behind the scenes. I could never get the hang of Photoshop or Illustrator. Sure, Photoshop may have features or Illust…
Re: Adobe is going to kill Fireworks
#65We switched from Photoshop to Antetype company-wide now and we don't miss it (It's still here for Icon Design though). We also felt Antetype superior to Fireworks as it has ways do deal with dynamic layouts and prototypic interactivity.
Re: Adobe is going to kill Fireworks
#66The perfect combination of vector and bitmap editing. I love Fireworks. My guess is that Adobe just couldn't figure out how to make it better. It was already pretty much all it needed to be by about Fireworks MX. And it remains, to this day, a very different codebase. User-friendly but quite powerful behind the scenes. I could never get the hang of Photoshop or Illustrator. Sure, Photoshop may have features or Illust…
and i sort of saw this coming for a while now given its somewhat odd positioning in adobe's product portfolio (overlap with photoshop, illustrator) and the lack of meaningfully updates over the past few iterations (though, as mentioned, there really hasn’t been much room for improvement for a while..). i’ve looked for alternatives, but sadly, can’t seem to find anything suitable.. on the plus side though, i imagine current versions should be perfectly capable for some time to come.
it is sad day indeed though.
Re: Adobe is going to kill Fireworks
#67The perfect combination of vector and bitmap editing. I love Fireworks. My guess is that Adobe just couldn't figure out how to make it better. It was already pretty much all it needed to be by about Fireworks MX. And it remains, to this day, a very different codebase. User-friendly but quite powerful behind the scenes. I could never get the hang of Photoshop or Illustrator. Sure, Photoshop may have features or Illust…
Agreed. I can only assume that at least 50% of the people that use Photoshop only do it because they've never tried Fireworks (or have to, because everyone else does). Of course, that means Adobe is sort of competing with it's own product, so it was inevitable that Fireworks would disappear some day. To the best of my knowledge, Fireworks has no competitor or open source equivalent. If anyone is thinking about it, yo…
Re: Adobe is going to kill Fireworks
#68Will it help Inkscape? Could Inkscape advocate Adobe to let Fireworks live to help SVG grow?
It's probably fine for Windows, though.
Re: Adobe is going to kill Fireworks
#69I need FW way more than I need PS these days.
How's Acorn as a replacement?
Re: Adobe is going to kill Fireworks
#70Our new vector drawing app, WebCode, is a nice replacement for Fireworks: http://www.webcodeapp.com/ It generates CSS, JavaScript+Canvas and SVG code from your drawings in real time and can also import PSD documents. The generated code works great on both Retina and non-Retina displays. You can even preview how your drawings would look on Retina displays directly in WebCode. It inherited a lot of things from PaintCod…
Also, preferences aren't in the usual spot (under the Apple menu)?