3 ms·

Why exactly is Dreamweaver such a bad tool to use, especially with it's code editor that (personally of course) seems to be hands and feet better than the compe

Why exactly is Dreamweaver such a bad tool to use, especially with it's code editor that (personally of course) seems to be hands and feet better than the competition. I can see why designers would dislike the visual editor side, but who really uses it for serious work anyway, PHP syntax highlighting is far better in Dreamweaver, as is HTML. its really a personal choice that the developer has to make, and if it works well for them, I don't think its right to say, "you use Dreamweaver, hence i am better". Same goes for Visual Studio/Aptana/whatever else, if the developer prefers t and can produce his work with it, why deride him for the tools he chooses to use?

dhoulb 13y ago
It's definitely possible for people to have dev environments that are objectively insane. Dreamweaver isn't too crazy though — some people use Vim. I've not really used Dreamweaver in years, but I assume most people disable the visual editor? Unless it's possible to preview using Chrome rendering and get some sort of LiveReload setup going? Does it even have a built in server, or does it just show static sites? The concept of Dreamweaver isn't a bad one, it's just their technology and standards support that's all mangled. Someone could probably create an awesome Dreamweaver-like integrated IDE using a mashup of Blink, nginx, Git, FTP, and Sublime Text. It'd make your local environment loads easier to set up. My combination of tools works great right now, but feels a bit cobbled together. Step one in web dev is figuring out a solid setup — took me years to get to a point where I'm really efficient. It's probably a barrier to entry. A single integrated thing, that followed standards, would definitely make it easier for new people to learn.