Live data from Hacker News

The Future of Adobe Fireworks

blogs.adobe.com

51–60 of 81 posts

Re: The Future of Adobe Fireworks

#51
post #44

It's weird they are killing this product because the existence of products like Sketch make it clear that there is a demand and a gap in the market for a good vector/raster tool for web design.

The existence (and ever increasing popularity) of Sketch can't be unnoticed at Adobe HQ. Therefore:

1. They're going to buy Sketch¹

2. They're about to release a new product that replaces Fireworks

3. They're going to have some version of Photoshop and/or Illustrator capable of the same things.

My guess? They're going to buy Sketch. If #2 was the case, it would have been demoed at Max. If #3 was the case, they'd have demoed at least some of those features at Max.

____

1. When I say 'Sketch', I mean it-or-something-very-similar

Re: The Future of Adobe Fireworks

#52

Earlier quoted context omitted.

I feel like Adobe never really got macromedia tools at all. They knew they wanted to own the content creation market, but they never really understood the developer side of the content creation game. Fireworks is the last Adobe tool I use these days and I'm disappointed they can never understand why someone like me would continue to use it.

Adobe's own online presence is a prime example of how they don't understand the web. Same goes for the decision to drop CS and continue with only their cloud-based services: they should've done that about 10 years ago. I can't remember for how long I've been saying I'd be willing to pay monthly for their programs if there only was such a subscription. And I'm not trying to brag there. I'm meaning to say that it's rid…

As a student, I still feel like their subscription model needs work. $20 a month is too much for a single application, especially when it requires a year-long commitment. $30 for the academic subscription is a good deal because it includes everything, but I only use a few of the programs. Again, this option requires a year-long commitment.

For an educational license, I'd gladly pay $10 for Photoshop. For a commercial license, I'd pay $20, but only if I could cancel at any time.

Re: The Future of Adobe Fireworks

#53
I knew this day was coming and yet I am still shocked. Fireworks is and always will be the best tool for wire-framing and web design, hands down. They've decided not to continue development of Fireworks and yet keep Dreamweaver? Dreamweaver is what I used for a period in my life when I was learning web development and you soon discover once you learn enough that it's horrible. I knew when Fireworks CS6 came out and Fireworks was neglected in the features and bug fixes department that it was only a matter of time.

Adobe is somewhat dead to me now. I'll continue to use Fireworks until it stops working completely and once it does might consider running a VM with a version of Windows that supports it. It's time for the open source community to step up to the plate and create an open sourced version of Fireworks, heck it would be amazing if Adobe open sourced Fireworks so us die-hard users who see its potential and power continue to make it better and keep it alive for many more years to come.

This wouldn't be such a bad thing if Adobe had another product like Fireworks, but they don't. Illustrator sucks for web design, Photoshop is too slow and bulky for agile web design or prototyping and the range of new applications Adobe has been bringing out don't really impress me in the slightest. The only way I can see Adobe from recovering from this is implementing some kind of way to load Photoshop in a "web mode" that gave you a similar interface as Fireworks but even then what about the features that make Fireworks so great? Pages, Master Pages, Styles, ability to click and drag elements around the canvas, Search and replace colours and fonts...

This is a very bad move. Those who say it's not a big deal have obviously never used Fireworks nor used it long enough to truly appreciate just how great of a tool it is. This one particular line in the post really grinds my gears, “We understand that Fireworks has one of the most passionate communities on the web” — obviously they don't understand at all, if they understood they'd see there is a following for Fireworks. Judging by the comments on the post (and they keep on coming) everyone agrees this is a bad move, I didn't see one comment that agreed this was the right thing to do. This is an attempt to move users onto newer web tools which in my opinion don't come anywhere close to the simplicity and power of Fireworks and most likely never will.

Fireworks was Adobe's only decent UX design tool and now I hope someone else see's any opportunity here to woo a very large number of Fireworks users who will be more than willing to pay for a decent and viable alternative to a very loved tool with a cult-like following.

It seems like Sketch from Bohemian Coding is the only decent Fireworks alternative that's out there and it's Mac only. You could use Gimp but we all know Gimp is far from a professional alternative to anything. This is a sad day for me and a lot of other people.

Re: The Future of Adobe Fireworks

#54
post #4

My first copy of Fireworks I bought when it was still owned by Macromedia and it was wonderful; so powerful yet easy to use. It was my impression that Adobe never really "got" it, or knew how it should exist in their ecosystem as a sort-of competitor to their other products. It was sad watching it flounder, but I wonder what Adobe could've done differently.

Sadly, all of Macromedia products didn't have place in ADobe ecosystem except Flash. Fireworks, Director, and my favorite Freehand. FH11, we had so much fun and productive times together! Only did I switch fully (mentally) to Illustrator with CS4.

Re: The Future of Adobe Fireworks

#55
post #4

My first copy of Fireworks I bought when it was still owned by Macromedia and it was wonderful; so powerful yet easy to use. It was my impression that Adobe never really "got" it, or knew how it should exist in their ecosystem as a sort-of competitor to their other products. It was sad watching it flounder, but I wonder what Adobe could've done differently.

Sadly, all of Macromedia products didn't have place in ADobe ecosystem except Flash. Fireworks, Director, and my favorite Freehand. FH11, we had so much fun and productive times together! Only did I switch fully (mentally) to Illustrator with CS4.

As a long time Flash and Director user before going Unity, Director was dropped by Adobe the day it was bought. It has been on EOL since the aquisition. They had the lead on 3d on the web then and they let it slip. There have been no real updates to Director since 9 when Macromedia still had a hand in it. The recent releases were just to make people think it was still alive, no big loss except for Adobe and market share.

Freehand was awesome and Fireworks will be missed, it's too bad Macromedia did get bought by Adobe really, things would be so different. It was great for competition and Flash would have gone native and hardware accelerated much earlier.

Re: The Future of Adobe Fireworks

#56
post #4

My first copy of Fireworks I bought when it was still owned by Macromedia and it was wonderful; so powerful yet easy to use. It was my impression that Adobe never really "got" it, or knew how it should exist in their ecosystem as a sort-of competitor to their other products. It was sad watching it flounder, but I wonder what Adobe could've done differently.

I feel like Adobe never really got macromedia tools at all. They knew they wanted to own the content creation market, but they never really understood the developer side of the content creation game. Fireworks is the last Adobe tool I use these days and I'm disappointed they can never understand why someone like me would continue to use it.

Macromedia was bought more because of it's foray into the mobile space. This is back when adobe still considered Flash Light to be a viable path.

Re: The Future of Adobe Fireworks

#57
post #7

I'm a bit confused that they kept Dreamweaver but killed off Fireworks. No web designer I know even uses Dreamweaver anymore, but plenty of people still use Fireworks. Odd decision by Adobe here.

Many Coldfusion developers use it, can't imagine many others do but perhaps I'm wrong.

Anecdote here: I'm a CF dev (shudder, I know) and everyone on my team hates Dreamweaver.

In fact, Adobe has an IDE called ColdFusion Builder (we don't use it though), so I have no idea who still uses Dreamweaver: http://www.adobe.com/products/coldfusion-builder.html

Re: The Future of Adobe Fireworks

#58
post #57

Earlier quoted context omitted.

Many Coldfusion developers use it, can't imagine many others do but perhaps I'm wrong.

Anecdote here: I'm a CF dev ( shudder , I know) and everyone on my team hates Dreamweaver. In fact, Adobe has an IDE called ColdFusion Builder (we don't use it though), so I have no idea who still uses Dreamweaver: http://www.adobe.com/products/coldfusion-builder.html

I did CF over a decade ago, I remember this: http://nowostey.net/uploads/posts/2010-01/1264151016_84f0bc9... was one of the first things that I really liked that was killed by the Allaire -> Macromedia -> Adobe mergers. I'm not sure if I can blame adobe for that as Macromedia just left it to die.

Re: The Future of Adobe Fireworks

#59
post #52

Earlier quoted context omitted.

Adobe's own online presence is a prime example of how they don't understand the web. Same goes for the decision to drop CS and continue with only their cloud-based services: they should've done that about 10 years ago. I can't remember for how long I've been saying I'd be willing to pay monthly for their programs if there only was such a subscription. And I'm not trying to brag there. I'm meaning to say that it's rid…

As a student, I still feel like their subscription model needs work. $20 a month is too much for a single application, especially when it requires a year-long commitment. $30 for the academic subscription is a good deal because it includes everything, but I only use a few of the programs. Again, this option requires a year-long commitment. For an educational license, I'd gladly pay $10 for Photoshop. For a commercial…

Fair enough, but at the very least, $20 (or even $60) a month sure beats the hell out of paying $2000 in one go, in my opinion.

Or to put it the way Adobe should've thought of it:

Assuming $50 a month (I pay more atm) over the 10 years since I quit school, Adobe could've made 6000 dollars on me.

Instead, they made 0.

(up until they launched creative cloud, that is)

Re: The Future of Adobe Fireworks

#60

Earlier quoted context omitted.

I feel like Adobe never really got macromedia tools at all. They knew they wanted to own the content creation market, but they never really understood the developer side of the content creation game. Fireworks is the last Adobe tool I use these days and I'm disappointed they can never understand why someone like me would continue to use it.

Adobe's own online presence is a prime example of how they don't understand the web. Same goes for the decision to drop CS and continue with only their cloud-based services: they should've done that about 10 years ago. I can't remember for how long I've been saying I'd be willing to pay monthly for their programs if there only was such a subscription. And I'm not trying to brag there. I'm meaning to say that it's rid…

>Same goes for the decision to drop CS and continue with only their cloud-based services: they should've done that about 10 years ago. I can't remember for how long I've been saying I'd be willing to pay monthly for their programs if there only was such a subscription.

How is that a substantiated argument?

Tons of people say otherwise -- that they won't go with this new model.

And 10 years ago (when nobody was doing it, so it was even more alien, and internet speeds were lower) a lot more people would have hated it too.

Post reply on HN