Live data from Hacker News

Ask HN: Is anyone still using Dreamweaver?

news.ycombinator.com

81–90 of 183 posts

Re: Ask HN: Is anyone still using Dreamweaver?

#82

No, no one is using it. It never was a go-to tool even back then. I feel old by just remembering it. Dreamweaver solved no one's problems. 1) Regular users didn't need it: they couldn't use it for publishing their web-sites anyway. They quickly just switched to social media for publishing their content. 2) Dreamweaver was not a great tool for professionals too. Its code editor was not convenient and overall the progr…

> It was never used in real work

Does this mean I need to return all my paychecks from 2004 to 2007?

Re: Ask HN: Is anyone still using Dreamweaver?

#84
post #80
post #24

Earlier quoted context omitted.

FrontPage Express was what I used to build my first website. (personal project with friends) I learned so much about HTML simply because of the limitations in FrontPage Express.

Same. I built a rockin Pokemon website with it when I was 9.

Awesome

Re: Ask HN: Is anyone still using Dreamweaver?

#85

Earlier quoted context omitted.

Microsoft Word's "Save as Web Page" or GTFO.

That's ironically still the easiest way to go for HTML emails as the output is almost guaranteed to display well across various email clients that don't implement CSS properly (Outlook).

IIRC Outlook[1] just uses the Word engine internally, so it's going to share the same quirks.

(I also seem to remember that Internet Explorer's Trident engine started as a fork from Word, although that's presumably a bit less direct in the later versions).

[1] At least proper desktop Win32 Outlook, not the dozens of other things Microsoft have called Outlook.

Re: Ask HN: Is anyone still using Dreamweaver?

#86
post #45

I like dreamweaver. But I could still code html by hand with HotDogPro. The one that I really miss is Macromedia Fireworks. The perfect mix between vector editor + html editor + OOP. And to think that it did all of that in the metadata of a binary format (png). Nothing has come close.

If you hadn't post this comment, I would have.

Fireworks could have been Figma, it could have been the default platform every designer used. But Adobe didn't understand it, they saw it as a weird Photoshop competitor and shelved it.

The last few versions bundled with CS were clearly neglected maintenance releases. I finally stopped using my slowing rotting copy in about 2014 when I got a Mac with a retina screen and fireworks was stuck with a terrible pixel doubled ui. :-(

Re: Ask HN: Is anyone still using Dreamweaver?

#87

Earlier quoted context omitted.

I did the same, except with Netscape Composer. That was a time where the output of the WYSIWYG editor - really, the source of any page - was pretty digestible, even to me as a middle school student. I've noticed recently that the JavaScript debugger in Firefox can "un-Webpack" (and in some cases un-minify, if I've read the inputs and outputs correctly) the code behind many sites. It's certainly not as approachable as…

I think it was Microsoft FrontPage that had the most undigestible output at the time. A mess of tables, inline styles, Internet Explorer-specific tricks, plus a reliance on FrontPage Server Extensions for full functionality. Adobe still had GoLive at the time, which was basically what Dreamweaver is now, and it didn't mangle the output as much, neither did Netscape Composer (which was way more limited). Many of the s…

FrontPage is what I made my first sites on as a child. That was such a fun experience.

Re: Ask HN: Is anyone still using Dreamweaver?

#88

Earlier quoted context omitted.

I did the same, except with Netscape Composer. That was a time where the output of the WYSIWYG editor - really, the source of any page - was pretty digestible, even to me as a middle school student. I've noticed recently that the JavaScript debugger in Firefox can "un-Webpack" (and in some cases un-minify, if I've read the inputs and outputs correctly) the code behind many sites. It's certainly not as approachable as…

I think it was Microsoft FrontPage that had the most undigestible output at the time. A mess of tables, inline styles, Internet Explorer-specific tricks, plus a reliance on FrontPage Server Extensions for full functionality. Adobe still had GoLive at the time, which was basically what Dreamweaver is now, and it didn't mangle the output as much, neither did Netscape Composer (which was way more limited). Many of the s…

I forgot if FrontPage had the automatic FTP upload or if it's a fantasy in my mind.

Re: Ask HN: Is anyone still using Dreamweaver?

#89

Earlier quoted context omitted.

Microsoft Word's "Save as Web Page" or GTFO.

That's ironically still the easiest way to go for HTML emails as the output is almost guaranteed to display well across various email clients that don't implement CSS properly (Outlook).

> email clients that don't implement CSS properly (Outlook).

Can anyone explain how this is even possible? It's 2025.

Post reply on HN