I can't comment on Dreamweaver's stability since I haven't tried it.

However, GoLive has its issues. Run it for a few hours of intense work and watch it lock-up. I'm a long time GoLive user and I've just watched it get worse and worse from version 4 up to CS2. Bugs too numerous to mention. I can't trust it. I have to proof all the code by hand ... sometimes it writes garbage, and sometimes it deletes stuff in layout but leaves the corresponding content in the code. I certainly can't trust it with Javascript so I write my own implementing "tricks" that bypass GoLive's desires to re-write it all the time.

I can't think of one bug in PhotoShop or ImageReady yet I've found dozens in GoLive. It's a dog too. Funny how GoLive seems to run about 10 times slower than PhotoShop/ImageReady on the same processor. Spinning cursors galore.

Don't get me wrong, it has its pluses and it's still my editor of choice. But Adobe needs to do either a total GoLive rewrite, which seems unlikely at this point. Or make some hybrid/new creation that "looks" like GoLive but functions better- whatever they name it, it needs to work as well as the other parts of the Creative Suite.

Remember the old days with Adobe PageMill? LOL - The very first version of Adobe GoLive in OS 9 ran very well, kicked PageMill in the behind, and yet it was all downhill from there.

Change is welcome and I really hope that Adobe does a better job with this acquisition.

When Dreamweaver 8 came out, I forced myself to use it rather than GoLive - which has been serving me very well for the previous 7 years or so.

Even though I had been staunchly pro-GoLive prior to this changeover, I soon found that Dreamweaver is extremely good. I now prefer working in Dreamweaver and keep a copy of GoLive for the few things it is better at. GoLive has a great feature which allows to you see which files in the site have orphan links. Whilst Dreamweaver also has the ability to identify orphan links, it is much easier to use in GoLive. GoLive also has a nifty feature that allows you to see which are the incoming and outgoing links to the file of interest. Both these features make it easier when changing a site and replacing content with new content.

Other than that, I don't use GoLive anymore.

What I hope is that Dreamweaver doesn't start to produce bloated code.

It's recent update to 8.0.2 resulted in a very annoying pop up window on every page that is opened that has Flash content. It took some time to find out how to stop this pop up window from launching. Most methods to embed Flash content don't pass XHTML Strict validators, hence I use a recommended method from the A List Apart website, which works great. I'm in no particular rush to change this method until a similar better method is proposed.

Back in the days of rollover graphics, I used behaviours in GoLive and found that it built up a massive behaviour library script file that was 50-60kb. It was ridiculously bloated code and so, again, I used a friend's 1kb script that did rollovers much more efficiently.

I hope Adobe bears in mind that it is better to produce clean, accessible code than overkill bloat code when it updates Dreamweaver.

If you are moving over to Dreamweaver, keep in mind that the Assets window hogs the processor if the wrong tab is selected. I was surprised how sluggish Dreamweaver was when I first used it. So I now minimise the Assets window and never use it - btw I'm on a G5 2GHz Dual with 3GB RAM & 360GB HD so speed, memory & hard drive space shouldn't be an issue!

Yeah, they didn't really leave it as much of a question, did they? I think this sentence sums it up, "The framework can be used with Dreamweaver or any other Web authoring tool, according to Adobe." Umm, like your own GoLive?

Well, I really hope they take the best features of both and create something better than either, with a more CS-like interface. If they mix Dreamweaver with Golive, and then Freehand with Illustrator, they can introduce two new apps in CS3: Adobe Dreamliver, and Adobe Frustrator!

Correct. Adobe bought the company that made this app - it was much better than PageMill. Unfortunately, they had a light version of GoLive that was priced competitively with PageMill. Adobe discontinued that version.

I have been developing my own effective, but somewhat crude, AJAX implementation.

I haven't adopted prototype or any other framework because I have no idea of knowing which framework will come out on top or which one will receive the most energy for development.

Adobe's demo of their new framework is intriguing. While I often hand code my own pages, I would love to speed up development by handing over the AJAX portion to a well thought out framework.

I say Adobe is moving in the right direction. Let's hope the framework and related documentation is solid.

---

http://www.bluerivers.org

In reply to:<hr />
Well, I really hope they take the best features of both and create something better than either, with a more CS-like interface. If they mix Dreamweaver with Golive, and then Freehand with Illustrator, they can introduce two new apps in CS3: Adobe Dreamliver, and Adobe Frustrator!

<hr />

Brilliant!