First Details on DreamWeaver CS4

Back in June 2008, Adobe revealed the first details of the next Dreamweaver less than six months after shipping CS3 — and the announcement was entirely about what was being taken out. Looking back from 2026, that cull turned out to be a preview of the whole product category’s decline. Here is what the 2008 changes were, and where everything landed.

What got cut, and why it was right

Two long-standing features were headed for the chop: Layout Mode and Timelines. Both were sensible removals. Layout Mode was a well-intentioned attempt to let graphic designers lay out pages the way they would in desktop publishing; the problem was the horrendous spaghetti code it generated behind the scenes. If you got the design right the first time, the code was stable, but as soon as you changed anything — and who ever stopped at a first attempt? — the page fell apart like a house of cards. Timelines relied on similarly outdated code for animation, which even then belonged in Flash.

More controversially, Adobe dropped ASP.NET support entirely, and JSP alongside it. The ASP.NET gripe went back years: Dreamweaver 8 shipped before ASP.NET 2.0 was finalized, and CS3 — a year and a half later — still only supported ASP.NET 1.1. Rather than keep second-rate support frozen in the past, Adobe cut it. The message was consistent: no support beats half-hearted support.

The speculation at the time centered on PHP, ColdFusion and updated server behaviors, plus a UI refresh (the panel-based interface shared with Photoshop and InDesign) and a new version of Spry, Adobe’s Ajax framework. All of that arrived in CS4 in late 2008. What nobody in the piece predicted was how little it would end up mattering.

Where it all went

• Adobe ended Dreamweaver development. Adobe announced in 2021 that Dreamweaver would receive no new features — maintenance mode only. The 2008 cuts bought the product a decade, not a future.
• Layout Mode lost to CSS itself. Flexbox (mainstream by 2015) and CSS Grid (2017) delivered exactly what Layout Mode promised — visual, designer-friendly layout — as standards, with no proprietary code generation. The idea was right; the implementation was doomed.
• Timelines lost to everything. Flash itself died (officially end-of-life December 31, 2020), and animation moved to CSS transitions, JavaScript, and later Web Animations API.
• Spry was discontinued around 2012–2013, obsolete almost on arrival once jQuery became the de facto standard for DOM manipulation and Ajax.
• ASP.NET and JSP outlived their Dreamweaver support. ASP.NET is still a first-class Microsoft stack in 2026; it simply moved past visual tooling — the same trajectory as the rest of web development.

The lesson from 2008

The 2008 piece ended with a shopping list: better server-side language support, standards-compliant HTML and CSS output, a Property inspector without deprecated attributes. None of it was wrong — it was just aimed at a world where developers still wanted a WYSIWYG web editor at all. Within a few years, hand-written code with live tooling (and later, frameworks that generate the DOM entirely) made that whole category of wish list irrelevant.

Dreamweaver CS4’s launch was, in retrospect, the product’s last significant moment. The cuts of 2008 were the correct triage — but triage is what you do when the patient is already in trouble.