(I cannot comment on the merits of either product for multi-user environments where different authors may be changing different parts of a site a the same time, simply because I haven’t had the opportunity to try it.) GoLive’s abilities to synchronize local and remote files, as well as basic functions like uploading modified files, work much more reliably than Dreamweaver’s (even accounting for the crashes).Īnd in terms of usability, Dreamweaver still suffers from what has become a real pet peeve of mine: an apparent inability simply to upload site files stripped of template tags or comments. Having said that, in my view, GoLive remains the vastly superior product when it comes to handling site updates performed by a single author. It was far quicker simply to SSH to the web server separately and delete or rename files from the UNIX command line. For example, my test copy of GoLive CS2 seemed pathologically prone to crashing when using the function to upload modified files to the web server, and using GoLive to accomplish simple tasks at the server end - such as deleting a couple of files - turned out to be so slow as to be nearly useless. Unfortunately, both also suffer from annoying site management bugs and shortcomings in usability.
Current Users of Other Site Development Environmentsīoth products offer significant improvements in terms of site management, with GoLive CS2 adding SFTP as well as FTP tunneled through SSH and over SSL, and Dreamweaver adding (at long last!) uploading of files in the background, so that updating the site no longer ties up the whole program until the update is finished.Current Users of Earlier Versions of GoLive.Current Users of Earlier Versions of Dreamweaver.Serious Developers of Large Scale Sites.
The Role of Visual Editors, and the Current Leaders in the Field.