Skip to navigation

PCPro-Computing in the Real World Printed from

Register to receive our regular email newsletter at

The newsletter contains links to our latest PC news, product reviews, features and how-to guides, plus special offers and competitions.

// Home / Blogs

Posted on March 5th, 2009 by Tom Arah

I’m sorry but Dreamweaver is dying

I’ve received a number of very kind emails regarding my last digital design column, but I have to admit that a couple made me feel slightly uncomfortable.

These were the emails from designers thanking me for pointing them in the direction of Dreamweaver when they were making the transition from print to web design. It was a decision that they had come to appreciate greatly over the years, providing them with the best possible platform for their web design careers.

dreamweaver is dying

The problem is that Dreamweaver is dying…

To be fair it’s not Dreamweaver’s fault. Nor is the problem Adobe and its development team – the last Dreamweaver CS4 version was the most impressive release in years. Moreover, although Microsoft Expression Web poses a far more credible threat than FrontPage could muster, Dreamweaver remains the best HTML/CSS page-based editor available.

The real problem for Dreamweaver and for its users is that the nature of the web is changing dramatically. Dynamically-generated web applications, from Amazon right down to the humble blog, all offer much more – in-built commenting, voting, RSS feeds, etc – than the best sites built on static HTML can ever hope to provide.

This isn’t a matter of bells and whistles, it’s absolutely fundamental. Ultimately a web site is all about content – posting it and making it findable – and Dreamweaver and the other static HTML editors have proven fundamentally flawed when it comes to these two core tasks (and features such as Dreamweaver’s libraries and templates are patches not solutions).

The bottom line is that the old model of the central webmaster hand-spinning every page of every website and, worse, manually adding the navigation necessary to help users find it, just isn’t scalable or viable. The only feasible course for the future is for content to be posted by the content contributor, whether that’s the site owner or site visitors, and for the best possible navigation to be constructed around that content on the fly.

In other words Web 2.0 isn’t an empty slogan, it marks a fundamental break with the past and Dreamweaver lies on the wrong side of it. So is this the end for Dreamweaver and the traditional Dreamweaver-based web designer?

Eventually yes. In the relatively near future every website will be a dynamically-generated web application and all of today’s sites built on multiple static pages will be ripped out and replaced.

The good news of course is that this is actually a huge opportunity – think Klondike gold-rush – for the web designer who can adapt. But how? After all your average designer is built along radically different lines to your average developer.

But it can be done. Just as Dreamweaver eased the transition for print-only designers to the new markup-based world of HTML; content management systems such as Joomla and Drupal can ease the transition for static Web 1.0 designers to the new Web 2.0 world of script-based PHP. Give them a chance and you’ll be amazed at what you can achieve and all without touching a line of code (that can come later just as it did with Dreamweaver).

I really can’t recommend this strongly enough. If you are a Dreamweaver user don’t bother upgrading to the latest version or exploring Adobe’s feeble attempts to graft end user content contribution onto Dreamweaver. Instead save your money and invest your time in getting to grips with the real future of web design: server-based content management systems.

Dreamweaver is dying. Long live Drupal.

Tom Arah


Well this article has generated a lot more comment than I was expecting (including on slashdot and digg) which is in itself a nice demonstation of web 2.0 in action and how Dreamweaver and static publishing in general is being left behind.

A lot of the comments are pretty much repeating themselves so I’m promoting the main points of an earlier response made below to try and clarify things and nip a few in the bud:

Comparing Dreamweaver and Drupal isn’t mad – they are both tools for producing websites.

Thinking about it I can see why people might assume they are entirely different – after all a cms is for producing a blog right? Absolutely not. You can reproduce any static site dynamically with a cms including simple and attractive brochureware sites.

Crucially you can’t do the opposite. This means that by using Dreamweaver you are denying your clients a lot of functionality – in-built commenting, rss feeds etc (only if you want them) – but most importantly end user content contribution and optimal on-the-fly navigation.

You’re also denying them the tag-based keywording that helps the search engines understand what your site is about. Google and cms go hand in hand and ultimately your job is to generate traffic.

Having said that it’s true that most cms sites currently do look and behave like blogs. More than that they look atrocious (most don’t even change from the default theme). There’s absolutely no reason why they should look so bad and that’s the other part of the equation and of my argument: current static designers have a lot to gain from cms but current cms also has a lot to gain from an influx of good design.

Clearly this post was aimed at the vast majority of Dreamweaver users – those designers producing static sites HTML page by HTML page. I wasn’t really addressing the developer and yes one of Dreamweaver’s great strengths has always been that it also caters for other languages and those developers manually building up their own dynamic sites.

And cms has even more to offer these users! Why reinvent the wheel and create your web application from scratch when you can take advantage of vast communal development effort that lets you achieve results that you couldn’t begin to dream of when working on your own?

Even with the fundamental shift to cms that I’m talking about there remains a role for an application to help users produce the cms logic and the CSS templates in the first place. And I’m sure a lot of the cms modules and most of the css templates were and will continue to be built in Dreamweaver.

But it’s precisely because these are then given freely to others to use and adapt that Dreamweaver becomes redundant for the vast majority of users. No one is going to pay for Dreamweaver with all its baggage if all they want to do is tweak a few lines of code. Especially as this is already more effectively done live in the browser.

Finally I carefully didn’t say that Dreamweaver is dead. To begin with, from some of the comments, it’s clear that there’s a lot of ignorance, inertia and self-interest to be overcome.

More importantly, as others have sensibly pointed out, these are early days and the cms options as they stand are currently only ready for early and adaptable adopters, not for the mainstream. You certainly shouldn’t expect to be able to switch instantly – I’m advising rethinking and retraining.

All in all Dreamweaver will be around for a while yet. However it used to be the dominant web force and the secret behind the overwhelming majority of professional web sites and it won’t be in the future.

The future for creating web design is in the browser not in Dreamweaver.


Unsurprisingly Adobe has a slightly different take on things and I’ve now added a follow-up post based on a chat with Devin Fernandez, senior product manager for the web products at Adobe


Still getting a lot of comments 6 months on. And with comment #264 it looks like I might even have persuaded someone to consider looking in to Drupal :-) In case anyone else is thinking about it, here’s the relevant part of my response:

“The article was primarily aimed at professional non-coding designers either starting out or recognizing that the world has moved on to web 2.0. Sadly it’s not a simple swap by any means (though things are getting easier).

However, if you are seriously looking to the future, I recommend taking a look at it – get a cheap BlueHost account and you can install it automatically and take it for a spin.

If you do, don’t judge it by first appearances (ugly and underpowered). Instead check out the add-on power available and get a better idea of what Drupal is capable of.

Essentially Drupal is harnessing the power of the data-driven web through the pooled efforts of a huge community of talented programmers meaning that you don’t have to code from scratch or even at all (though if you can that’s even better)

Tags: , , , , ,

Posted in: Real World Computing, Software

Permalink | Trackback

Follow any responses to this entry through the RSS 2.0 feed.

316 Responses to “ I’m sorry but Dreamweaver is dying ”

  1. Peter Bowyer Says:
    March 6th, 2009 at 9:12 am

    This post summarizes my experience exactly, but one cautionary plea from a developer and consultant: please have some understanding of web application security before you unleash unsuspecting clients onto Joomla and Drupal.

    Web applications need to be kept up to date with security patches, just like your computer does. We’re regularly called upon to clean, restore and secure hacked Joomla and Drupal websites – usually the problem arose because no updates had been applied since the site was built.

    Drupal and Joomla provide fantastic web 2.0 features, but with the extra power comes extra responsibility for you as the provider… please use it wisely!

  2. Simon Says:
    March 6th, 2009 at 9:47 am

    How about those of us who use Dreamweaver to write our own dynamic sites? I use Dreamweaver to speed up the development of my web applications and it works a treat. I write everything in code view and there are so many time saving tools in Dreamweaver, I believe that it would take me a lot longer if I used a simple text editor.

    I have been doing this for a long time, I’d never heard of Web 2.0 when I started. My clients just didn’t get it …. I would give them a CMS, tell them how to use it and still they would phone me up for any amendments! The CMS usually ended up as a tool to help me maintain web sites for my clients. This has changed. Now many clients may not know what a CMS is but they know that they want one and they are prepared to pay for it now … mostly!

  3. Paul Says:
    March 6th, 2009 at 10:10 am

    Don’t forget also that Joomla, Drupal, Expresson Engine and others do not allow for an undo. Make a mistake, delete something, and it?s gone. You keep backups of your data don’t you?

    Take from someone who has been moving a Freeway built site to Expression Engine: a web browser is not the tool to use to manage a web site. It may be OK for editing the odd text story, but if you are doing it day on day, you yearn for the desktop app experience with saves, undos and the ability to make a copy of critical files before undertaking something slightly dangerous.

  4. Tom Arah Says:
    March 6th, 2009 at 10:22 am

    Simon: I’d say that cms has even more to offer the developer. It just doesn’t make sense to reinvent the wheel. Take a look at the drupal contributed modules page and imagine how much work that represents – and it’s all yours ready to adapt where necessary.

    Paul: Moving to cms is definitely a paradigm shift and backup is crucial. However Drupal provides in-built versioning and with the Backup & Migrate contributed module you can schedule database backups.

  5. Tom Arah Says:
    March 6th, 2009 at 10:34 am

    Peter: Sorry – missed your post first time around. And couldn’t agree more. Backup and security are both critical – you need a backup system and you need to update whenever the new security release notice appears. Before cms can go fully mainstream the seamless handling of both aspects really needs to be moved into core.

    More generally I think that the time is right for professional designers to start making the shift from static authoring packages to cms but be professional about it ie don’t expect to produce public sites immediately. There’s a lot to learn.

  6. Alex Pepper Says:
    March 6th, 2009 at 3:47 pm

    You know what the funniest thing is?

    I still have to use FrontPage 98 to update an intranet site!


  7. Toby Champion Says:
    March 6th, 2009 at 11:33 pm

    Regarding undo: many CMSes, including open source products such as SilverStripe ( do indeed keep previous versions of page content in the database, allowing you to roll back as necessary, or view old versions and cut and paste. Meanwhile, of course, templates, code and other assets can be maintained in a revision control system such as Subversion (

  8. James Says:
    March 6th, 2009 at 11:49 pm

    What do you build your Drupal templates in? Not every site is going to fit some pre-made template. There are plenty of situations where a CMS is unnecessary and static pages do just fine, why add the overhead of Drupal for a landing page? There are plenty of holes for Dreamweaver to fill that have nothing to do with managing a site with global find and replace. Static sites have been going away for years now, becoming more modular since the first server side include. Besides don’t you prototype or test locally?

  9. SEKOconcepts - Blog » Blog Archive » Dreamweaver is… dead? Says:
    March 7th, 2009 at 12:07 am

    [...] Tom Arah explains how in his view, Dreamweaver is [...]

  10. Granville Says:
    March 7th, 2009 at 12:08 am

    As a drupal developer, I find that I like dreamweaver above many of the open source editors mostly because of it’s ability to show me the code and the visual result when i make changes. This is something that Drupal and other systems can’t really deliver, at least not yet.

    I’ve used notepad++ and I’ve seen Eclipse and Netbeans, but haven’t sued the latter two. I know that’ll I’ll be sticking with DreamWeaver simply because of it’s editing capability, but I image I’ll migrate to an open source editor if it can show me the results of html and css changes as well as DW can.

    I do agree that DW is on the downward slope, but I don’t think that many of us in the professional world will exclusively use the JS based editors that get integrated into systems like Drupal and Joomla until they just get more powerful.

  11. Don From Clover Content Says:
    March 7th, 2009 at 12:27 am

    I’m not sure Dreamweaver is dead, necessarily. I think you’re right that it’s dead as a site maintenance tool. But lot’s of people use it to create HTML pages and to translate designs into HTML.

    CMS templates as well as website builders are making it easier to create a site, but I think there are a lot of site owners who want a custom looking site and many templating systems have limitations in this area. Custom designs and flexibility are still of high value to designer/developers and Dreamweaver is the tool of choice in this area.

    So for site maintenance, yes, Dreamweaver is dying, but for creating sites, I think it will be around for a long time.

  12. Mixed Martial Arts Philippines Says:
    March 7th, 2009 at 12:33 am

    I’m kinda confused why is Dreamweaver (IDE) being compare to Drupal (CMS)

  13. bigyaz Says:
    March 7th, 2009 at 12:42 am

    MMAP nails it: You’re comparing two entirely different (but complementary) tools. This post suggests you don’t really understand Dreamweaver, and certainly haven’t taken advantage of many of its features.

  14. Says:
    March 7th, 2009 at 12:55 am

    @Mixed Martial Arts Philippines I Agree.

    If anything, Tom, you should have been comparing Contribute to Drupal and Joomla. And for my money, Contribute leave those two for Dead.

  15. foljs Says:
    March 7th, 2009 at 1:01 am

    I’m kinda confused why is Dreamweaver (IDE) being compare to Drupal (CMS)

    Because the guy is clueless…

    Tools such as Dreamweaver for EDITING code for web templates and dynamic behaviour (php, jsp, js, etc) will always be around.

    Drupal, as a CMS, only assists you in dynamically managing your content –this has nothing to do with building a web design and coding it, in regards to style and behaviour.

    The only way Drupal makes Dreamweaver obsolete is when you use a pre-built template (which defeats the whole point –and the pre-built template could as well have been built with Dreamweaver).

  16. Joe S. Says:
    March 7th, 2009 at 1:12 am

    I have to agree with the last two posts. You really need a clue. An editor/IDE like Dreamweaver/Eclipse is built as a development tool. Php and Coldfusion are server technologies that are languages of their own. And Joomla/Drupal are CMS systems. All very different. At some point a developer sat with a editor of some form to create every server technology or CMS. Heck I go as far as saying every program running today. Next time less buzz words and more depth.

  17. Zeke Weeks Says:
    March 7th, 2009 at 1:17 am

    I think you mistakenly see the decline of one use of Dreamweaver (publication and maintenance of static HTML-based sites) as the entire app’s downfall. The truth is that DW is a complete Integrated Development Environment that can be useful for several purposes – and, with CS4, the interface can even be adapted to suit different users’ workflows.
    Online CMS apps are publishing platforms – as are paper and static HTML, which DW happens to be able to edit. But to call Dreamweaver a publishing platform would be akin to calling a Swiss Army knife a screwdriver. Yes, many people only use it to publish content, but Dreamweaver was designed with a vast amount of capabilities that have nothing to do with content publishing. It is useful for web design – something beyond the aims of a CMS – and even database-driven dynamic web app development. I wouldn’t recommend it, but one could *create* Drupal or WordPress with Dreamweaver.
    Yes, static HTML as content management is dead. But until my web-based apps start making their own visual designs and application logic – creating themselves, essentially – I’m keeping my Dreamweaver, Expression Web, and Visual Studio around.

  18. deblitz Says:
    March 7th, 2009 at 1:19 am

    These last few comments hit right on the mark. I haven’t used Dreamweaver to build a website itself for about 8 years, but I do use Dreamweaver on a daily basis. There’s no better tool for converting your designs into HTML templates that will be fed into a CMS.

  19. Rex Says:
    March 7th, 2009 at 1:22 am


    Drupal has a revisions management feature. Others note that some other CMS packages do too.

    I moved from “hand built” to Drupal about 2 years ago. Getting good at customizing templates has taken a while. Now, even that is easier and getting more so.

    Note to that the Firefox plug-in “Web Developer” is indispensable in diagnosing and fixing CSS issues. Similarly, editors like Bluefish help a lot too.

    I’ve also seen a number of sites built using Dreamweaver that work well on IE6 but look terrible in Firefox. I suppose some of the trouble is that it’s usually a site built by a non-professional rather than the pros.

  20. Strangefish Says:
    March 7th, 2009 at 1:25 am

    Thanks for echoing what I’ve been saying for years. CMS is the future. It won’t be long before they provide the same type of experience you’d get from a desktop.

    Start with an existing template and customize, adapt, extend to your site’s requirements. Edit the CMS source code and write custom modules if you like. I like Joomla but Xoops is what I’ve used the most. I can’t recommend them enough.

  21. avitarx Says:
    March 7th, 2009 at 1:31 am

    All the comments about DW being obsolite are true to a point, but Drupal sets the bar for a good editor far lower. When making a custom template using a starting point such as Zen (template that is designed for customizing) there is not too much HTML editing to do, and with things spread out over dozens of little files, the WYSIWYG aspect is far less valuble. Drupal takes car of a lot of your JS too, dramatically reducing (if not eliminating) the value of the JS librareies.

    So what you are left with is fantastic (probably the best) CSS and HTML text editor, anfd a PITA site manager.

    Is DW worth it for the CSS editor (the part I find most useful anyway)? Considering that one needs Flash, Photoshop, Acrobat, and maybe even Illustrator anyway, DW is essesntially as free as Drupal.

    I would like to see Adobe expand it for working with CMS’s for sure, but even as is, it is a useful tool.

    I hope they integrate an AMP (and other server stacks) framework into it, so I can easily develope a CMS template (or even a django app) locally, and use an improved site manager to flip it up to a server. They could probably develope a plug-in architecture to allow for previewing the the whole page as you edit template files too. The plug-ins would trech it how to put together the files from a given CMS with either greeked text, or actual data from the local databse I would like ythem to incude as one edits.

    This WYSIWYG CMS templater is within their reach I believe, and would put them way ahead of simply being the best text editor available.

  22. Josh Says:
    March 7th, 2009 at 1:41 am

    I’ll admit I used Coffeecup and Dreamweaver 4 for far to many years, way past the release of MX, now granted I’m running both my companies and my personal blog site off of wordpress, but I still alter themes and page templates by hand. I will say that I could never imagine spending $$ for Dreamweaver though now that their are viable Open Source alternatives like Quanta+. You can’t beat an IDE when it comes to disseminating someone else’s code.

  23. David Singer Says:
    March 7th, 2009 at 1:41 am

    Dreamweaver sucks, always has, probably always will. If all you can do is point and click around a WYSIWYG editor then you should not be a web developer.

  24. Charles B. Says:
    March 7th, 2009 at 1:43 am

    I’m sorry to say your wrong about “Dreamweaver Dying” . It is not dying, and it has an enormous community which continues to grow and proves otherwise. The headline in this article was just used to grab peoples attention to read a post that is baseless, and inaccurate at best. Coming from someone who made a transition from print, to web design then onto web development, this software isn’t being hurt by the advent of cms applications like Drupal, or Joomla. Having built custom cms applications for companies, and state/local government. Hell I have even setup those services for my friends and used Dreamweaver to brand the design and layout of those services. I can almost guarantee Dreamweaver had a big hand in making those very applications your championing as the future.

    The only thing Mr. Arah has right is the less of a need for static website design. Yes it’s all going dynamic folks, but what he missed is the fact that web design is still required to customize those cms solutions. To build the templates that actually drive the brand and information your trying to convey to the end user. Not to mention those aspiring to go from web design to web development like I did, the tools are already in dreamweaver to start learning ASP.NET, PHP, ColdFusion, Java, and much more. These are the true technologies behind the cms revolution that your preaching. Dreamweaver is a great tool to unlock the best these cms applications have to offer.

  25. Arnold Miller Says:
    March 7th, 2009 at 2:00 am

    What an odd statement to say that Dreamweaver is dying.

    The CMS I use offers me multiple options – framework files, built-in WYSIWYG content editor, uploading HTML files made in Dreamweaver, etc.

    Of them all, I find the Dreamweaver route is the most used by contributors.

    Maybe it’s just that everyone else is using systems without a well-designed cache construct? I know I’ve certainly found Drupal and Joomla quite limiting in practice…

  26. Dreamweaver is dying. Long live Drupal. – Says:
    March 7th, 2009 at 2:04 am

    [...] pointed to this great article on the changing nature of web [...]

  27. JC Dill Says:
    March 7th, 2009 at 2:33 am

    This is a very timely post. I have been asked to “de-drupal” a site that was conceived as a blog, with posts and comments, but the creator wants it to sit as a static site, and not encourage new people to post comments (he wants people to email if they want to contact him). How do you deal with this problem if you keep the site in drupal?

  28. David F. Skoll Says:
    March 7th, 2009 at 2:49 am

    @JC Dill: You can convert a Drupal site to a static site by keeping it in Drupal, but turning off anything that allows modification by non-admin users.

  29. Jean Gazis Says:
    March 7th, 2009 at 2:52 am

    JC Dill: Dupal allows you to very easily fine tune user access to any functionality – turning off comments and unpublishing content is a matter of checking off a few boxes. You can allow unmonitored comments, managed comments, no comments, or add modules for custom workflows. If you “de-drupal” the site, what happens when the creator changes his/her mind again and wants to turn comments back on?

  30. j.k. Says:
    March 7th, 2009 at 3:31 am

    The onslaught of web 2.0 does not eliminate the need for a layout tool.

  31. Jim Caruso Says:
    March 7th, 2009 at 4:25 am

    I own CS3. I’m writing this from DrupalComn DC 2009. Enough said.

  32. James Smith Says:
    March 7th, 2009 at 5:05 am

    After 14 years in web design, I couldn’t agree more. But you left out the amazingly easy to use, and beautiful to develop, Wordpress. It’s simplicity + functionality as a CMS definitely puts it up there. My platform of choice.

  33. David Says:
    March 7th, 2009 at 5:20 am

    I also agree with the fact that this article is flawed. Dreamweaver is not dying, and to compare it to CMS tools is a little silly.

  34. Tim Thigpen Says:
    March 7th, 2009 at 6:22 am

    Such dichotomy misses the real opportunities, namely the continuous search for all possible solutions.

    I am a publisher self taught . We run a social site using Ning and a “static site” using Dream Weaver.

    Not a day goes by that I am not thankful I have access to both but do not have to rely on either.

    For our purposes we will continue to enjoy and leverage both for neither are perfect and right now somewhere someone is creating something that will blow both out of the water.

  35. ilter Says:
    March 7th, 2009 at 6:40 am

    “I’m sorry but Dreamweaver is dying”

    I think you are not sorry.

    And I think it is just like saying “html” is dying.
    It is a humongous editor with a lot of features. Maybe some of its features are too much for some people, but it is an editor.
    You might write e-mails to your friends, but when you want to write a book, you don’t keep sending yourself e-mails.

  36. Dreamweaver dying? | Says:
    March 7th, 2009 at 7:01 am

    [...] an interesting post here, author Tom Arah argues that because more and more new (and revamped) sites are blogs or other CMS [...]

  37. Boblin Says:
    March 7th, 2009 at 8:17 am

    LOL..Thats funny..last time I checked, most designers are using Dreamweaver to edit the very templates that Drupal uses….

  38. jacob Says:
    March 7th, 2009 at 8:35 am

    Does Dreamweaver not edit css, php or html anymore?

  39. Damion Says:
    March 7th, 2009 at 8:56 am

    Dreamweaver is dying. Its falling to textmate.

    I was a notepad fan for a long time, and when i met Dreamweaver it was heaven. As the abstraction moved to CSS, DW had a hard time keeping up. DW is just as great for dynamic as static sites. Its failure was its WYSIWYG – it wasn’t. I was a fan for years n years, but it just didn’t get the job done.

    Switched to texmate n cssedit, wouldn’t think of going back. DW really did its job for years (I used it everyday all day). Live preview, just invalidates DW.

    Drupal didn’t kill DW, the heavy lifting just went from DW to CSS.

  40. Christopher thomas Says:
    March 7th, 2009 at 9:12 am

    Dreamweaver is dying?? Good, go back to working in McDonalds and let the professionals do all the work, we’ll earn more money that way

  41. Dreamweaver is Dying -'s official Web Hosting Forum | Discussion on cPanel Linux Windows VPS and Dedicated Servers Says:
    March 7th, 2009 at 9:37 am

    [...] Dreamweaver is Dying Dreamweaver is dying possibly because the nature of the web is changing dramatically. "Dynamically-generated web applications, from Amazon right down to the humble blog, all offer much more

  42. robsta Says:
    March 7th, 2009 at 10:11 am

    Dreamweaver’s only failing for me is that I have to pay for it.

    Aptana / Eclipse offers almost as much feature wise and runs faster…. but I hardly use these now… it’s mostly direct off a webserver.. CMS Made Simple is my preference to Drupal.. as it offers online editing of templates, user defined php code, css and of course wysiwyg content. And I don’t have to stick to a ‘theme’ I can code any which way, and I don’t have to muck about ftping templates to the server if I want something different… add in the editarea plugin and you can syntax highlight php and html code…

    which means I can edit my entire site anywhere – just need a browser.

    That’s why desktop IDEs are dying … have you seen Mozilla’s online IDE…

  43. Rene Kriest ProBloggerWorld Says:
    March 7th, 2009 at 11:30 am

    I haven’t heard of any developer that he learns drupal to get the job done. Dreamweaver allows me to develop apps for Wordpress etc. I gonna try to build code for Textpattern and vBulletin via Drupal. ;)

    To me the author misses the point. I am a web designer/web developer and that means building feaure rich applications on the root of the system – and as far as I know the root of the web isn’t build on drupal. This is like saying that cars aren’t build from scratch but drop out from heaven to be sold to the buyer.

    When it comes to web design the fundamentals are still xHTML and CSS. Combine this with a little php and AJAX and there you go. CMS do exactly what the author denys: they provide static code. Developer and good designer go the other way. They build their apps from static to dynamic.

    This article provides no insights at all. Web 2.0 – the term is dying. That’s all.

  44. frank katzer | internetagentur ( fulda / petersberg) Says:
    March 7th, 2009 at 11:33 am

    sorry, but you missed a thing: web 2.0 will never enter corporate websites! a corporate website is not a mashup of rss-, twitter- and youtube-feeds. its about presenting services and products. you forget that there a millions of websites that are far away from being web 2.0 – and many features of web 2.0 would never fit to their website strategy…
    sure dreamweaver will not be the best editor for long – online apps, cloud-structures and other evolving technologies will rule web-developing in near future….

  45. Technocrank Says:
    March 7th, 2009 at 11:40 am

    Dreamweaver And Drupal Are Not In Competition…

    A little dis­cus­sion over at Slash­dot about this daft blog post­ing which claims that Dreamweaver is dying.  While the claims of the chang­ing nature of the web (2.0, AJAX, RSS) are valid, they don’t negate the use­ful­ness of a tool li…

  46. John Says:
    March 7th, 2009 at 12:32 pm

    I agree with most of the comments. This post sucks.

    I use dreamweaver with my php/mysql/ajax sites. I even used it for a facebook app recently. Why would you have to create each html page? You can create templates just as easy and use server side coding. I’m not sure I understand how you compare it to a CMS either.

    If you are using a CMS you could create a theme in DW. If you are using DW you could create your own CMS. I don’t see the logic to this post.

    Like others have said: You can’t compare a CMS to an IDE to programming languages. It just doesn’t work.

  47. OwenK Says:
    March 7th, 2009 at 1:26 pm

    Paul, have you looked into Subversion?

  48. Alister Cameron // Blogologist Says:
    March 7th, 2009 at 1:29 pm

    Drupal is too complicated.

    Long live WordPress!


  49. Dreamweaver is dead…Designing dynamic sites should be standard « Kungfuwit: Tech Writing FU Says:
    March 7th, 2009 at 2:29 pm

    [...] I’m Sorry But Dreamweaver is Dying [...]

  50. Paul McClean Says:
    March 7th, 2009 at 2:32 pm

    Dreamweaver, at the end of the day, is just a fancy text editor. Professional web designers use it for it’s awesome code-hinting, completion, search and replace…. not the visual layout tools. It’s one stage in the process of producing a dynamic web site in the same way that mocking it up in Photoshop first is. The author doesn’t seem to understand modern web development workflow. At all.

  51. Jon Says:
    March 7th, 2009 at 2:33 pm

    Dreamweaver won’t die until Adobe says its dead because they will always make it more economically sensible to purchase any of the Creative Suite Premium Packages instead of the apps a la carte or even the Creative Suite Standard packs,

  52. Kevin Says:
    March 7th, 2009 at 3:08 pm

    People that use Dreamweaver for visual layout creation should not be allowed to have websites. Professionals don’t use it because of its childish layout tools but rather because it’s a step above a simple text editor in terms of usefulness and web-specific tools. I’m sorry, but I don’t think Dreamweaver is dying, nor do I think you really understand how modern websites are actually developed.

  53. Julien Says:
    March 7th, 2009 at 3:21 pm

    Give the guy a break :

    he’s essentially telling people to stop focusing on “learning Dreamweaver” for producing static website.

    And he is right : A lot of beginners dive into Dreamweaver, trying and fighting to output static pages. They would better off learning what is a blog, RSS, the best CMS platforms, how they work, etc.

    Dreamweaver is not a “fancy” text editor. Dreamweaver is a bloated, big and old text editor, IMHO.

    I had to teach it to beginners, and it’s UI was really confusing for them. I suppose it’s incrementally better know that Adobe design it.

    PS : I like to do some CSS from time to time, and I gave up on CSS with Dreamveawer. I now use CSSEdit (It’s a fully dedicated CSS editor. Mac OS X only, clean, useful, light, live preview, etc. cheap too.)

  54. Steve Says:
    March 7th, 2009 at 3:22 pm

    Dreamweaver is alive and well in corporate America (what’s left of it anyway). I use Dreamweaver, textpad, & c# for Fortune 500 co sites. All tools have their strengths & weaknesses. It’s important to analyze a tool for its intended purpose.

    PS: Microsoft couldn’t create internet technology if it’s existence depended on it. Its idea of css is 1995 era Frontpage bloatware with just an iota less bloat. This is why I’ll never give up Dreamweaver. But, c# for the back end is not too bad.

  55. Dreamweaver muere. Viva Joomla « Tecnologia, Actualidad,y mucho mas…. Says:
    March 7th, 2009 at 3:22 pm

    [...] indican en PC Pro, esa tendencia a dejar de diseñar páginas y sitios web con aplicaciones como Dreamweaver ha [...]

  56. Drew S Says:
    March 7th, 2009 at 3:24 pm

    Since when is Dreamweaver only for creating static sites? I develop ONLY dynamic sites and I’ve been using Dreamweaver for quite some time. You should actually crack it open and try to write some code before you blog about it. The title of this blog should have been “I only create static sites and I use Dreamweaver”, then I could have avoided wasting 5 minutes of my life reading your blog entry.

  57. Robert H Hilley IV Says:
    March 7th, 2009 at 4:15 pm

    I only write static sites in dreamweaver but have found myself building more and more sites on Wordpress … its so simple and instead of needing to be at the office to update a site, I can do it from any web browser and/or my iphone :-)

    Good post!

  58. Eagle Hawk Design Says:
    March 7th, 2009 at 4:20 pm

    I disagree completely. First; I would say 75% of my clients do not want anything to do with updating their own sites. That’s why they have hired me. Second; I agree with Drew S, “Since when is Dreamweaver only for creating static sites?”
    You stated in your blog post: “Eventually yes. In the relatively near future every website will be a dynamically-generated web application and all of today’s sites built on multiple static pages will be ripped out and replaced.” I couldn’t disagree more. Yes dynamically-generated content will have a huge presence, but static sites will still be out there and necessary. Similar to CSS; sometimes, weather you like it or not, you do have to use a table every now and then.

  59. Dreamweaver is Dying? at Mike Conigliaro Says:
    March 7th, 2009 at 4:20 pm

    [...] apparently, Dreamweaver is dying. This article is interesting to me for a couple reasons. First of all, I’m happy that other [...]

  60. Adrian Says:
    March 7th, 2009 at 4:35 pm

    Sure, if someone will not develop, it will die!
    Adobe should dance with Open Source, let’s imagine below:

    Adobe purchases or donates the relative open source projects such as LAMP (although MySQL has been purchased by SUN Microsoft), and then adds them to web design toolkit to build fully web design environment so that people can easily build a dynamic web system by using it.

  61. Dreamweaver正在死去 - Jeff-Chen.Com Says:
    March 7th, 2009 at 4:42 pm

    [...] 一位Web开发者宣称Dreamweaver正在死去: 这既不是Dreamweaver的错误,也不是Adobe和开发团队的问题——事实上最新的Dreamweaver CS4还是给人留下深刻的印象。虽然微软的Expression Web对它构成了威胁,但Dreamweaver仍然是目前最好的HTML/CSS页面编辑器,但真正的问题是web正变得越来越动态化。动态生成的 Web应用数量远远多于基于静态HTML网页,如Joomla和Drupal之类的内容管理系统能很容易的帮助静态Web 1.0设计者转换到动态的Web 2.0脚本世界。所以Dreamweaver正在死亡,Drupal万岁。 [...]

  62. Paul McClean Says:
    March 7th, 2009 at 4:43 pm

    @Julien By “fancy” text editor, I meant (in the context that I use it personally) it’s just a text editor with extra bells and whistles. Something like Komodo Edit does everything that I need too, but DW just does it *slightly* better. It has the edge in that respect.

    I would love to see a ‘coders only’ version of Dreamweaver that did away with all the visual cruft and just concentrated on the code editiing capabilities. It would need to cost a heck of a lot less though.

  63. martin Says:
    March 7th, 2009 at 4:47 pm

    I think Adobe GoLive CS2 was the best editor on the market. That was untill Adobe bought Macromedia. From that day GoLive died. The focus on simpel webdesign was Adobe GoLives prime features.

    I work as a system consultan for the advertising industri in sweden. Many agencys still use Adobe GoLive CS2 to make websites. They find it to be the best editor in all levels. Why did Adobe kill this editor?

  64. megaman Says:
    March 7th, 2009 at 4:58 pm

    ugh, “web 2.0″.. is that term still being used?

  65. Dreamweaver is dying - Grand View Photography Says:
    March 7th, 2009 at 5:01 pm

    [...] I’m sorry but Dreamweaver is dyingInteresting article about how the web is changing, static HTML pages are soon going to be a thing of the past. [...]

  66. John Davies Says:
    March 7th, 2009 at 5:08 pm

    Wow, that is prety cool dude. Well done.


  67. Hussain Says:
    March 7th, 2009 at 6:40 pm

    C’mon DW can never die. I use DW 8 and im still highly satisfied with it!!!

  68. Rick Says:
    March 7th, 2009 at 6:47 pm

    I have found Movable Type to offer the smoothest transition from static to dynamic publishing. From a designer’s viewpoint, the templates can be designed like ordinary web pages, with tags to include the dynamic content. The pages can be published dynamically, statically, or any combination. Good online documentation and support. And its free and open source.

  69. Doug Holton Says:
    March 7th, 2009 at 6:51 pm

    Yeah we need to change how we teach web design, too. I’m revamping a web design course I’m teaching to include stuff using Drupal, for example, although we’ll still teach about HTML and CSS too.

  70. Brett Says:
    March 7th, 2009 at 6:53 pm

    It’s a scary article but true.
    Mark my words, Flex is the new King.
    I do not understand why more and more employers are trying to turn designers into programmers.

  71. DOGFACE Says:
    March 7th, 2009 at 7:13 pm

    “Dreamweaver remains the best HTML/CSS page-based editor available”


    Try Textmate or Coda and learn what you have been missing and weep over all that money you wasted on Dreamweaver

  72. Ian Says:
    March 7th, 2009 at 7:27 pm

    Any serious developer will want to write their own templates for a lot of these web apps… they’re still going to want a nice program to write them in.

  73. txoxy Says:
    March 7th, 2009 at 8:06 pm

    What you are really seeing is the failure of CSS to provide a full set of tools for creating interesting, creative screen layouts. As a consequence the Web is full of boring machine-generated pages that you elevate in importance by calling them “dynamic.” This is poop. You IT types are seeking to turn the creative work of a graphic artist into a sausage-making process where words are squeezed into boring, uniform templates. Ugh!

    Pick up a print issue of Wired or People or any other widely-circulated magazine and compare what you see to their websites. The websites are boring. The loss of quality is worse than what MP3 does to real music. But even worse than boring, the web sites are not generating the same kind of revenue as the print publications did. Heeding IT types has put the publishing industry into crisis. Money is evaporating. Publishers will fail if they don’t wise up and send you back to your machine rooms.

    I think that if you IT types really did rule the world, all our print magazines
    would be uniformly printed on fanfold greenbar in all caps. You need to be stopped DEAD! Long live DreamWeaver! And GoLive! And creativity!

  74. Anselm Bradford Says:
    March 7th, 2009 at 8:10 pm

    From my interpretation the point the author is making is that static web design is dying (with Dreamweaver just being a product representational of that kind of development). But I would point out the ability to create dynamic websites has been around for years and years (PHP heralds from the mid-90s), and during that time CMSs have been built with varying degrees of capability, and static web design has also remained. Drupal, like any popular open source project, has a strong community that drives it forward. Drupal 6 added features and fixed bugs of Drupal 5, and Drupal 7 will be the best yet (presumably). But this is constantly happening, software that’s worked on gets better. The important point here is not so much that static web design is dying, but that dynamic web design is thriving.

  75. Tom Arah Says:
    March 7th, 2009 at 8:26 pm

    OK. Too many responses to deal with individually – and a nice example of the difference between web 1.0 and 2.0 and how Dreamweaver has been left behind.
    Comparing Dreamweaver and Drupal isn’t mad – they are both tools for producing websites.
    I carefully didn’t say that Dreamweaver is dead. However it used to be the secret behind the overwhelming majority of professional web sites and it won’t be in the future.
    Yes I’m a designer not a developer but if Dreamweaver becomes a developer-only tool that’s dying compared to its former importance.
    Moreover, as I said above, the likes of Drupal have even more to offer the developer. Why do it yourself and reinvent the wheel when you can tap in to the extraordinary talents of an open source community?
    And, while it’s true that much of the code and templates might well have been produced in Dreamweaver originally, the whole point is that that means the average user no longer has to and will spend 99% of the time in the browser.
    Yes Drupal is a great editor, but are you really happy to pay $hundreds for the ability to tweak a preset CSS template, when the real content handling is free and open source?
    And in any case, as Rex points, out you’re better off doing that live in the browser too.
    Can’t quite believe that anyone could say that Contribute – an expensive proprietary solution that can only be opened to the workgroup – can outdo a truly open, browser-based cms approach. Based on the CS4 version and its own moves to end user editing in the browser, Adobe clearly doesn’t think so either.
    Yes you can switch off comments, rss etc and do apparently-static sites with cms. And if you’ve used tagging, they will benefit enormously from being automatically SEO friendly. Remember your prime job as designer is to bring in traffic.
    Of course most clients would prefer to update their sites if it’s simple, safe and free – it is with cms not with a static site.
    Absolutely agree with the point about design flair. Most Drupal sites are unbelievably ugly. But that’s because they’ve been produced by developers. I’m arguing that the time has come for any adaptable designer to embrace the largely code-free cms approach and to make it aesthetically as well as logistically beautiful.
    More generally a lot of the negative comments clearly come from keen Dreamweaver fans – a group in which I include myself – who feel under attack. That wasn’t what I was trying to do. Dreamweaver is a great program that has done great things. However if you want to do the next great thing in web design it’s time to move on. At least explore what you can achieve before dismissing it. CMS is a massive opportunity not a threat.

  76. staiano Says:
    March 7th, 2009 at 8:49 pm

    If only this were true I would say this is the best news I have ever heard [for the web]. The sooner dreamweaver dies the sooner people will actually have to know what they are doing in order to build a web site which makes a better web for all.

    Bye-bye dreamweaver, any chance you could take IE6 to the deadpool with you? Pretty-please with a cherry on top?

  77. staiano Says:
    March 7th, 2009 at 9:07 pm

    @Paul McClean, “I would love to see a ?coders only? version of Dreamweaver” There was, it was called homesite [imho]. Great program created by Allaire, then Macromedia bought Allaire and 1 version later the program was no longer being updated. You can still find it though and is still very useful.

  78. Dreamweaver is dying at John Thomson: Thinking out loud Says:
    March 7th, 2009 at 9:53 pm

    [...] I’m sorry but Dreamweaver is dying | PC Pro blog [...]

  79. Bah Says:
    March 7th, 2009 at 10:02 pm

    Note to all current and future web developers:
    Understand what you’re developing – don’t learn to “satisfy the IDE”. If you know what you’re doing, the death of Dreamweaver will mean practically nothing. Get a good text editor; possibly one that provides a direct-to-ftp save feature. There – you’ve got the basics.

  80. peggie Says:
    March 7th, 2009 at 10:24 pm

    Point taken, it’s time for those of us who have relied substantially on Dreamweaver in the past to begin (if we haven’t yet) migrating into a suite of tools rather than the one.

    To that end, I’ve been reading about a Joomla extension that facilitates designing Joomla sites in Dreamweaver … my idea of a nice, soft transition if there really is such a thing and it works. Does anyone have more information about this?

  81. anon Says:
    March 7th, 2009 at 10:33 pm

    You’re not sorry. You god damn liar.

  82. Mike Rundle Says:
    March 7th, 2009 at 11:47 pm

    This article is ridiculous. When telling your print design friends how to transition to the web, how about you give them an HTML & CSS book and tell them to start reading some tutorials. Why would you advocate them using a WYSIWYG editor when that doesn’t teach them anything?

    Web professionals write code by hand, just like software developers write code by hand, just like writers write words by hand. They don’t use an automated story-generator or something, they know the English language and they use it for their profession. Using WYSIWYG editors is not how professionals create websites, end of story. If you consider yourself a professional and you’re using WYSIWYG editors like Dreamweaver because you don’t know HTML or CSS then, guess what? You’re not a professional. Not by a long shot.

    Hand-holding your print designer friends is the worst thing you could do for them. What’s wrong with learning something new? HTML is not complicated, and learning CSS doesn’t take very long with all the books, blogs, and tutorials out there now.

  83. David Says:
    March 7th, 2009 at 11:58 pm

    This is in response to Paul’s post from March 6th.

    Just a clarification. Drupal DOES allow for undoes at least in terms of content creation, provided you direct it to create a new revision either by using the content management settings or for an individual post. In fact the revision history of Drupal is an outstanding feature, and should not be overlooked.

    There is even a very useful module called Diff which allows you to see differences between subsequent revisions.

  84. Dirk Says:
    March 8th, 2009 at 12:22 am

    Reading trough the comments on this article… only a few people seem to know what they are talking about.

    It’s very simple: If you use Dreamweaver to create websites you are not a webdesigner. Most people in the business abandoned Dreamweaver back in 2000, 2001. Dreamweaver is just a tool for hobbyists who want to make a website.

    In short, the so called death of Dreamweaver means nothing for web professionals.

  85. staiano Says:
    March 8th, 2009 at 12:36 am

    @Mike Rundle & @Dirk, you guys are totally on point Mike Rundle, if you use Dreamweaver to create websites you are not a webdesigner/professional.

    I wish more people had your smarts on the subject.

  86. J. Jeffryes Says:
    March 8th, 2009 at 1:45 am

    Wow. I don’t even know where to start. This is like saying “Cars are dying, because I like to swim!”

    Dreamweaver does pale a bit compared to Visual Studio, or other tools built purposely to develop dynamic applications and sites. Hopefully new tools from Adobe will address that. Catalyst looks like a step in the right direction.

    That said, there’s nothing that says you can’t use Dreamweaver while developing dynamic sites. I’ve been doing so for years, and I still use Dreamweaver with dynamic sites regularly. The challenges of developing a dynamic site are the same regardless of the html and style editor you use. Whether you use Drupal, Joomla, Silverstripe, Expression Engine, or any other CMS is largely irrelevant. Bringing it up at all is a distraction, or maybe an admission of ignorance.

    Too bad this post has gotten so much exposure over the social web. Now I’ll be dealing with clueless designers claiming Dreamweaver is dead for the next few weeks.

  87. J. Jeffryes Says:
    March 8th, 2009 at 1:47 am

    A short followup:

    No professional designer uses the visual tools in Dreamweaver to do anything, other than a semi-functional preview.

    If that’s the root of this debate, then people are even more misinformed than I thought.

  88. Chris Charlton Says:
    March 8th, 2009 at 2:18 am

    I am the guy who created the Drupal extensions for Dreamweaver (, and I have to disagree with this article. In fact, no disrespect but I feel this post created more FUD because no respectable designer would use free themes if they’re entire career is based around custom designs. Dreamweaver is strong and is a key tool in creating Themes for Drupal, or Joomla, or Wordpress, or any other customizable CMS.

    I assure you, and everyone reading this article that Dreamweaver is a tool for web production. Drupal, which I love, and I manage user groups for Adobe and Drupal in Los Angeles (LA Drupal; DrupalCamp LA), the room gets packed when I cover Drupal + Dreamweaver… so I repeat, this article is just an opinion and not based on true market numbers. It’d be good to do some research about market adoption for Dreamweaver, PHP, Drupal, and you will see that web designers are not dropping DW, but asking how it should be properly used in the flow of web production when a CMS is adopted and customized.

    The latest release of Dreamweaver (CS4) is a boon for people who need to stay on top of web design as it has great live preview features, the best CSS editing for pros, and a live JavaScript engine that allows you to pause any state of interactivity – which Firebug does not have, and has had PHP and database support for a long-long time. All these are relevant for today and tomorrow; people just need that proper help of workflow and not told their commercial software is “dead” in the eyes of web production.

    Long live Dreamweaver. Long live PHP.

  89. Michael Kimsal Says:
    March 8th, 2009 at 2:28 am

    “the old model of the central webmaster hand-spinning every page of every website and, worse, manually adding the navigation necessary to help users find it, just isn’t scalable or viable.”

    I’ve *always* found this a bizarre way of doing stuff. I’ve been doing website work since late 1995, and in early 1996 started using PHP (PHP/FI) and then bounced between Perl and PHP, and later ASP then more PHP. I’m not sure I’ve done it the “old model” way since January 1996, and even then I hated the “make every page by hand” approach. Server-side includes and whatnot are vital.

    Many people learned to use ‘include’-style creation techniques on the client with packages like Dreamweaver, so must have understood some of the benefits, but still didn’t really “get” the full power of dynamically assembled sites. Yeah, it’s sometimes a bit of a pain to preview stuff with server-side includes, but the otherwise rapid development generally makes up for it.

    Just so funny to see that in *2009* we’re talking about how the old “central webmaster making pages” model is dying.

  90. Sean’s Mental Walkabout » Blog Archive » Links for March 7th Says:
    March 8th, 2009 at 3:00 am

    [...] I’m sorry but Dreamweaver is dying | PC Pro blogThe bottom line is that the old model of the central webmaster hand-spinning every page of every website and, worse, manually adding the navigation necessary to help users find it, just isn’t scalable or viable. The only feasible course for the future is for content to be posted by the content contributor, whether that’s the site owner or site visitors, and for the best possible navigation to be constructed around that content on the fly. [...]

  91. Says:
    March 8th, 2009 at 3:05 am

    as a web designer of 13 years, I am having a hard time seeing every website eventually going to dynamic content.

    Besides the top social media type sites, the majority of useful sites I see on the web are static brochure sites that would never bother with the complexities of CMS. Furthermore, the businesses I deal with do not want the added expenses and maintenance of keeping up with CMS updates, problems, patches, security, etc… They hire me to build a site and then a couple times a year want some updates at minimal expense.

    Overall, a crazy article. Dreamweaver will be around for ages and so will static pages.

  92. logan Says:
    March 8th, 2009 at 4:45 am

    Sweet Jesus! The author of a post proposes that time is marching on, and that maybe the Web equivalent of radio is giving way to the Web equivalent of television. And so the masses descend, trotting out stale arguments about whether a Ford is better than a Chevy, or a Chevy better than a Ford. Or, rather, whether a car—Ford or Chevy—is “better” than a bicycle.

    Boasting that you code by hand rather than with the help of leveraging WYSIWYG tools first doesn’t make any of you any better than those who prefer to do it otherwise. Or any worse, necessarily. It just makes you sound more loathsomely arrogant to the people you serve—yes, serve: the people who have either hired you to make a website or who are producing the content that fills that website.

    You are carpenters—some, admittedly, capable of building exceedingly nice cabinetry—but carpenters nonetheless. Mostly framing houses. And mostly in housing developments.

  93. David Says:
    March 8th, 2009 at 4:55 am

    Dreamweaver is NOT dying. Agree with certain points of this post, but not this specific idea. Dreamweaver CS3 and CS4 have come a long. Since Adobe took over Macromedia, Adobe has begun to expand the capabilities of Dreamweaver.

    CMS has a LONG way to go before it can ever take on an IDE program such as Dreamweaver. Right now, it is extremely difficult to generate a good design with CMS – and I’m speaking strictly design right now. CMS is great for something basic, top to bottom layout that doesn’t involve to much effort into the design, but when one wants to create something more than that – Dreamweaver is FANTASTIC for templating that complex design; CMS cannot do this.

    CMS – Content Management System; a system that manages content – it doesn’t create it or design it. To an extent, it can generate it, but one cannot create or design to the extent of their imagination.

    I’m rambling. Point being, yes, CMS is a great asset for web development but will be used complimentary to IDE programs such as Dreamweaver.

    Furthermore, to add to “PrestonHall.Com”s comment – static pages are SIMPLE. There are man holes in CMS right now that are extremely difficult to patch and work around. Many users want nothing more than a simple static web page or website.

    Dreamweaver will live on for years to come as it grows, expands, and adapts to new technologies.

  94. David Says:
    March 8th, 2009 at 5:05 am

    Also, no matter who you you are, the way Adobe is improving the UI between dreamweaver and their other software, such as illustrator and photoshop, will keep people using dreamweaver for designing their templates and webpages.

  95. Dreamweaver Is Dying. Long Live Drupal! « Bob Morris: Investing, tech, coffee. Says:
    March 8th, 2009 at 5:31 am

    [...] 7, 2009 · No Comments Via Slashdot, a PC Pro article says static HTML is going the way of the Dodo. The real problem for Dreamweaver and for its users [...]

  96. The Future Says:
    March 8th, 2009 at 7:00 am

    Actually, the author is way behind – truly dynamic web sites which are the future of the web won’t be web sites at all, and won’t be driven by web-bases CMS systems.

    They will be a combination of Silverlight/Flex rich client apps that just happen to be hosted in a browser (perhaps).

    Mark my words.

  97. หมดสมัยของ Dreamweaver? | Pantip Guide Says:
    March 8th, 2009 at 9:00 am

    [...] – PC Pro, [...]

  98. Dreamweaver正在死去 at waiwai Says:
    March 8th, 2009 at 10:06 am

    [...] 一位Web开发者宣称Dreamweaver正在死去:这既不是Dreamweaver的错误,也不是Adobe和开发团队的问题——事实上最新的Dreamweaver CS4还是给人留下深刻的印象。 [...]

  99. DevLano Says:
    March 8th, 2009 at 10:13 am

    its not dying, there are just more options.

    i’d put my trust in adobe, over any random, open source, be gone tomorrow, ide.

    (altho, any one remember GoLive? i do. gl>flash>dw>flex)

    also, some day the web will be in 3D. who know what you’ll be using.

    html/css could very well die.

    i can’t even get round corners in all browsers.

    (I can, I just chose to ignore IE)

    i’m ready to stop using html/css.. but i’m forced to..

    p/s – drupal and wordpress are on their way out. just fyi.


    more options.

    first cms to have a motion graphic interface wins. duh.

    thats what the actionscript3 changes were all about.

    improving the way flash interacts with db driven information.

    and it wont even be a cms, it will be a highly integrated service.

    adobe dw/flex/flash/cf/ps/pp/ae/sb/ol user.

    what if firefox became an ide? gasp!

    what if an os became a browser? gasp!


  100. Chris B Says:
    March 8th, 2009 at 10:47 am

    How can you compare Dreamweaver to Drupal? That is the most bizarre comment I have ever heard. That’s like saying music is dying, long like gmail.

    One is a web code editor and the other is a content management system. I ALWAYS build my pages in Dreamweaver, and have done for years. Then I take the code out and implement it into the CMS.

    Somebody in the comments mentioned that Dreamweaver don’t create standards compliant code. You need to learn HTML and code yourself, but in Dreamweaver code view, which is fantastic as spotting unclosed tags etc.

    I will never ever get over how bizarre a statement that was.

  101. Nasar Says:
    March 8th, 2009 at 11:50 am

    I live with Dreamweaver(I’ll die without it.. he he ..As far as notpad is there,no worries), such a good desktop based editor.
    I build my XHTML templates on DW. It is only next thing based on the site scope to switch to a CMS or not.

  102. Jamie Says:
    March 8th, 2009 at 12:50 pm

    I don’t see how Dreamweaver, a IDE/Tool is going to die because of Drupal (or other CMS/blog platform), a system/engine. People still use programs like Dreamweaver to help layout their templates. It beats out most other programs out there.

    It seems like the author is focusing on one small part of Dreamweaver, the ability to handle all files on a static site. If Dreamweaver was built totally for static type sites, then why did Adobe even go through the hassle of including server side technologies?

  103. jean Says:
    March 8th, 2009 at 12:56 pm

    I am going to have to disagree with the guys who say dreamweaver is dead or going to die and cannot create dynamic websites. True the web is changing everyday, but Dreamweaver is a tool that does the basis, of conectivity etc. the rest of the loops and logics has to be done buy the programmer.

    The people who use drupal and joomla are good at what they do best, they will require immediate results in integration, but that would a point when it comes to serious debugging issue.

    One cannot just sit and write a connection statement to a db and write query each and every time, but can do loops, get the logic worked out if a tool is present.

    So guys no Dreamweaver is not Dead

  104. Trypu Says:
    March 8th, 2009 at 1:24 pm

    Look at the best search engines from one place!

  105. Ron Says:
    March 8th, 2009 at 1:29 pm

    IDE of choice: Coda

  106. Stuart Says:
    March 8th, 2009 at 1:31 pm

    I fail to see how the emergence of dynamic websites is bad for Dreamweaver. Yes the program allows you to build static pages but it also have all the ability to allow you to code dynamic websites as well.

    Moreover Joomla or Drupal don’t replace dreamweaver in the slightest. How will you design the templates that go into Drupal? DW has built in css support not to mention all the ajax, and dynamic data features.

    Sorry but comparing DW to Drupal is like comparing Photoshop to Iphoto. Just doesn’t make sense. DW ain’t going nowhere IMHO.

  107. mallchin Says:
    March 8th, 2009 at 1:37 pm

    Dreamweaver is not dying and still represents the pinnacle of web-design applications. Whilst CMS do have there place it takes some massaging and tweaking to get the most out of them, and sometimes that means editing code, something Dreamweaver is great at.

  108. RETARDED POST Says:
    March 8th, 2009 at 1:51 pm


    What do you think the CMS’s code is written in. or the pre-made templates. or the plugins. or the template that don’t yet exist. If you think that DW is some sort of static html only site buillder, you’re a retard.

    This post just don’t make any sence and i hope for the best of web it gets pulled down before it gets anyone fooled. Digg frontpage, shows just how many idiots it already fooled.

    If you are planning to write a comment to the huge pile of crap comments this post has already got, please oh please don’t. Just write something like “WHAT A RETARDED POST”. All caps.

    btw:im not a native english speaker so if you’re retarded enough to buy this post and want to diss me or something, please leave my english typing skills out of it. Thank you.

  109. axel Says:
    March 8th, 2009 at 1:59 pm

    Come on. You can’t compare Dreamweaver with Joomla. Ok installing Joomla is very easy, but you are talking about different things.

  110. The Truth Says:
    March 8th, 2009 at 2:00 pm

    I don’t think the author of this article is a web designer or developer.

  111. Brandon Says:
    March 8th, 2009 at 2:01 pm

    Sadly, engineers and non-gui developers have been saying this for 10 years. It’s akin to the “flash” is dead conversation. But what you fail to note is that templates, buildkits, front-ends of any stripe, have to come from somewhere. An API is how we do it. Now maybe some of the more advanced features in Dreamweaver are dead and maybe what you meant to say was that Dreamweaver as an all-in-one resource for web development is dead. Maybe that’s what you meant to say, but that’s not what I read.

  112. Metalkid Says:
    March 8th, 2009 at 2:03 pm

    Dreamweaver is an Html/css Editor and Joomla and Drupal are CMS… I dont understand your article…. sorry

  113. Mark Says:
    March 8th, 2009 at 2:05 pm

    I’m sorry but this article is worthless. You can’t compare CMS’s with software used to build web applications. That’s like trying to compare Photoshop with iPhoto. They aren’t the same thing.

    I know it’s hard to think of ideas to blog about sometimes, but please spare us garbage like this.

  114. Ed Says:
    March 8th, 2009 at 2:32 pm


    that is nonsense.

  115. The obvious Says:
    March 8th, 2009 at 2:33 pm

    This article is blatant linkbait.

  116. The not-so-obvious Says:
    March 8th, 2009 at 3:09 pm

    Linkbait for sure.
    This is not a technology article, this is pure entertainment blog material.

    There are graphic artists.
    And there are programmers.
    And then there’s all these people who think because they can slap some HTML, slice a graphic, and make a link, that they are web developers.
    (Oh and there’s those people who actually listen to and pay this last group which just continues to feed their impression of themselves.)

    I’m sorry, but you’re not going to get “contributor’s” without some programmer doing some serious coding to create that “mashable” website’s behind the scenes technology. And its not going to look real good without some graphic art skills creating a decent design and balance of color and form. (Yes there are people with both those skills, and they know their abilities and their limitations.)

    So what’s this got to do with Dreamweaver? Dreamweaver is tool for someone developing (programming) websites, and its not going anywhere, why?
    Because not every website calls for Web whatever.0 interactive mashability…
    And are Joomla/Drupal/etc… the future for all web development? NO because they are only ONE possibility… and require one to effectively become a “programmer” of their technology… a skill not everyone will be able to muster.

    Lame article… I’m heading back to Digg to bury it.
    And I think I have some laundry to put in the dryer… oh wait… maybe I should dry them in Laundry 3.0!!!

  117. Dreamweaver is dying « The Ancient Geeks Says:
    March 8th, 2009 at 3:30 pm

    [...] is dying March 8, 2009 — Martin Poulter From an opinion blog post on PC Pro, an attack not on Dreamweaver software but the static-content mentality that says that creating web [...]

  118. james Says:
    March 8th, 2009 at 3:56 pm

    and how do we create and edit themes for these cms’s ………

  119. Paul Godfrey Says:
    March 8th, 2009 at 3:59 pm

    As hard as dreamweaver sucks…you suck harder. This article is terribly misguiding to your audience. Please open up a book or consult someone with a fucking clue.

  120. From Digg via PCPro: I’m sorry but Dreamweaver is dying …A Post Worth Reading for a Chcukle | Visualrinse | Design and Development by Chad Udell Says:
    March 8th, 2009 at 4:01 pm

    [...] some more. Submit a completely ridiculous web design comparison to my comments here. I need a more | digg story Posted on March 8, [...]

  121. Aaron Says:
    March 8th, 2009 at 4:13 pm

    Interesting article. The bonus of dream weaver i always found was the graphical design, which for the most part does not completely pass standards when using it, and the templates feature (which you can always do with php includes if needed). I have moved over to aptana for the last year or two, and it has been golden. A great free editor, based on eclipse. They also have built an Ajax server for it as well.

  122. Bill Says:
    March 8th, 2009 at 4:19 pm

    This is easily the dumbest thing I’ve read all week. Maybe in two weeks.

  123. Bill Says:
    March 8th, 2009 at 4:20 pm

    Just checked my calendar – this is for sure the dumbest thing I’ve read in 3 1/2 weeks !

  124. Mike Darling Says:
    March 8th, 2009 at 4:58 pm

    I use Dreamweaver….but wish I didn’t have to.

    I now use Wordpress and Themes that convert the blog into websites…and adding content is quicker and easier….I even use Wordpress CMS for my own biz site.

    Why charge a client $5,000 for a website that they can’t change or add content, when I can charge $2,000 for a website (Wordpress CMS) that looks great, gets SEO ranking, and easily allows the client to add content themselves?

    I do use Dreamweaver for editing the css stylesheets – and for editing the php code of the theme’s pages… but other than that, the only thing I use Dreamwever for adding content is for building websites for SiteBuiltIt! websites.

    Embrace change. And profit from it.

    My thoughts.


  125. Jeremy Says:
    March 8th, 2009 at 5:33 pm

    While I agree with the point that Dreamweaver is dying, I disagree with the idea that Drupal will end up being the savior.

    If anybody can build an application that will replace Dreamweaver, it will be the Wordpress development community.

    Drupal = oscommerce quality = crappy.

    Wordpress = MagentoCommerce quality = the new ecommerce standard = beautiful quality.

    I realize that this post has nothing to do with ecommerce, but that’s the best analogy I can come up with.

  126. rarzi Says:
    March 8th, 2009 at 5:45 pm

    This is easily the dumbest thing I’ve read all week. Maybe in two weeks.

  127. Brian Reich Says:
    March 8th, 2009 at 5:49 pm

    While I personally hate designing with Dreamweaver, I think it still has a place in a workflow in which different people are responsible for interface design and back-end implementation. There’s no reason you can’t design a site in Dreamweaver and adapt that layout to Wordpress, Joomla, Drupal, or a home-brew CMS. I don’t know of a single CMS or blog package on the market that doesn’t support some sort of templating, and this is where Dreamweaver shines. I would never, EVER use Dreamweaver as my coding IDE however, I don’t care what language support it has.

  128. merlinvicki Says:
    March 8th, 2009 at 6:04 pm

    Dreamweaver is certainly not dying. It is still one of the best Editors around with both code/design view. With its remote connect option i work on Joomla, wordpress etc directly making html/php changes on the fly. Not only it corrects me when i am writing wrong code, but it also helps me with code hints very few editors provide. It also helps me keep in check who is working on what files with the file checkin/checkout system. Sorry, but the author’s comments are more of a personal nature than the real truth.

  129. John Says:
    March 8th, 2009 at 6:07 pm

    After seeing this on both reddit and digg. You are either a complete idiot and have no clue what you are talking about or you just wrote an amazing piece of LINK BAIT.

    I’m going with #1.

  130. Rob Porter Says:
    March 8th, 2009 at 6:15 pm

    I have been a web developer for over 15 years and I have used Drupal, Joomla and Dreamweaver together to build custom sites. They all have advantages and disadvantages. As far as the “death” of Dreamweaver – that will not be anytime soon.

    Maybe you (Tom Arah) are biased in your opinion, and that is your right to be biased. But, don’t think for a minute that seasoned Professionals, like myself, are going to give up an indispensable tool like Dreamweaver.

    I would rather hand code everything – double check in Dreamweaver for syntax and code errors.

  131. Ken Says:
    March 8th, 2009 at 6:21 pm

    Don’t see it, Dreamweaver is a tool to work on HTML, Drupal is a content generation tool, Surely what tend to be done in Dreamweaver like 6 years ago before the advent of easy to use CMS free tools, can be done using one CMS and one html template, the only work to be done would be creating the html templates, but, it still needs to be done, so, html editors would be around until the CMS would start to add a way to do it in situ (there are a lot of places to do it, but pretty cumbersome and pretty standard, no way you can go innovative or buildign something new with those tools).

  132. James S Says:
    March 8th, 2009 at 6:24 pm

    David Singer – “Dreamweaver sucks, always has, probably always will. If all you can do is point and click around a WYSIWYG editor then you should not be a web developer.”

    The fact that you define DW as WYSIWYG and assume that’s all anyone uses it for shows everyone familiar with the other 99% of DW’s functionality that you have no idea what professionals use it for.

    DW is not WYSIWYG, the web is too dynamic. You’re right about one thing-some beginners do use DW to try to point and click in design view, but that hardly dismisses the vast amount of other features and capabilities of the app.

    How does one “click around” writing and formatting recordsets, advanced JavaScript and PHP, setting up database driven applications…and the list goes on.
    Please advise us how DW “sucks” in these areas.
    I doubt you can, as it seems like you only tried to use it as a “WYSIWYG” or saw someone else do that. Too bad you didn’t get past the front door into what you can really do with it.

    Just continue to suffer in your ignorance.

  133. porfitron Says:
    March 8th, 2009 at 7:12 pm

    Joomla and Drupal [and Wordpress] don’t build themselves… nor do they provide a platform for easily creating your own themes or add-ons. Dreamweaver still can play a role here. I regularly use Dreamweaver to make my own PHP, CS, and JS files. Aptana is also a GREAT tool for this, but since we’re talking about Dreamweaver, I think it’s a poor assessment to categorize Dreamweaver as an HTML editor… it really is a web development platform [PHP, JSP, ASP, s/FTP...]. The article should really be entitled the HTML Webmaster is Dying.

  134. Glenn Says:
    March 8th, 2009 at 7:14 pm

    Dreamweaver as a way to author and edit professional web pages that are live has been dead for years. The era of the web app killed it long before AJAX become popular.

    Dreamweaver is very much alive as a way to quickly produce high fidelity mockups and is still very popular with web designers.

  135. Andy Says:
    March 8th, 2009 at 7:50 pm

    Dreamweaver is an overly-converged application. It is a content manager, a code manager, a code generator, and an ftp client. Sure there are components of CMSs and frameworks that still need to be produced at some point, but imho, dreamweaver does nothing well. Now that content management has moved into serverside applications, and code libraries for dy6namic applications are readily available outside of what adboe offers, it is basically an inefficient, messy crutch for people that can’t hand-code i.e. adobe-centric designers.

  136. TheBigO Says:
    March 8th, 2009 at 8:21 pm

    This is a very negative article, creating hysteria and directing people towards CMS – content management system – like one other poster says – didn’t build themselves. Authoring tools like Dreamweaver ARE still needed for those of us who still hand code and choose to work with it.

    I think the problem here is that ‘designers’ may not get the value from dreamweaver that may not manage to keep up with components in order to keep apace with the move in web technologies.

    I see this article as slightly worrying in that you are basically forcing a perfectly good application that has proved its worth to many developers over the years in favour or some online editing tools that have yet to offer the same feature set.

    Let’s also not forget, Drupal, Joomla, Dreamweaver and Frontpage (to name but a few) in the hands of people who do not understand web standards, semantics and web accessibility can be dangerous.

    Dreamweaver is a tool, like Photoshop or Word. Just because you use Photoshop does not mean you are going to be any good at it – but if you have the skill, then you can produce great pieces of work. And if you have word, you are not going to be the next great author – but some great authors may have written great books using word.

    This article is like saying – The printed book is dead, because you can fit a book into a PDF and carry around with you on your PDA, laptop or iPhone. But that isn’t the case. People still like to hold a physical book and leaf through the pages – and people who code also like to get their hands dirty without having some web app try and tell them how to do stuff – or force them into a certain way of doing things.

    Anyway – that’s my 2p worth on the subject. Long live any application that helps e get a job done!

  137. Elena Adams Designs - News » Blog Archive » The Death of Dreamweaver Says:
    March 8th, 2009 at 8:37 pm

    [...] See the original article here. [...]

  138. Sally Foster Says:
    March 8th, 2009 at 8:54 pm

    This is retarded. You are comparing a tool and an application it created. We still need the tool to modify the highly flawed application. Drupal isn’t a solution for every, or even most problems.

    I’m not a fan of DW – I dropped it when it was “UltraDev” and yet I concede that Macromedia-then-Adobe have kept pace with emerging technologies.

    DW has never been a decent WYSIWYG – it’s a text editor for professionals. If you think that innovation is going to come from people using Drupal/Joomla/canned solutions, you probably DO need a WYSIWYG.

  139. Nobodyspal Says:
    March 8th, 2009 at 9:07 pm

    Your an idiot. Take two steps away from your blogosphere and you’ll find the real web past the opinions of 11yr old critics talking about nothing. If you love CMS so much just stay on Myspace of facebook like all the other tools.

  140. Ras Samuel Says:
    March 8th, 2009 at 9:11 pm

    Dreamweaver is is not dying out, but it is being put in its proper role as a XHTML/CSS design tools for professionals who don’t hand code. Using Dreamweaver as a content-management tool was never a good idea to begin with and fostered unnecessary dependence on the ‘designer’ as a content-manager. Clients are finally being educated about the point that they should have some sort of CMS in place so that they don’t have to send all updates through their designer. You’re a little late on reporting this trend. This transition has happened over the last few years… I’d say it’s old news by now.

  141. Rishi Says:
    March 8th, 2009 at 9:44 pm

    Coda blows Dreamweaver out of the water with its simplistic UI and straightforward features.

  142. “In other words Web 2.0 isn’t an empty slogan” Says:
    March 8th, 2009 at 9:47 pm

    [...] I’m sorry but Dreamweaver is dying | PC Pro blog [...]

  143. JimPerryWebCS Says:
    March 8th, 2009 at 10:15 pm

    This is a great article.

    It reminds me of a friend who has a favorite hammer. As a young boy, my friend’s father taught him to drive nails into spare boards in the workshop. When the boy mastered the art, his father gave a hammer for his own.

    Over the years, the boy used the hammer to create toy airplanes from three scraps of wood, and later a birdhouse, a book shelf and a wood shed. One day the boy, now a man, tried to use the hammer to install a sheet-rock drywall. Unfortunately, the hammer repeatedly tore the paper holding the sheet-rock together, so the man bought a drywall hammer. The room was finished a short time later.

    I still have my Dad’s hammer, but I also have a full toolbox of hand and power tools.

    The technologists I prefer to work with are religious about foundational principles and theories, not tools.

  144. Ryan Says:
    March 8th, 2009 at 10:29 pm

    Dreamweaver, Go-Live & Frontpage all died to me the moment I learned how to write good clean code. A WYSIWYG editor is unable to give a good web designer true site optimization. That’s (just another reason) why they’re dying.

  145. I’m sorry but Dreamweaver is dying « irrevocable stuff Says:
    March 8th, 2009 at 10:53 pm

    [...] read more | digg story [...]

  146. lawl Says:
    March 8th, 2009 at 11:07 pm

    you’re retarded, idiot. dreamweaver isn’t “dying,” and it’s on the right side of web 2.0. besides that stupid SPRY bullshit, CS4 is the bomb

  147. La linea di confine tra unopuntozero e duepuntozero - The New Blog Times Says:
    March 8th, 2009 at 11:09 pm

    [...] a mio modesto avviso, proprio su questo stesso argomento alcuni osservatori sono più categorici e ritengono che applicativi come DreamWeaver stiano morendo, ma sono convinto che non sia così. A ben [...]

  148. Alex Prykhodko Says:
    March 9th, 2009 at 12:53 am

    In the author’s response: “The future for creating web design is in the browser not in Dreamweaver.” Good web design actually starts from .PSD, not from .HTML. Devs are never gonna be designing within a browser. The author is totally unaware of what he’s talking about.

  149. Just Ziya » Blog Archive » Dreamweaver正在死去|Solidot Says:
    March 9th, 2009 at 12:58 am

    [...] 一位Web开发者宣称Dreamweaver正在死去:这既不是Dreamweaver的错误,也不是Adobe和开发团队的问题——事实上最新的Dreamweaver CS4还是给人留下深刻的印象。虽然微软的Expression Web对它构成了威胁,但Dreamweaver仍然是目前最好的HTML/CSS页面编辑器,但真正的问题是web正变得越来越动态化。动态生成的Web应用数量远远多于基于静态HTML网页,如Joomla和Drupal之类的内容管理系统能很容易的帮助静态Web 1.0设计者转换到动态的Web 2.0脚本世界。所以Dreamweaver正在死亡,Drupal万岁。 [...]

  150. I’m sorry but Dreamweaver is dying | Buzz Newsroom Says:
    March 9th, 2009 at 1:27 am

    [...] from here [...]

  151. Aaron Says:
    March 9th, 2009 at 1:56 am

    I don’t buy it. No matter how dynamic a site you’re building, tools like DW will speed up markup, CSS, and Javascript development, especially with the live view and realtime JS debugging in CS4. Dreamweaver is far from dead, its purpose for existence is just a bit different than it used to be and the way it fits into a workflow has dramatically changed.

    Frankly, I’m annoyed by elitist individuals like the author who are “religious about foundational principles and theories” but don’t have a clue how to help people actually realize those ideas, which is done by using tools. You’re hindering progress, not helping.

  152. dingle Says:
    March 9th, 2009 at 2:25 am

    This author is an idiot. I utilize Dreamweaver to code my own CMS packages for clients. I have found that the existing packages have far more than I need in them, and the amount of time to track all the variables they are using to customize them and clean them up is a huge waste of time. Even tracing all the CSS to manipulate the site to match your preferred design (or hello, the clients design?) takes unnecessary time. I reuse all my own code, test on a server locally, all while Dreamweaver maintains the links and site and server (both IIS for ASP and Apache for PHP) info for me. The author writes as if all they know how to do is write simple html pages. Get with the program and step up to some modern day programming. You are feeding lies to the masses on this site due to your ignorance of the full potential of the software. Just because you don’t know how to properly use and setup Dreamweaver, you jump to the conclusion that it is now going the way of the dinosaur. I think your opinion is best kept to yourself on this matter. Atleast leave it to the people who know how to use the software properly anyway.

  153. dbonneville Says:
    March 9th, 2009 at 3:21 am

    I’ve used DW since version 1 for my freelance graphic design business. Every version has gotten better, but I have never relied on the DW templates. Comparing DW to Joomla or Drupal is totally silly. I write sites in Perl, PHP, Joomla, Expression Engine, write JQuery, Javascript, etc. DW is simply the best code editor out there that is cross-platform and industry recognized. The author really, really, did not understand what he was talking about.

    To sum up: I use DW incessantly everyday, and all I do is CMS. I manage complex server relationships between DEV, SIT, UAT, and PROD environments. The article is just utterly misinformed.

    To say DW is dying is like saying Word is dying because people use email and not printed letters to communicate. If anything, the article was written intentionally to drive ad views. Nobody could be this inflammatory in purpose without understanding what they are talking about. Next thing, you’ll see is “Obama is a Muslen”…

  154. rsys Says:
    March 9th, 2009 at 3:35 am

    How we are going to made CMS without the IDE ??? for me CMS is just bunch of code that help to generate or manage content… IDE where we write the code…

  155. Don’t Use Dreamweaver or FrontPage Anymore: Chris M. Lindsey Says:
    March 9th, 2009 at 4:51 am

    [...] Arah at PC Pro has a nice article explaining why you should no longer be using Dreamweaver (or FrontPage) to make websites, and [...]

  156. rumblepup Says:
    March 9th, 2009 at 5:53 am

    I’m sorry, but you have made the absolute dumbest association I have ever heard in my life. A CMS does not DESIGN a website, a DESIGNER designs a website. Dreamweaver is NOT a PLATFORM, it is a visual (WYSIWYG) tool that is used to create the visual style.
    This is the most ignorant post I have ever read, and the only thing you have done is point out exactly how.
    You are doing a disservice to your readers.
    I’m wondering if you have ever seen DRUPAL design a website? It creates the layout? It creates the colors? How about the Logo, does it make that too?

  157. Beer Blog Says:
    March 9th, 2009 at 5:58 am

    I really don’t like Dreamwearver or Joomla!. I think Notepad is the best editor out there, but it only works if you know what you are doing. The only wiswig ap I use would be Visual Studio and that’s to develop ASP.NET. Take care.

  158. Just Ziya » Blog Archive » Dreamweaver 正在死亡 | 煎蛋 Says:
    March 9th, 2009 at 6:41 am

    [...] Dreamweaver 正在死亡,Drupal万岁。(Link) [...]

  159. Wizard Says:
    March 9th, 2009 at 8:02 am

    I had to check the date of the post … to make sure it was current … Near the end it says ” … these are early days and the cms options as they stand are currently only ready for early and adaptable adopters, not for the mainstream … ”

    “Early days” I have been using a CMS in one form or another since 2002. Move on people, it’s 7 years later. The “early days” are over.

  160. Gaurav Says:
    March 9th, 2009 at 8:37 am

    I feel dreamweaver is so memory consuming … we have other open source alternatives notepad++ , netbeans etc

    so why worry for dreamweaver

  161. National Centre for e-Social Science BLOG » Blog Archive » Web Development Tools: HTML editors can’t compete with Content Managment Says:
    March 9th, 2009 at 8:58 am

    [...] Why Dreamweaver is dying [...]

  162. I’m sorry but Dreamweaver is dying | Says:
    March 9th, 2009 at 9:16 am

    [...] I’m sorry but Dreamweaver is dying | PC Pro blog [...]

  163. billybob Says:
    March 9th, 2009 at 12:04 pm

    what a load of sh1t…absolute nonsense

  164. justmeol Says:
    March 9th, 2009 at 12:58 pm

    Yeah maybe … but probably not. The vast majority of websites, including those for small businesses do not have nor do they need cloud or webservices. They need access to data … their own, stored on THEIR server. LAMP and AJAX is more than sufficient to get the job done. Getting really old hearing about all the bleeding edge technologies that we have to have to survive. I don’t even use the bloody program(DW). Its big and bloated. For me Homesite(Macromedia/Adobe) is still the best tool for the job. You actually have to learn how to write your code. Its had live view for 10 years (we call it server mapping). Whether you write MVC/OOP or code procedurally with includes and functions, the end result is all the same. Learn some javascript and the DOM.

    Not sure why this writer thinks DW is a static HTML editor. That’s not even close. Even with its limitations, you can code in any server side language you like. That’s NOT static by any means. You can write AJAX code in NotePad for heavens sake …. I don’t get the point?

    As a developer, I’ve seen what Joomla and Drupal do. They create cookie cutter look alike sites based on templates. Get a CSS editor and learn what CSS really means. Try Andy Budd’s CSS Mastery … a great book.

    Go out and rent a VPS server where you have root access. ($40 bucks a month … if that’s too much go in on it with some friends). Learn to use the command line, write apache directives and htaccess files. This stuff is not rocket science.

    You don’t need CMS systems. You need to take your job seriously and learn to write code. You can hook into API’s without needing any additional software. Building websites without understanding how they work is like building a car and expecting it to run. Sooner or later you are going to have to debug the thing. Take a look at the forums for Joomla and Drupal. They are chock full of fundamental coding questions from people who want to build sites but don’t have enough experience to understand the underlying code.

  165. » Links for this day Says:
    March 9th, 2009 at 1:17 pm

    [...] Dreamweaver is dying The fact is that Dreamweaver has always been looked at as the “Kick Me” note attached to your back. [...]

  166. billybob Says:
    March 9th, 2009 at 2:10 pm

    the article is not criticising dreamweaver per se…but the fact that source code it edited off live and uploaded to a particular web server. It is sugggesting that this is a thing of the past!!!

    As a web developer I can tell you that 90% of the time this is not a thing of the past. The other 10% is for the clients that require a CMS system that they never use!!!!

  167. txoxy Says:
    March 9th, 2009 at 2:39 pm

    CMS hackers desperately need designers and those designers will be using Dreamweaver.

    For a different perspective on this discussion take a look at the blog entry: “Why do Drupal themes suck?” .

    He says: “Drupal is a wonderful playground for code developers. By and large, code developers are bad graphic designers. It’s almost as if loving beautiful code structure keeps you from loving beautiful visual design.”

    The problem with most of the anti-Dreamweaver comments in this thread is that lacking an eye for good visual design the need for Dreamweaver is completely invisible to you. You can’t appreciate what you can’t see.

  168. Robert Says:
    March 9th, 2009 at 4:12 pm

    Sad but true. Good article Tom.

  169. Timothy Says:
    March 9th, 2009 at 4:23 pm

    I hate Dreamweaver. SciTE all the way!

  170. Straw Dog Design » Dreamweaver is dying? Says:
    March 9th, 2009 at 5:10 pm

    [...] article up over at about the future OF THE INTERNET ITSELF. Author Tom Arah makes the case that Dreamweaver is dying [...]

  171. Austoon Daily » I’m sorry but Dreamweaver is dying Says:
    March 9th, 2009 at 5:26 pm

    [...] I’m sorry but Dreamweaver is dying [...]

  172. Kjinx Says:
    March 9th, 2009 at 5:28 pm

    Dynamic content is fabulous, super fun for designers and programmers, powerful and often (not always) great for users, and everything you said … except one thing …. it’s crap if you are building SEO. And for those of us actually using the web to reach customers, sell products, and make a living (you know ….. “commerce”?) …. well — silly us — we actually care about people finding us and lots of dynamic content will just about guarantee that won’t happen (unless you’re someone like Amazon who doesn’t need to be found because they’re already found … if you understand what I mean).

    So we’ll stay with Dreamweaver and our stodgy old fixed HTML pages thank you very much, we’re on the first page of Google for 21 of our key words in the natural listing and doing over a million dollars in NEW business a year from those stodgy old fixed HTML pages.

  173. Is Dreamweaver Dying? - Says:
    March 9th, 2009 at 5:39 pm

    [...] just stumbled upon an article about the increasing obsolesence of Dreamweaver and tools like it. The point is that websites are becoming increasingly dynamic. Building static [...]

  174. Real Says:
    March 9th, 2009 at 5:40 pm

    dreamweaver is not wysiwyg at all with respect to its integration with CSS — just look at the difference between what a well written page with CSS looks like when in the editor compared to it being rendered in any browser; dreamweaver fails!

  175. Davide Vasta Says:
    March 9th, 2009 at 7:40 pm

    Good point. But according to me the problem is not about Dreamweaver (or FP or whatever else), but about static HTML vs dynamic, server side, solutions.
    I also think that even moving toward full browser operated web applications, one will still need for a long time a “classic” IDE, for some purposes.

  176. From Digg via PCPro: I’m sorry but Dreamweaver is dying …A Post Worth Reading for a Chuckle | Iona.LABS Says:
    March 9th, 2009 at 8:20 pm

    [...] FTA: The real problem for Dreamweaver and for its users is that the nature of the web is changing dramatically. Dynamically-generated web applications, from Amazon right down to the humble blog, all offer much more – in-built commenting, voting, RSS feeds, etc – than the best sites built on static HTML can ever hope to provide. Read it here. [...]

  177. Tech-E » HTML and me - when WYSIWYG is not enough Says:
    March 9th, 2009 at 9:35 pm

    [...] as the premium product, seems to now fall short.  Blogger Tom Arah talks about just that over at PC Pro Magazine, saying that more and more those to whom he use to recommend Dreamweaver are now looking to Blogs [...]

  178. David Singer Says:
    March 9th, 2009 at 10:17 pm

    @James S I know it can be used as a straight code editor with no WYSIWYG functions but then why spend the money? There are dozens of better code editors out there that support more languages, have better formating options, and do a much better job at syntax highlighting (especially when it comes to JavaScript libraries).

    To the other points you mentioned. Why would you want an IDE to generate your JavaScript for you? Why not just write it yourself. The “advanced” JavaScript you mentioned is something I have never seen Dreamweaver do. Sure it will generate JavaScript but its always ugly and bloated and often inline. If you wrote it yourself you could optimize it and leverage other libraries that you have already loaded. Furthermore Dreamweaver will often write JavaScript for functionality that could/should be done in CSS.

    As far as creating recordsets there are existing tools which I think are better suited to that task. This is probably just my opinion though.

    I also have some questions about scalability with DW. My current working directory has 31,678 files in it and I typically works with 200-400 open files. I just tried opening 400 files in DW and it brought my Core 2 machine to a halt for a few minutes. To me thats unexceptionable.

    In the end for me a lot of it is coding style. Dreamweaver helps you write code. The thing is I don’t want help. I don’t need help. I prefer to write the code myself and have the editor do as little work as possible.

    I would also direct you to

    Adobes own page on DW written with DW contains the following:
    Inline JavaScript – Considered by most to be incorrect style.
    Random JavaScript – Just randomly placed thought the page.
    Inline CSS – Considered by most to be incorrect style.
    Incorrect tag indentation… and 30 blank lines of code (31-60) – WTF is that?
    Incorrect tag usage.

    And the best for last 27 errors. If thats the kind of site you want to write then DW is probably perfect for you. Personally id rather write valid code and I find that its much easier to do with a editor that stays out of the way like Aptana.

  179. Dreamweaver 正在死亡 - 左岸读书_blog Says:
    March 9th, 2009 at 11:35 pm

    [...] Dreamweaver 正在死亡,Drupal万岁。(Link) [...]

  180. Jeff Johnson Says:
    March 10th, 2009 at 5:44 am

    In my humble opinion, the article overstates the change, probably in order to be provocative. Yes, dynamic content is on the ascendency, but static Web content is not going away.

    Reason 1: Websites have value.

    In the 1950s and 1960s, visionaries predicted that all existing buildings would, by the year 2000, be razed and replaced with Jetsonian space-needle constructions. It didn’t happen, mainly because buildings are major capital investments that retain their value not just for decades, but sometimes for centuries. (Retro-chic and nostalgia for antique buildings add to this.)

    Websites are capital, just like buildings. Companies spend millions of dollars on their websites, and they treat them like capital investments. Those investments must be depreciated over a reasonable lifetime. They cannot simply toss out a site they developed last year because some new web technology comes out.

    Even small organizations spend sigificant money on their websites. My consulting website cost about $25K, not even counting my own labor.

    Reason 2: Static content isn’t going away.

    Static content will always be with us, even on sites that have dynamic, user-contributed content. Sure, YouTube is going to be mainly dynamic content, but what about YouTube’s Acceptable-Use-Policy page? That will remain static. At the other extreme, sites for small non-profit orgs will remain mostly static even if they have some dynamic pages, such as discussion forums. E.g., my wife’s documentary photography website ( is mainly static, even though to keep up with modern web practices the home page is now a WordPress blog.

    I’m not arguing that Dreamweaver will remain. I never use it. I am just saying that static Web pages are here to stay.

  181. I’m sorry but Dreamweaver is dying - Waavoo! Says:
    March 10th, 2009 at 11:49 am

    [...] [...]

  182. danreb Says:
    March 10th, 2009 at 2:17 pm

    I don’t used drupal but used WikiCMS as my CMS framework for my website clients. I developed the templates for the CMS in Dreamweaver and then drop it to template directory of my CMS.
    I will agree to the author that Dreamweaver is dying if he can show a tutorial or demonstration that Drupal can create a templates by its own just by using a web browser and edits all the layouts in there without any text editor or IDE.

    Maybe he’s right if drupal had this capabilities.

  183. Says:
    March 10th, 2009 at 2:48 pm

    dont tell me dreamweaver is finished! ive spent the last 6 months swatting up on it! I do find the css aspect impossible tho

  184. Lanny Says:
    March 10th, 2009 at 8:52 pm

    The author of this “article” has absolutely no idea what he is talking about. Zero. None. Nada. I am a full time developer who spends 12 hours a day in dreamweaver – I haven’t build a “static” site in years. I also do not work off of frame works and pre-built cms’s. Dreamweaver saves hours build front-end ui’s to corporate sites as well as the backend to major projects. This person is obiviously not a developer but a blogger who has no real concept of what it takes to build the applications he writers about.

  185. It’s time for web 1.0 to die « The ByteBaker Says:
    March 10th, 2009 at 8:55 pm

    [...] a website is impractical at best and downright stupid at worst. A recent article proclaimed that Dreamweaver is Dying, and I have to grudgingly agree. Over the past two years, I tried maintaining an old style website [...]

  186. Craig Says:
    March 10th, 2009 at 9:00 pm

    DOS is dead! Long live the Mac. (overheard circa January 24, 1984)

  187. Sites and Soundbytes » Drupal Lives! Says:
    March 10th, 2009 at 9:08 pm

    [...] was intrigued by an article by Tom Arah at PC Pro titled I’m Sorry but Dreamweaver is Dying.  Our library made the move to Drupal around two years ago.  We are now on our second [...]

  188. Andrei Gonzales Says:
    March 10th, 2009 at 10:40 pm

    Apparently, Mr. Arah had an answer to a question that had no reason for being asked.

    Whereas, I have a question to which Mr.Arah may not like to answer:

    “How many websites and web apps has Tom Arah built on his own?”

  189. Frank Says:
    March 11th, 2009 at 6:22 am

    I think this is fifty fifty the chance, that these editors do not have a future. As there are still many companies out there, who simply require a web presentation which isn’t changed very much or often, static pages will still survive. So, why give up this kind of editor for these kind of projects.

    Enhancements to these type of pages can be done via a neat JS framework or even some flash (don’t yell at me, some want it for visual appealing stuff) and that kind of code (JS) can be easily edited with dreamweaver and co.

  190. keruchan Says:
    March 11th, 2009 at 7:10 am

    What exactly is wrong with dreamweaver? I don’t understand at all, I’m using DW to create Joomla templates, there is a plug-in on DW for inserting module position, it can also update the temlates xml file on it’s own, there is also a one click conditional snippets for module positiion and you can even embed and build a dynamic flash. (I’m pointing to a flash which uses php/mysql not XML.)

    Static web sites are almost dead today but DW is not just for static web, DW has a lot of features, it is a package. I bet the author only knows how to build a static site on DW, and being so damn amaze when he found out about CMS. This is lame…

    DW is not a system it is a tool a software, CMS like Joomla and drupal is not a tool nor software they are system, it’s not right to compare the two, and I bet some of those CMS developers are using DW to create modules and extensions.

    I’ll dig this stumble and Delicious, so people know how funny this article was.
    give this article a lot of traffic he needs. ^__^

  191. anonymous Says:
    March 11th, 2009 at 5:27 pm

    You are an idiot or a internet troll. Dreamweaver isn’t a tool you match with Drupal. Probably the developers made Drupal with Dreamweaver. Plus you still need an editor like Dreamweaver to make drupal or joomla’s template. Now if you compared it with textmate or Eclipse, then you might have a valid article, but this article is just naive and a waste of our time.

  192. aristarkhos Says:
    March 11th, 2009 at 6:43 pm

    This is from a content generator’s side of the fence. Working with a static/less-dynamic built on something like JSP, for example, has been a painful experience. Changes that need to be made to improve readership and end-user experience can only come from a CMS solution because of its flexible nature.
    The struggle with developers to change elements or add features is something I do not look forward to because it means endless sessions on “feasibility studies” and listening to “this will be a bit of a fight” which leads to “this is not priority right now”.
    A simple up-to-date CMS solution will help solve these problems but they are stubborn. So I dont think editors like DW will die for a loong time. Stubborn professionals who do not want to move to next level of web designing/coding are going to be the obstacle.

  193. Wayne Says:
    March 12th, 2009 at 2:24 am

    What a lot of crap! You can do anything you like with DW! I use it all the time to create static sites, dynamic sites as well as templates used for CMS so get your facts straight. And besides, I don’t agree that you should use CMS for each and every client. They are burden to keep up to date, prone to hacking, prone to data loss, most need technical skills as well as HTML skills so where is the benefit to someone who just wants a plain & simple brochure site. You don’t give someone a Rolls Royce when all they are willing to pay for is a Mini…..

  194. Mike Says:
    March 12th, 2009 at 8:19 am

    I think most of the web design people have lost the plot, aided only by short sighted business managers.

    The business side of the web is about information with a shortcut to results, not an art gallery.

    When you had to write in HTML and access was via a dial up modem pages were kept simple and direct. With the advent of dreamweaver and the like designers were let loose, limited only by the access speed. Now with broadband it seems anything goes.

    A few equations: Time = Cost: Greater the time taken to navigate = Greater the loss of interest: Harder to find information = easier to find another suppliers page:

    Pet hates:
    Intros- Imagine every time you went to a high street store you had to endure 3 minutes of fancy graphics (often meaningless or irrelevant) before you could shop.

    The mouse trap: Where you have to concentrate on making sure the mouse pointer avoids certain words in case a popup covers what you were trying to read, making the original article impossible to digest.

    And to close what could have been made into a book

    The Who, What & Why of a company web site: Who we are, great, you are just the type of company we are looking for. What we do, even better, I have found just the product I need. Why (have the website), no bloody idea, we cant find a phone number to contact you.

    Remember, just because you have bought an expensive tool kit you do not need to use every tool each time you design a website.

  195. Строитель Says:
    March 12th, 2009 at 9:45 pm


  196. Dreamweaver is not dying…yet | Traveling Down the Information Backroad Says:
    March 13th, 2009 at 2:17 am

    [...] tweet from my friend Alvin last week led me to I’m sorry but Dreamweaver is dying on the PC Pro web site. For the uninitiated, Adobe’s Dreamweaver is still the leading web [...]

  197. Carlos Says:
    March 13th, 2009 at 3:41 pm

    I think Dreamweaver, Expressions, Visual Studio, Notepad ++ or other editing programs are going to be around for a while. Keeping local copies of the HTML,CSS, PHP,ASP.Net files locally on my machine is much more comforting than trusting a hosted server or web development environment to do all my development. With the possibility of a server crashing and losing all my data, even with backup, I still will always keep local copies of the skeleton of my projects.
    The web is still not bullet proof. It servers still crash, websites get hacked, data gets lost in the abyss the internet, caching, and all the other things that happen to our sites, a local copy is trustworthy.
    If full development becomes fully web controlled, then I will start worrying, but for custom jobs, templates won’t work. Those templates were built by a developer using a local computer software such as DW or VS, packaged, the, pushed to the server. It did not create itself. So as for DW or others to fizzle out is a misconception. Even if full web controlled development becomes available, you don’t have local copies to get the thing back up and running.

  198. nikhil Says:
    March 14th, 2009 at 6:52 pm

    which world are you in??
    whoever told you that you cant make dynamic pages with dreamweaver??
    it integratees beautifully with coldfusion
    and i discovered to my delight how easy it makes designing my little apps

  199. Yoko Says:
    March 15th, 2009 at 3:33 pm

    My first thought when I saw this article was: When was this written? Checking the url, this month!

    Dreamweaver died a long, long, time ago.

    For me. I suppose it still has it’s uses. It’s still good at what it’s always been good at; building static sites. I personally hate it for that, but there you go.

    Plugins for browsers and great text editors are now and the future. Dreamweavers design view will always be an out of date browser. Dreamweavers code view is shocking.

  200. Boycott Novell » IRC: #boycottnovell @ FreeNode: March 15th, 2009 - Part 1 Says:
    March 16th, 2009 at 2:00 am

    [...]…; (I’m sorry but Dreamweaver is dying) [...]

  201. A nice chat with Adobe about Dreamweaver | PC Pro blog Says:
    March 16th, 2009 at 2:49 pm

    [...] my recent post, I’m Sorry but Dreamweaver is Dying and the ensuing online discussions/abuse, I was summoned for a chat with the headmaster – Devin [...]

  202. rodron Says:
    March 16th, 2009 at 4:51 pm

    I love creating websites in a CMS (I use Drupal) and there’s no doubt that it offers so much flexibiilty and options to let our imagination run wild. I do, however, still find that i still need to put together a mockup of my website design in Photoshop, then test it out in Dreamweaver (which is quick for me), before I start adding php and CSS tags and merging it into a Drupal theme. For those of us who are visual thinkers, Dreamweaver is still a godsend, although sometimes it might not be perfect, it comes close to a preview before we make it into a theme.

    March 16th, 2009 at 8:42 pm

    [...] scheme would fail in this new environment and while this has already been admitted by some there are others who are going in the entirely wrong direction. personally i embrace it, sure it [...]

  204. » Drupal and Dreamweaver’s Jekyll and Hyde Problem Says:
    March 17th, 2009 at 4:04 pm

    [...] on at Slashdot about a blog post made by a web designer: Dreamweaver is Dying, Long Live Drupal. (Original post is here). As a web producer at O’Reilly put it: “I’ve been waiting to jump into this thread because talking [...]

  205. Ronny Karam Says:
    March 17th, 2009 at 4:21 pm

    If your comparison was made between writing dynamic pages from scratch and CMS, I would’ve agreed with you on some points.
    Yet comparing Dreamweaver to Drupal is hilarious. Ask any Drupal developer where he modifies his dynamically generated CMS files. The answer will be, in most cases, either Zend or Dreamweaver.
    Dreamweaver isn’t a content management system. It’s a code editor. It’s like a fancy notepad or text edit.
    While Drupal is a content management system that performs specified tasks. Still, when you add a particular method you have to go back to your favorite code editor, like Dreamweaver and write your code from scratch.

    So your comparison is not valid…

  206. 3D Power Sparks - What? Are You Insane? Says:
    March 18th, 2009 at 9:13 pm

    [...] Tom Arah, he really provided a conviencing blog entry. I you haven’t read the blog on “I’m Sorry, Dream Weaver ….” I can’t even write it. You could at least have skirted the “in your [...]

  207. Dreamweaver_Chicago_User Says:
    March 18th, 2009 at 9:55 pm

    I have been building dynamic sites for almost a decade – mainly in PHP and I still use Dreamweaver almost everyday. Think of Dreamweaver as the front-end for design program and PHP as the element that ads the dynamic portions. This article in my opinion is garbage. If you don’t know how to code in PHP, Dreamweaver can also do that for you, so I am not really sure the author is that familiar with Dreamweaver. Of course you can hand code your HTML, but I for one value my social life too much.

  208. 2002 free frontpage hosting web Says:
    March 19th, 2009 at 7:24 am

    2002 free frontpage hosting web…

    I can’t believe that I missed your point, I will have to do some research on this….

  209. ebookey Says:
    March 19th, 2009 at 12:31 pm

    Glad to hear it’s dying. I’ve been tempted for more than 10 years to try to learn Dreamweaver, but now, Wordpress or Drupal will solve all my problems in no time ;)

  210. BoomBoom Says:
    March 19th, 2009 at 12:41 pm

    It will take a very long time until Dreamweaver will die. This article is just trying to alarm for nothing its readers.

  211. joe ekine Says:
    March 19th, 2009 at 12:46 pm

    The last time I worked with dreamweaver was 6 years ago, before I switched to phpnuke. After phpnuke I went from typo3 to drupal. But still, I am not very content with drupal. The cms just needs too many queries and is not very easy to learn for beginners. The release cycle of drupal is not easy to predict. Right now they are half year off their schedule.

  212. andrea Says:
    March 19th, 2009 at 1:06 pm

    If the writer really knew how to use dreamweaver wouldn’t have written this article, period.

    Sorry for the crappy english but it’s not my moter language

  213. RISC OS Says:
    March 19th, 2009 at 3:49 pm

    @Peter Bowyer

    Then use a real content managemnet system like TYPO3 and not a blogging tool like Drupal/Joomla

  214. potsK Says:
    March 19th, 2009 at 4:23 pm

    totally agree with the author of this article. that’s why I turned my back on dreamweaver years ago.

  215. Kwesi from ATL Says:
    March 19th, 2009 at 4:53 pm

    This is more alarmist rhetoric than anything else…what sincerely scares me is the fact that when I entered this field it was about the freedom to develop anything you want with anything you want…the democracy and free spirit of the web…as things progressed and cooler sites came about we all wanted to know “How did they do that?” and more importantly “How can I do that?”. But now it seems that with the advent of Web 2.0 ( Corporate Buzzword Jargon Alert!!! Any real developer knows that that term is for people who have never worked in the web industry but only know about what the news tells them about the web) it seems that content is king and the “if you can’t give me content then get out of my way” attitude is really hurting the look, feel and ultimately the tone of our beloved web. Pages are all starting to look the same…blocky grid based scrolling content monsters that give you what you need content wise but does not make me want to stay on the page nor revisit to see something new.

    This my dear brothers and sisters also affects our industry as a whole…Anyone of you that has worked on the web knows that this is a very thankless but full time job…articles that elevate the virtues of content over well thought out design treat the web as a disposable item that is only good for what it can provide right now than for a lifetime. That ultimately comes back to us designers, developers, programmers and countless web working masses as an attitude that our profession is a casual affair and disposable and the service we provide is at best meaningful within a blink of an eye or a click of a mouse. If content is so much more important than anything else then why did we leave the grey background and content full pages of Mosaic? Why is Flash still so relevant? I heard the same alarmist tone at the beginning of 2004 with many stating that “the web is dead”…Did that happen? Obviously not…so to say that Dreamweaver or any application that creates, employs and educates people about the web is dead is completely ludicrous.

    Honestly, I work with all tools to develop a site based on the clients requests…that’s the long and short of it. But to say that a piece of software is dead to get hits on your web story…that smacks of immaturity and a lack of credible experience within your subject.

  216. Sam Lewis Says:
    March 19th, 2009 at 7:35 pm

    For those that want to edit in a browser – good for you. What happens when you need to work offline – in a plane, a hotel without internet, your mom’s house? Your beloved javascript editor won’t help you then.

    Dreamweaver lets me edit anytime, anywhere (and I do work everywhere). Also, if you’re dealing with any ajax-type integration, there’s not another code editor (which is really what Dreamweaver is) that will allow you to view the Live code and then freeze it to interact with the CSS in a different state. If you haven’t looked at Dreamweaver since MX or MX2004, you don’t even know the product. It’s a fast code editor that allows you to also view in Webkit (Live view) as you’re working, CSS editor with great code hinting and ability to view of all rules that apply (or don’t apply) to an element. Related files lets you edit all files, whether CSS, javascript or includes while having the HTML code available side by side in the vertically split workspace.

    To the author – writing an article saying DW is irrelevant just because you build non-static sites just shows your development perspective. And your lack of understanding clients that actually want attractive, custom design. Dreamweaver is far from dying — it’s thriving, growing and adapting to the environmental changes within our industry. After the amazing release that was CS4, I can only anticipate with baited breath what they might be doing for the next release.

    And, oh yea – I integrate Wordpress, Drupal and other CMS/blog type applications all the time. I use Dreamweaver CS4. ’nuff said.

  217. Jason Says:
    March 19th, 2009 at 8:31 pm

    Exactly, I wrote about this back in September:

    I think a lot of people don’t understand that Dreamweaver is actually more limiting than enabling. If you’ve made the switch from tables to css for your designs, it’s only a matter of time until you realize that it’s fancy wizards are actually slowing you down. And why use such a kludgy tool like that for your design? If you use Photoshop, Illustrator or Fireworks to create your mockup, it’s then just a matter of rebuilding what you already see in HTML/CSS. Hands down, you’ll work faster and more creative with this technique. And if you’ve made it to that level, moving to a CMS isn’t so bad at all.

    Dreamweaver doesn’t have any serious support for dynamic content. Even if they decide to move more in that direction, expect it to happen VERY SLOWLY as they try to capitalize on adding this feature or that feature. Adobe is proprietary and thinking about its bottom end, while open source is out there innovating. Check out the Joomla, Drupal or Worpress extension directories if you have any questions!

  218. Stephanie Sullivan Says:
    March 19th, 2009 at 11:40 pm

    Jason – it’s amazing the level of misunderstanding that exists about Dreamweaver. You mention in your article your “comfort zone of drag and drop.” I would respectfully say that this is one of the misconceptions that gives DW a bad name. DW should not be used to drag and drop. That’s really old skool. DW CS4 has great features, a good CSS interface and fabulous time-saving code features. It’s nice for us visual types to have a view of the page while working, but editing really ought to be done in code view.

    The only “fancy wizards” in DW I use are accessibility prompts that make it simple for me to add things like alt attributes to images, etc. Dropping a data table in is quicker with the wizard as well since you can specify which row/column should have TH, add the summary and such if you’d like. CSS can be edited in a wizard if people would like, but I prefer either directly in the properties pane of the CSS Panel or typing directly in my CSS document (shown in the related files toolbar) and using DW’s code hinting and code completion. I would like to lay down a serious challenge for anyone using a regular code editor – try to out code me either typing directly into your Joomla/Drupal/Wordpress editors to create the code from your design (or your text editor of choice). There are many of us DW users that have found extreme time-saving features built into DW, use it for good and not evil… and we don’t find it limiting in the least.

    I see you offer DW training on your site, but from the sound of your post, your DW skills seem to be a couple versions back. As to the cost of DW, if people use PS/IL/FW, they likely buy the suite anyway. DW is included. :) The code swiftly written in DW, which has been created using the graphics program of your choice, is then integrated into the CMS – it’s a hand and glove relationship.

    I co-wrote a book teaching DW users how to best use the program to write standards-compliant, accessible markup and CSS. Whether you’re building static or dynamic sites, the principles are the same. (And looking at your markup, I would tell you to be careful with your .frontpagetext class that hides over half the content on your front page. The Goog’ll get ya!)

    Remember, different strokes for different folks. Don’t throw the baby out with the bathwater… and all that. Have a great weekend!

  219. Paul Says:
    March 20th, 2009 at 8:51 am

    I have to agree with the article. I taught courses in DW for 6 years, and I found myself losing interest in teaching the tool because when I would explain what was happening when something went wrong, my students would glaze over and complain about having to learn to code. I feel like Adobe cultivates this attitude with their marketing of all of their web products.

    Though it is true that the static HTML site model is going away, what the article points out is that DW since 4.0 has really been heaping on tools to make static pages act like dynamic pages. (XSLT support, WYSIWYG database tools, etc.) For this reason I understand the comparison and I have to agree that without alot of organization and planning creating a contribute / Dreamweaver system for a client is a risky endeavor. Because the system is a stateless one, client errors turn into developer’s headaches. I’m wary of any system that stores its information in the rendered page. (Not just Ct/DW, but redDot CMS for example does a similar thing)

    I have to say there is one really great thing about DW is the closing tag autocomplete. I’ve used many editors and I think this autocomplete is the most natural and is not used by many other editors. Where DW is falling behind is as an IDE. Compared with Aptana that refactors JS and PHP (because it’s built on Eclipse), DW seems like a child’s toy. When dreamweaver was conceived web coding was primarily inline scripting. With PHP 5 and JS frameworks that hack prototype, the Web2.0 coding environment is class based and requires a “smarter” tool. If Adobe doesn’t adopt the eclipse platform for DW (as they have for Flex / Air) they’ll find that develpers who are still using their IDE don’t upgrade. I’ve only opened CS4 once, and I don’t see any reason to do it again.

  220. Jason Says:
    March 21st, 2009 at 6:27 am

    Hi Stephanie,

    I appreciate what you have to say, and great sleuthing! As far as the hidden div, I think it’s pretty harmless. My intention isn’t to use a black hat trick to mess with Google. It’s simply to make up for the fact that I don’t have a lot of text on my home page. Bottom line is that the search engines want to know what the site is all about, so they can index correctly. You’re correct in that technically their algorithms might end up docking me (IMO because they are still a bit primitive). Honestly, I admit it was a bit of a lazy thing to do and if I get docked I’ll simply remove it and try something else.

    As far as your other comments, I certainly have respect for your knowledge and position but I have to disagree. I was only having a little bit of fun with “Comfort of Drag and Drop” and didn’t mean it to be taken literally (although there are STILL people using Photshop/Imageready to export their code). I’m well aware of how to create clean code with Dreameaver (I also dislike when people bag on it for this). I’m also well aware of the new features and had even used the CS4 beta before writing the article. I also know how to properly set up templating, libraries, use the server side behaviours, spry, code completetion/hinting (every code editor has this) and pretty much everything Dreamweaver has to offer. I still say it better evolve quickly or become obsolete.

    I know that many people are passionate about this subject, and I understand why. They’re used to it and don’t want to have to change! Heck, I totally understand this and it certainly wasn’t easy for me. But the bottom line is that DW doesn’t offer real dynamic support and I’ve been working w/it since Ultradev. It’s a toy when it comes to that, period. I won’t say that it doesn’t make a good code editor (even with a web app like a CMS, although they render design view useless), because it does. If someone wants to use it for that, it’s more than fine as I said in the article. The problem is I think Adobe is deluding a lot of people into a sense of false complacency to how professional web development works. More and more they’ll wake up to this when they see their clients demanding more and more web 2.0. Or… they’ll stick with design mock ups only and learn to work as a team.

    I suggest giving open source a closer look. It’s a breath of fresh air in a world where profit matters most. Open source is making everything easier for us, just from a slightly different angle than you’re used to with Adobe.

    p.s. the code editors of a CMS aren’t meant for real design. They’re mainly for clients to be able to make simple changes. By the way, you can’t even compare Contribute to a good CMS. With a CMS, you have the ability to get WAY more granular…thus making client changes much simpler. Think of a photo gallery that gives the client separate fields to enter for title, caption, description, category (and then files it). When they upload a single image, it gets resized to two versions, thumbnail and bigger image. Maybe they can even choose certain featured gallery images for a special display on the home page. And that’s just one small example of the level of integration you can get. Sure there are a few DW extensions out there, but trust me they don’t compare.

  221. Jason Says:
    March 21st, 2009 at 8:21 am

    Hi Stephanie, one more thing. I’m really not trying to argue with you, but I think doing a little more research could be really enlightening. Don’t take it personally, because I know you’re good at what you do.

    “I would like to lay down a serious challenge for anyone using a regular code editor – try to out code me”

    “Dropping a data table in is quicker with the wizard”

    Ok, but I’d have ahh… kick your butt! :) That is at least if the goal wasn’t something very, very basic. The tables that you get “dropped” with a CMS are unimaginable with Dreameaver. How’s “it’s already done before I even start” going to fare in our race ;) That’s the thing with a CMS. So much is already done for you before you begin. What you do mainly, is simply “hook” into the features with your design. The admin interface for it all is also created before you even begin. Simply use what you need, and there are many extensions to add all sorts of functionality.

    As for the css aides, they’re good for learning. I admit to still using them a bit…but it’s really much quicker when you’re typing, copying, moving, renaming styles in code view. Creating much of the HTML I also find much faster to type. Any decent editor has snippets which you can use for the kludgy stuff like doctype. As far as theme creating, I’d personally much rather use Photoshop/Illustrator anyway…cause I DO like to drag and drop when I can.

    Hate to say it, but it’s really a modern day John Henry race.

  222. History of HTML and the future of editors « Wired & Less Says:
    March 22nd, 2009 at 12:29 pm

    [...] are only so many things you can do with HTML. But, static sites are becoming obsolete. Tom Arah writes on his blog about one of the greatest HTML editors ever, Dreamweaver,  that just is not suited for the web 2.0 [...]

  223. dagli editor visuali agli ambienti integrati di sviluppo | soluzioniweb | e-xtrategy Says:
    March 24th, 2009 at 9:05 am

    [...] spunto dall’articolo “i’m sorry but dreamweaver is dying” di tom arah approfitto per fare una piccola riflessione sui software per la [...]

  224. Pete Markiewicz Says:
    March 24th, 2009 at 3:23 pm

    There are actually two trends – the CMS model and the Web Services model. In the CMS model, templates are constructed within the CMS, server-side. This places very specific constraints on available design patterns.

    For example, Joomla sites are implicitly designed for portal-style websites, and are difficult to modify in other directions. E-commerce packages like Magento are just specialized CMS systems, and have similar limits to being modified to arbitrary design patterns. ASP.NET is like a super-CMS in many ways.

    The other trend is to grab the same data using a Web Service and Ajax, and construct a completely arbitrary page, server-side by manipulating the JavaScript DOM. In this case the designer gets full flexibility of design back, but the trade-off is that they have to do lots of JavaScript programming.

    In either case, static web pages are on their way out. XHTML is moving to a model where it does NO formatting at all – in time, even the and tags will disappear. Everything in XHTML will be a collection of s and s, and HTML authoring will be pure information design. CSS will provide all the presentation, and JavaScript will provide all the interactivity and behavior.

    BTW, most Joomla templates use a lot of Ajax, so to create CMS you need the other skill.

    BTW, Flash has a similar trend. . AS3 looks a LOT like Visual C#, and the XML object in Flash can access web services via AS3 similar to JavaScript. In my classes, I let students use either XHTML/Ajax or Flash/AS3 XML to construct mashups.

  225. Rob Stocks Says:
    March 26th, 2009 at 10:34 pm

    There will always be a roll for Dreamweaver because there will always be a roll for talented designers. We provide a CMS ( but went to great lengths to create a Dreamweaver Extention Toolbar to make it easy for designers to deploy. This gives companies the best of both worlds. A killer design from a talented designer, and a great CMS.

  226. Pedro Matos Says:
    March 27th, 2009 at 1:51 pm

    It may be true that Dreamweaver is dying, and then again may be not. One thing is clear static pages have their uses and it will be a long time before they disappear. An example is when one goes to many official movie sites where a trailer is posted. The site as a whole might consist of one to five static pages and the movie trailer. The page is such that the content in it will not change dramatically over time, or the ability of content management is unnecessary. Another example is that email campaigns don’t build themselves. The same goes for content management systems. Someone has to come in, design it, build it, ect….

    For the everyday user, Dreamweaver is dying, but for developers it is far from it as one might need to implement new code for a new service that may not be available out-of-the-box from the CMS.

    I don’t believe Dreamweaver is dying, but more that it is evolving with the times. Abode might make so radical change that we as designers and developers are not aware of at this time. Only time can tell us whether Dreamweaver will die, or evolve into something else.

  227. I Hate Php! A Beginner's Guide To PHP & MySQL. | Says:
    March 29th, 2009 at 10:33 pm

    [...] I’m sorry but Dreamweaver is dying | PC Pro blogPosts about Programming from google blogs as of March 20, 2009 « [...]

  228. Death of Dreamweaver-Interview with Jeffrey Zeldman, Author Publisher, A List Apart | Web Professional Minute Says:
    March 30th, 2009 at 11:35 pm

    [...] Jeffrey Zeldman, Author Publisher of the magazine, A List Apart. I asked Jeffrey to comment on a few articles floating around regarding the death of Dreamweaver. Special thanks to Jeri Hastava, WOW member and Webmaster at [...]

  229. cold fusion mx web hosting Says:
    April 2nd, 2009 at 6:28 am

    cold fusion mx web hosting…

    I never thought I will agree with this opinion, but you know… I agree partially now…

  230. Aniseed Training Says:
    April 2nd, 2009 at 6:30 pm

    If you’re on a Mac and tired of Dreamweaver try RapidWeaver. For website design it’s a real eye-opener and allows a huge amount of web 2.0 functionality as well as CMS and use of Google and Yahoo’s online apps to be brought right into the programme making many CMS options available for updating pages, calenders, image galleries. As a long-time Dreamweaver user RapidWeaver was like a breath of fresh air. It’s got Accordians and many other spry-type goodies available (but without the quite unbelievably fiendish editing system that Dreamwaver has)

  231. Layout | hilpers Says:
    April 6th, 2009 at 9:02 am

    [...] is all flash) Why bother, when there are better free alternatives, like Drupal and Joomla?…aver-is-dying/ — Facts are sacred … but comment [...]

  232. The Fantastico route to Web 2.0 | PC Pro blog Says:
    April 10th, 2009 at 1:29 pm

    [...] I upset a lot of web designers by saying that Dreamweaver is reaching the end of its dominance and that the future for website production (complete with crucial web 2.0 functionality such as [...]

  233. gnobgnob Says:
    April 14th, 2009 at 7:17 am

    I bet some of those Joomla, Drupal… cms developers are using DreamWeaver to create modules and plugins/extensions.

  234. Web Design Dubai Says:
    April 23rd, 2009 at 5:08 am

    The bottom line is that the old model of the central webmaster hand-spinning every page of every website and, worse, manually adding the navigation necessary to help users find it, just isn’t scalable or viable. The only feasible course for the future is for content to be posted by the content contributor, whether that’s the site owner or site visitors, and for the best possible navigation to be constructed around that content on the fly.

  235. cepcoicroek Says:
    May 2nd, 2009 at 8:00 pm

    [...] as static sites. Its failure was its WYSIWYG – it wasn’t. I was a fan for years n years, but it just did…

  236. ChomiAlgoglok Says:
    May 2nd, 2009 at 8:31 pm

    [...] 2009 at 3:22 pm

    Dreamweaver is alive and well in corporate America (what’s left of i…

  237. FUSYELEGRES Says:
    May 2nd, 2009 at 9:36 pm

    [...] years n years, but it just didn’t get the job done.
    Switched to texmate n csse…

  238. VofGeofsbow Says:
    May 2nd, 2009 at 10:33 pm

    [...] last year or two, and it has been golden. A great free editor, based on eclipse. They also have built an Ajax s…

  239. Shinnimbitise Says:
    May 3rd, 2009 at 8:44 am

    [...] n cssedit, wouldn’t think of going back. DW really did its job for years (I used …

  240. bikeman Says:
    May 6th, 2009 at 6:44 pm

    Open sourced CMSs have a long way to go before I switch from DW (yes I do use it professionally for file management of dynamic sites) for 2 reasons:

    1.The appalling lack of quality control (with Joomla) which results in a constant fixes breaking other functions.
    2. Lack of security as a result of clients not willing to pay for constant updates.
    3. The general ‘fk off and use something else’ that open source CMS developers have when their software isn’t up to scratch.

  241. bikeman2 Says:
    May 6th, 2009 at 6:51 pm

    There is nothing that a CMS can do that DW can’t!!!

    With DW’s built in PHP and ASP behavours I can easily create dynamic websites with browser based content management, dynamic menus, RSS/XML data feeds, AJAX functions etc etc

    The author of this article doesn’t know what he is talking about.

  242. week eight thoughts « Reneespeak’s Blog Says:
    May 12th, 2009 at 8:14 am

    [...] I came across some interesting opinions. On March 5th, Tom Arah posted an article on PC Pro called “I’m sorry but Dreamweaver is dying”. As a designer he states that Dreamweaver is the best HTML/CSS page-based editor available, and [...]

  243. sherif mayika Says:
    May 12th, 2009 at 9:19 am

    Themegenie – the Advanced Dreamweaver extension for Drupal theming – Now Available For
    Dowload from here

    Themegenie – the Advanced Dreamweaver extension for Drupal theming

    Theming Drupal is no more a Herculean Task or tiresome job. Thmegenie makes Drupal themeing a breeze.

    Features at a glance

    • Create base theme files in a single click, fast.
    • Comes with Drupal template intelligence, hence high level of accuracy
    • Completely Programmer free. Do it as you design html pages in Dreamweaver.
    • Creating Regions is pretty simple.
    • Transform your dreams to themes without confusions, PSD to Themes possible.
    • With Themeenie you can create themes for your personal sites, blogs,
    • e-commerces, wikis, forums and many more. It’s your choice!.
    • Real-time drupal view – View your theme using Dreamweavers’ design view just like you see it on a drupal site.
    • Create page modules and regions in a click.
    • Browser specific css.
    • override template files.
    • Theming blocks, nodes and comments has unlimited possibilities with a few default styles you can choose from. Rounded, zebra, collapse and so on.
    • Nine styles of menus with unlimited CSS possibilities including Suck/Super fishes.
    • Theme Search, Forum, Poll.
    • The maintenance page.
    • And much more
    Coming features
    - opt fixed, elastic, fluid regions
    - Integrate color module
    - Create theme settings
    - Tabbed Region
    - Collapsible Regions
    - Css Switch
    - Import Wordpress Themes
    - Import Joomla templates
    - theme Subthemes

  244. lebisol Says:
    May 19th, 2009 at 7:00 pm

    The only thing left of my dear UDW/DW is the code view…the rest is Adobe fluff relevant only in Adobe world.
    There are CMSs and then there are CMSs…Open Source will always suffer from Open Source Developer Syndrome of “I got better things to do right now then help the community”.
    Dreamweaver is still the best rapid development tool if you are making sites by hand and not using frameworks and/or CMS but it is not a replacement for skills.

    Developing and designing sites is NOT a point-click-confirm process.
    Adobe needs to cut down the price by at least 70% if they want to stay in the game and in the tool set of developers (not = print designer trying to ‘put cool looking stuff on the web’).

    Today I fire DW only when someone hands me a table based design….
    for the rest:
    -cms of choice: ExpressionEngine :
    -tools: FF with Firebug and WeBuilder:

    At the end of the day…
    Only fools worship tools.

  245. Questions for all Web designers - DesignersTalk Says:
    June 8th, 2009 at 7:24 am

    [...] Sorry for not clearing things up – by resolution, I mean when you create the document (File -> New), what size do you make the image? Thanks for the replies guys. Also, what do you think about this? [...]

  246. Dreamweaver training Says:
    June 16th, 2009 at 11:59 am

    As a Dreamwevaer trainer and user for 10 years. I couldn’t disagree more. The way Adobe involves this core programs means they will be around for a long time.

  247. J Mitchell Says:
    July 1st, 2009 at 10:30 am

    Essentially this article says, use Drupal or Joomla if you want a CMS.

    Dreameaver is “Dead” if you want a CMS, beacuse it isn’t one and you have to write your own or maintain you own copyright.

    Obviously, likewise if you want to write your own code, especially dynamic code, you can’t use Drupal or Joomla beacuse they can’t do that either. Following the articles use of the word “Dying”, this means Joola and Drupal is dying!

    Basically both DW and CMS systems are good and have their uses.

  248. iphone downloads Says:
    July 10th, 2009 at 11:02 am

    iphone downloads…

    Awesome information you have here. Thanks for sharing….

  249. Fosia Says:
    July 29th, 2009 at 1:55 pm

    This is great. I was little upset that i can go to see the last comments in this blog so I see this comments is very excellent.

  250. CMS and CSS: Problem Solved | PC Pro blog Says:
    August 6th, 2009 at 8:05 pm

    [...] while back I wrote about my belief that the future for web authoring lies beyond static web pages with Web 2.0 and with the big three content management systems (CMS): [...]

  251. Marsh Says:
    August 10th, 2009 at 7:17 pm

    I read this article back in March and have monitored the comments to see how it would evolve. I am surprized to see the short sighted views of developer vs. designer that as persisted in many of the comment posts. CMS is here to stay but CMS is a very immature product. As much as the opensource world hates Microsoft, I think their is much to be learned by their focus and product evolution. They see that the future web is a workflow process and I don’t mean just updating content in a workflow/taskflow type process. What I mean is that they see design and application development as two diffierent skills that must go beyond co-existing, they must blend together in a shared development environment. Both Adobe and Microsoft suites are about building rich content and rich interfaces and they are begining to bring about a development workflow process environment within their suites respective suites that is creating a collaborative solution. All OpenSource CMS solutions suffer seriously by comparison when you look at the site development from a workflow collaboration perspective.

    Rich Content is the future of the web. Linking to YouTube for your video content works for some things, but as the web evolves and bandwidths increase, the need for much richer user video and graphical experience will be a reality and the need for those other suite tools like Photoshop, Illlustrator, Flash, Soundbooth and Premeier will become ever more important. When the bandwidth permits the web to go HD and vector graphics replace gifs and jpgs then the need for designer and developer to collaborate will be critical. Both Adobe and Microsoft see this and their suite of tools are evolving to address this content need all while looking more closely at the workflow of website collaborative devevelopment.

    Microsoft has now made SharePoint desinger a free tool allowing designer and developer in the .Net framework to work much closer than they ever have in the past. Moving development content between Visual Studio and SharePoint designer is getting easier and better with each new version. Repurposing content into the next generation SharePoint CMS is far more dynamic than any current CMS on the market, opensource or vendor based. The content owners would all rather use their daily tools like Word and Excel to do their work rather than having to learn and use any CMS interface to copy and past content into a website template. Microsoft is giving them the ability to repurpose that type of content directly from their tool of choice without ever having to see a CMS interface. Microsoft is leveraging that this type of user behavior will push their next generation CMS solution into the mainstream of corporate and goverment environments. Content Management is far more involved than just basic web site content.

    You might think that I am not a OpenSource CMS fan and you would be wrong. As long as their are organizations who can’t afford the Adobe / Microsoft solutions their will be a need for CMS. But that doesn’t equate to the Death of Dreamweaver/Adobe Suite or the Microsoft Expression Suite of tools. The environments are different and the needs are different. I have mentioned Adobe and Microsoft a great deal, but don’t overlook google. As cloud computing becomes more of reality, CMS will become an even more important component. My files must live where my cloud computing applications can get to them.

    So is Dreamweaver dead… not by a long shot. I won’t be giving it up anytime soon.

  252. Web Design Quote Says:
    August 13th, 2009 at 10:19 am

    This article is really nice and very important information Dreamweaver.thanks for sharing.

  253. Karachi Hotels Says:
    August 17th, 2009 at 4:29 pm

    I think dreamweaver is sexy. It has so many features that wordpress cant have in ages. Long live Dreamweaver

  254. zoot suit Says:
    August 18th, 2009 at 10:44 am

    Like everything else on the internet. Things change and evolve. Dreamweaver may have been around for a while but it will still work for most people. Those who crave more bells and whistles will have to look elsewhere like Drupal.

  255. Web Host Review Says:
    August 18th, 2009 at 11:47 pm

    I still find DreamWeaver very useful. I like to use it to generate HTML code that I don’t know how to code manually. However, it is definitely being displaced by software such as Wordpress or Joomla.

  256. Jason Says:
    August 27th, 2009 at 5:10 pm

    Obviously, those people on here comparing Dreamweaver (or any IDE, for that matter) to a CMS has no experience in Web development. As a Web developer for the past six years, I can tell you that the comparison is totally nuts. Dreamweaver may have a LOT of competition from Eclipse, but there’s no competition from Joomla, Drupal, WordPress, etc. How ELSE are you going to edit the code in a CMS? Notepad? A development IDE is still the best answer, and Dreamweaver still offers a lot in that category. One thing I can’t stand is people writing blogs about something for which they know very little about. Save your opinions for people who care.

  257. Jason Says:
    August 27th, 2009 at 5:17 pm

    Saying Dreamweaver is being replaced by a CMS is like saying wheels are being replaced by cars.

  258. Jim Spence Says:
    August 27th, 2009 at 7:46 pm

    Jim Spence…

    Be sure to read Webmaster Book ( ) before writing your own comments!…

  259. Website Redesign Says:
    August 28th, 2009 at 9:07 am

    Good info post. Thanks so much.

  260. Twitter Trackbacks for I’m sorry but Dreamweaver is dying | PC Pro blog [] on Says:
    August 28th, 2009 at 5:32 pm

    [...] I’m sorry but Dreamweaver is dying | PC Pro blog – view page – cached I’ve received a number of very kind emails regarding my last digital design column, but I have to admit that a couple made me feel slightly — From the page [...]

  261. iphone look alike Says:
    August 30th, 2009 at 12:00 pm

    iphone look alike…

    I have been looking for a long time and found this post. Thanks a lot….

  262. host the tops Says:
    September 2nd, 2009 at 10:26 am

    i am using Notepad++ as my web editor, its almost the same as dreamweaver, as you dont need the design-view

  263. Business blog Says:
    September 24th, 2009 at 5:49 pm

    Can I ask whether Drumla is a web tool like dreamweaver or is it more like say Wordpress? I use both of these as I have websites built using dreamweaver and I have a couple of blogs I have built using Wordpress – I was thinking about upgrading my Dreamweaver and came across this article which has got me thinkingof now using Drupal – please comment, thank you

  264. Mollom: What’s in a Name? | PC Pro blog Says:
    October 16th, 2009 at 4:25 pm

    [...] man behind Drupal. Drupal is the most powerful open source content management system and IMHO deserves to replace Dreamweaver as the web designer’s tool of choice. In fact, as far I am concerned, the major factor [...]

  265. Tekshek Says:
    October 21st, 2009 at 3:13 pm

    in my opinion dreamweaver is still best

  266. Michele Says:
    November 5th, 2009 at 5:02 am

    yep – Dreamweaver will be around, not matter what new ’solutions’ come on the market. The DW community is very active ergo evolving too and pulling right along side.
    Moronic to compare DW to anything but a developer tool. Use it every day [only thing am sorry is that GoLive is no more for the css].
    Other than that, I have yet to build a site where I have not used DW for the base design. And I designed in nearly all CMS’s etc over the years since 1993.
    Plus, just look at all the fuss one has to make to render top SEO. If you do your theming/templating right the first place in DW, you don’t have to worry about it.
    But then again, if you only look for the ‘editor’ function of DW, well, you can get a lot cheaper software for ‘cheaper’ websites, because that’s then exactly what you will produce.
    Aren’t we all so concerned about indexin/ search enghine, well, guess what – I never heard that any engine could not read html. But sure a lot of cms reading failures/lapses, and you wind up with yet another module to install.
    I can automate everything in DW.
    I have built some site a while back in Typo3 – and know it alright – but outright hated it when creating content. How circumstantial versus DW auto content. What takes 3 hours in Typo3, takes me 10 min in DW. [am using Typo3 only as one example]
    So – YES-YES-YES- I will use DW for a very long time to come still.

  267. Says:
    November 10th, 2009 at 9:11 pm

    Dreamweaver will never die for me because i had a hard enough time learning to use it in the first place.

  268. Sergey Says:
    November 20th, 2009 at 1:28 pm

    Yes I agree with you. An interesting blog and to read interestingly and the main thing all articles in a theme

  269. Computer Support Says:
    November 25th, 2009 at 1:43 pm

    dreamweaver always best!!!!

  270. The Capable Manager Says:
    January 28th, 2010 at 3:39 pm

    As a complete novice, I built a couple of sites in DW and they listed quickly in Google even though the content was very light and simple. Now poeople say that joomla is the way forward free and CMS, but others say good SEO in joomla is really hard to achieve – and I have found this with sites that I have had built for clients. Why is this, and how can I get future functionality that is alluded to in the blog with the ease of ranking high?

  271. Werbegeschenke Says:
    February 8th, 2010 at 3:49 pm

    Great post, keep up the good work!!

  272. Òóðû â Èñïàíèþ Says:
    February 23rd, 2010 at 2:48 pm

    Êàíàðñêèå îñòðîâà…


  273. SEO Generation Says:
    March 1st, 2010 at 3:19 pm

    Open sourced CMSs have a long way to go before I switch from DW (yes I do use it professionally for file management of dynamic sites) for 2 reasons:

    1.The appalling lack of quality control (with Joomla) which results in a constant fixes breaking other functions.
    2. Lack of security as a result of clients not willing to pay for constant updates.
    3. The general ‘fk off and use something else’ that open source CMS developers have when their software isn’t up to scratch.

  274. Al Kracker Says:
    March 12th, 2010 at 2:54 am

    You luddite you! How dare you expose the bare truth! No seriously, being a traditional print designer then a DW disciple, I am shocked at your notion but eternally grateful for this eye opener. There is none so blind as he who cannot see! I’ve already put in my app. for a hack license. I’ll definitely be making more money driving a cab than designing websites in DW.

  275. rent a car madrid Says:
    March 17th, 2010 at 12:41 pm

    Dreamweaver, is a fancy text editor.We, web designers use it for code-hinting,it is not a layout tools.

  276. Paul Dean Says:
    April 1st, 2010 at 10:38 am

    You have to check out a company called Business Catalyst.
    It is a web 2.0 company that caters for web app integration into websites. You can use Dreamweaver to design the site including using all the features of Business catalyst via triangle. Why can you do this? Because Business catalyst – previously good barry is now owned by Adobe.
    In my view, it kind of flattens the argument.

  277. Brian Says:
    April 9th, 2010 at 5:50 pm

    Dreamweaver is not dead. I use it every day to build code faster. It helps me save time so I’m making less mistakes. As long as there’s code for web, Dreamweaver will always have a use.

  278. Novuss Says:
    May 5th, 2010 at 3:18 pm

    Many of my colleagues work at the university wíth dreamwaver…no sign of beeing death!

  279. alex grey art style Says:
    May 27th, 2010 at 4:40 pm

    alex grey art style…

    [...] I’m sorry but Dreamweaver is dying | PC Pro blog for alex grey art style on alex grey art style [...]…

  280. Melanie Says:
    June 3rd, 2010 at 3:03 pm

    No problem for me. Dreamweaver is getting more and more useless because childrens of today learning html without WYSIWYG – and thats the right way. In my first days of HTML I was using Frontpage for my first sites… Long ago.

  281. career Says:
    June 8th, 2010 at 12:34 am



  282. xpert4dent Says:
    June 28th, 2010 at 7:54 pm

    Dreamweaver is dying?? Good, go back to working in BurgerKing and let the professionals do all the work.

  283. Deal Peter Says:
    July 9th, 2010 at 12:01 pm

    realy nice article! dreamweaver ist just awesome

  284. Chris Edwards Says:
    July 12th, 2010 at 2:47 pm

    Don’t like CMS like joomla and drupal, I prefer to code using mysql and PHP using dreamweaver. I find that the CMS use overly bloated code to produce simple functions.
    Also you are entrusting your website security to the people who write CMS add-ons.
    With regard to re-iventing the wheel by designing your own code, no need to do that either, when you write your own login/join script you keep it to use again and again on other websites.
    By using dreamweaver you have to learn to code in your given scripting language of choice andby doing this you gain a better understanding of both the code and website security.
    I will accept that it is faster and easier to use a CMS like Joomla and Drupal but not better.

  285. Bowraven Says:
    August 4th, 2010 at 1:31 am

    I came across this article,as I was considering upgrading my Dreamweaver, but having got to grips with using Wordpress, I am now thinking that you have a real point here, although, I do have some websites that do not use Wordpress and at some point will need updating so I am now wondering whether to upgradeor not!

  286. Rick Bellefond Says:
    August 10th, 2010 at 11:26 am

    We currently have a website,, that has about 80 pages or so and has some really good seo rankings for some very competitive keys that is currently done using FrontPage. Since FrontPage is not supported anymore and our website has an old look and feel we want to have our website have a newer, cleaner look and feel without giving up our seo rankings. We wanted to be able to maintain our same url names including the .htm extensions. We looked at having our site done in WordPress or Joomla and was told we would run into problems keeping the url names the same so we hired a company who is using Dreamweaver to create a custom CMS for us using Dreameaver. Is this a good idea? Are we leaving one dying platform for another?

  287. NonProfit Says:
    August 31st, 2010 at 5:13 pm

    Chris Edwards (@285),

    Druapl works because people work better in together.

    I have a whole community of developers peer-reviewing the code I will implement. Before I ever look at a module, It’s been deployed on thousands of sites. With that comes hundreds of bug reports/feature requests and security concerns. Far more than any one individual could ever identify, let alone address.

    The web has moved past the point were a shop of two or three really smart people can work together and remain relevant. As expectations have grown, so has the need to develop in larger communities. By working together, individual developers, like myself, can do amazing things.

    I urge you to adapt or your business will die.

  288. shaun Says:
    September 23rd, 2010 at 2:16 pm

    Dreamweaver is a great tool for web design although I have to admit I have used word press more lately.

  289. Mike Says:
    October 2nd, 2010 at 3:08 pm

    Wordpress and Blogger rule the blogsphere!

  290. George Melchers Says:
    November 29th, 2010 at 6:39 am

    Yes I agree with crycom , a browser is a browser and you can not edit a CMS theme in the browser alone and that’s why I challeged Mr.Tom Arah that if he can show a tutorials on how to create a theme of a drupal site in the browser then he’s right. Dreamweaver is Dying! just show me how to create a complete drupal template by using a browser alone.

  291. Twayne Says:
    December 10th, 2010 at 6:14 pm

    Hmm, it might be the industry is due for a shaking out, but I have to disagree with a lot of things here.

    1. CMS is far from all it’s hyped up to be. For the reasons already given in other posts and others not mentioned (there are a lot) my evaluation of 3 CMS apps was a dismal failure.
    Newbies, or those who don’t know what other apps can give you might be well satisfied with CMS at least untiil they discover the power and features of a good HTML/PHP/ASP generator.

    2. I somehow doubt the old 2009 post about Dreamweaver dying simply because of the size of its userbase. Those who have it, will continue to use it for some time to come, official support being available or not. I consider Dreamweaver “good”; nearly as “good” as my chosen app, which is also appearing “dead”, moreso than Dreamweaver. That’s Fusion 11 originally from Netobjects but now owned by apparently, at last count.

    3. Learning HTML and PHP or ASP or both, are something every single web site author should know, regardless of the app/s they use to generate the final code.

    4. NVU or its predecessor is probably
    the best newbie app around for wysisyg editors with a considerable amount of helpers, etc., and will create a perfectly fine web site with any features a web browser can interpret. It even helps you thru setting up all the meta tags, etc., that you need. Weak on security, but every app I’ve found to date is weak in that area, forcing the user to use PHP or suffer the inherent hacks and intrusions, mostly forms of code injection, a tough area for newbies to get their heads around.
    CMS from what I see is the weakest there is for security. There seems to just be NO security code for the CMS apps; a little field checking but that’s all.

    Well, that’s my 2 ¢ for today, anyway.

  292. CNA Training Says:
    December 16th, 2010 at 4:06 am

    Images removed? I see red crosses

  293. mieszkania pruszków Says:
    December 16th, 2010 at 7:03 pm

    Good an very informative post. I will come back to your blog regullary. One thing: I do not exactly know what do you mean in the second paragraph. Could you please exmplain your opinion?

  294. John Says:
    March 26th, 2011 at 1:38 am

    It’s such a tired cliche to simply call it wisywig and decry the laziness of its users. Dreamweaver is an absolutely brilliant program that competent web designers and programmers understand how to use to create clean, efficient code and robust sites with complex functionality. It serves a different purpose than CMS and Blogs, which are often horribly bloated code-wise, and can be nightmarishly complex to maintain. It’s such a brilliant and powerful program when used properly that I find it difficult to take any author that would write something like this seriously.

  295. John Says:
    March 26th, 2011 at 1:48 am

    Wow, just reading these comments and the degree of ignorance is appalling. Makes me wonder if 90% of the respondents have any idea what they’re talking about. Good thing people that do know what they’re doing still use powerful, well designed tools like Dreamweaver.

  296. John Says:
    March 26th, 2011 at 1:51 am

    FYI give me the average Wordpress page and I can recreate it in Dreamweaver with 75% less code.

  297. Clearfind Says:
    March 31st, 2011 at 4:59 pm

    Agree wholeheartedly with John. How about this… perhaps for many of use seasoned designers / developers, Dreamweaver is but one of many tools at our disposal. As it should be.

  298. Josh Says:
    October 3rd, 2011 at 9:01 pm

    I have Dreamweaver too, as much as I hate Frontpage and all that crap.
    We should all revert back to good ol’ Notepad!

  299. Turod Says:
    October 8th, 2011 at 12:36 am

    Well, I am using Dreamweaver, still and I have to say to you that those CMS totally SUCK. For a developer or site builder to use CMS’s is much more pain than using the true tools of web design, as dreamweaver. A CMS is an application, that solves a certain problem, like online stores, blogs, but what you do when you want a complete NEW and UNIQUE design ? Do you start learning a CMS and remain dependent on it and beg the developers to do some tools, learn that tool, just to solve a problem ?
    I believe and from my experience, that CMS’s bring more problems than they solve, when you want to create something unique. They are very limiting and in the process of adapting them, you rather learn how to hack, than how to create something properly. Is like, instead of building a car int he factory, you would get an old one and try to tune it, in the end spending more for it, than for a new one and and it’s still an old car int he end, limited to what used to be it’s purpose, when created.
    CMS’s are for lazy, mainly ignorant “developers”, when they use them extensively, I think. A true developer and a true design is made from scratch, with tools like Dreamweaver. Cms’s are for blogs, ecommerce and limited stuff, but for unique design you need to know the stuff and that stuff is put to practice in Dreamweaver, so we should rather see some cms’s stop being developed, than Dreamweaver or MS tools.

  300. Charles Miniard Says:
    November 2nd, 2011 at 5:23 pm

    Right now it looks like Expression Engine is the top blogging platform out there right now. (from what I’ve read) Is that what you are using on your blog?

  301. Funnelweb Creations Says:
    December 20th, 2011 at 2:56 pm

    As a web developer I have to say that I don’t totally agree with this article. Whilst we use Joomla for many sites that we create, it is December 2011 and I estimate 75% of the sites we create are done so using Dreamweaver CS4.

    To be fair most of our clients are looking for very simple sites (5-10 pages) so on this scale we still think DW suits our needs best. Interesting article thought!

  302. Ashish Singh Says:
    January 1st, 2012 at 1:01 pm

    The writer has no clue about web development. CMS is not viable for all projects. I’ve been using Dreamweaver since the hay-days of Macromedia and like any program it is just that – Garbage In Garbage Out ! If you want tailor-made ready to customize solutions I’m sure there are millions of options out there. Next time please don’t waste the time of other readers looking for vaible solution. And what exactly is Web 2.0 ???

  303. MadlanaJr Says:
    January 19th, 2012 at 4:16 pm

    the writer of this article is a sad ignorant idiot with no code knowledge whatsoever. if he knew even 1 function of php or javascript he’d know that dreamweaver isnt for making static websites. is he even a web developer for starters.?

  304. Casey Says:
    February 14th, 2012 at 12:47 am

    @Ashish singh Web 2 = user generated…

  305. Hubert Craft Says:
    March 2nd, 2012 at 5:14 pm

    Some tips i have observed in terms of pc memory is the fact there are specifications such as SDRAM, DDR or anything else, that must match the specific features of the mother board. If the personal computer’s motherboard is kind of current and there are no os issues, replacing the memory literally usually takes under sixty minutes. It’s among the easiest pc upgrade treatments one can picture. Thanks for sharing your ideas.

  306. Michel Says:
    July 30th, 2012 at 4:37 pm

    Dreamweaver is such a well-rounded program and the platform is so familiar that if it does disappear, chances are that sometinhg very similar but maybe more Noob friendly would appear.

  307. Christina Says:
    August 16th, 2012 at 6:04 pm

    I’ve never used DW, I started doing websites in the mid-90s with straight up HTML. After that I went to GoLive and was so frustrated with it I just hired programmers after that. I’m more a designer.

    After having so many problems with designers, I finally started building websites with Wordpress and Blogger. I can now design a website and have it live in less than 3 days.

    No software to update, the learning curve was very little, I use my own Photoshop graphics, no programmer and best of all it’s free. I didn’t have to pay almost $400 for software that doesn’t allow RSS feeds (or at least that’s what I’m reading) or interaction with social media.

    The cloud is definitely where it’s at right now.

  308. Christina Says:
    August 16th, 2012 at 6:05 pm

    I meant to say “After having so many problems with ‘programmers’…..”

  309. ducsu Says:
    September 11th, 2012 at 6:40 am

    Intesesting topic. I have usesd Dreamweaver in the past when I first tackle on creating my first webpage. I knew nothing of course but a handful of web desiginers were using Dreamweaver as their web tool. It is a great tool but it doesn’t give you the freedom as if you are using a simple notepad like notepad++ to tweak your code as I soon find out later.

  310. David E. Says:
    October 23rd, 2012 at 11:10 am

    Don’t think it’s dying, but the fact is that less people uses Dreamweaver every day, probably because there are easier ways to develop websites like the popular WordPress and Joomla CMS. Anyway it’s still a good tool for developers, for example if you are creating/editing a WP or Joomla theme/template Dreamweaver is still one of the best tools for that. Dreamweaver may be also the choice for custom projects where a public CMS isn’t situable. It isn’t a “required” development software nowadays, but it may increase the productivity in many cases and that will give Dreamweaver more life time… with less users but it will be still in the market for a while. PD: I’m a bit surprised to not see a mention to WP as one of the main causes of the Dreamweaver drop.

  311. discount magazine subscriptions Says:
    December 4th, 2012 at 1:34 am

    Your method of describing the whole thing in this post is truly pleasant,
    all be capable of easily be aware of it, Thanks a lot.

  312. Fidel Macchiaroli Says:
    July 10th, 2013 at 1:07 am

    Hi,pls want to ask if there is any a single for java,if there isn’t,pls when will there be

  313. Morocco desert tours Says:
    July 20th, 2013 at 3:30 pm

    I was using dreamweaver on the past, but now you don’t feel free designing an interesting template with it. You can only make very simple template website but not design template.

  314. Unimpressed Says:
    July 23rd, 2013 at 6:18 pm

    Well, it’s 2013 and I’m still using DW since the Macromedia days – been over a decade. Simple site? Complex dynamic site? Custom CMS? I build ‘em all, spending 80% of my time in code view writing PHP and ASP.

    Oh, I’m the designer and the developer by the way.

    “Acheive results with a CMS I couldn’t produce on my own?” What am I developing exactly? Anything I want, if I have enough MEs?

    Hate Adobe? Fine, but quit writing such ignorant articles that compare apples to oranges and pro usage to noob usage.

  315. Digitalpoin8 Says:
    October 14th, 2013 at 11:06 am

    Images removed?

  316. Mike Says:
    November 6th, 2013 at 3:41 am

    I’ve used DW for my websites in the passed but lately for all my investment sites I’ve been switching over to Wordpress.


Leave a Reply

Spam Protection by WP-SpamFree

* required fields

* Will not be published






Your email:

Your password:

remember me


Hitwise Top 10 Website 2010