Live data from Hacker News

Adobe is going to kill Fireworks

twitter.com

31–40 of 107 posts

Re: Adobe is going to kill Fireworks

#31
post #6

I can't believe this. Photoshop is not meant for web design, we only have Fireworks for the task. A simple task like selecting a layer in Photoshop makes me want to cry.

Right-click to get a list of layers under your pointer. Or you can set a preference that click on an element automatically selects that layer in the layer palette. This makes you cry?

Re: Adobe is going to kill Fireworks

#32
post #5

What do people use Fireworks for?

I like Fireworks for rapidly prototyping designs. I don't really use the slice/export feature, but for prototyping before committing to code, Fireworks works perfectly for me. I've been using it for over 10 years now and have become extremely quick and comfortable in it.

Photoshop never felt right to me for doing prototypes that eventually iterate into an actual design spec. I need to crack open Photoshop a few times a year. I'm in Fireworks almost everyday. I'm sure a lot of it is my muscle memory, but for many of my graphic and photo editing tasks, Fireworks is so much faster.

Unfortunately, Fireworks has become less intuitive as its evolved and I suspect it's lost a lot of its luster to new users. Even though I'm only using Photoshop a few times a year, I still need to keep it around.

I suppose this change by Adobe will force me out of an old habit, but I'm looking forward to exploring some non-Adobe options.

Re: Adobe is going to kill Fireworks

#33

I see more people writing about how they are using Illustrator to design sites now than Fireworks/Photoshop. Claiming that it helps design responsive sites better/more intuitively. I haven't used Fireworks for years. Once you are proficient in Photoshop, I rarely found a reason to open Fireworks even given all of its benefits.

I don't really like this approach. Don't do web design in Illustrator, do it in HTML5 + CSS3. Sure, it might take a little longer at first, but the time saved over a longer time frame makes it worth it in so many different ways.

Instead, graphics software should be used for elements in the layout rather than the layout itself.

It turns out that positioning is quite orthogonal to colour. Borders are orthogonal to textures. Sizes are orthogonal to form design. Not entirely, but that's, in the first instance, how they should be formalised before further dependencies.

It is in combining them that we find beauty. And CSS3 is a far more suitable way of doing just that in a considered fashion than Illustrator could ever be.

Re: Adobe is going to kill Fireworks

#34

This doesn't mean the software cannot be used anymore, right?

Not immediately, but once a software product is killed, you won't get updates for future Operating Systems, no security updates, no support for new file formats ... eventually it just dies a death of time decay.

Re: Adobe is going to kill Fireworks

#35
Our 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 PaintCode (our app for Mac and iOS developers), which makes it very nice for user interface design.

Re: Adobe is going to kill Fireworks

#37
Fireworks is the only Adobe product I use religiously. I never understood why it didn't take off with the web design world. I believe it to be the most intuitive of the bunch.

Simple things like copy/paste work like they should, and whereas PS might be more robust, it takes 2-3x more clicks to achieve what FW can do in just a few.

Re: Adobe is going to kill Fireworks

#38

Often 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.

i'm the complete opposite. i latched-onto macromedia fireworks before adobe bought it up (probably because i managed to get it for free¹) and have never been able to comfortably shift to photoshop..

i get the sense that you can achieve very similar outcomes using either one, but just always preferred the way you do so with fireworks over photoshop and similar programs. i’m not too savvy in the design space, but would appreciate any insights into the differences between the two, particularly as it relates to workflow.

¹ should note that while i initially gained exposure to the program via less-than-legal ways, having since grown up i am now a happy paying customer. i imagine this experience is quite common and this type of exposure a net benefit to companies like adobe.

Re: Adobe is going to kill Fireworks

#39
I've never really been able to solidly get into Fireworks, despite trying several times. The fans love it, but I've personally found it very clunky.

However, a colleague swears by it for designing and developing HTML email newsletters. The general state of support for HTML and CSS in email clients is extremely poor, so you have to use inline styles and table-based layouts. Fireworks is perfect for this.

Post reply on HN