Comparison: Adobe Dreamweaver VS. Aptana
VS
If you fall into the category of the standard web designer, which likely explains why you’re here, you’ve used some of today’s high-powered web IDEs: powerful tools for creating powerful websites and web applications, complete with built-in browser testing, some sort of crummy design view, version control, the works. It’s especially likely that you’ve used Macromedia (now known as Adobe) Dreamweaver.
Within the past two years, the eclipse project, a Java-based open source IDE, has been forked into two separate projects: Aptana, which is targeted primarily at AJAX-centric developers, and RadRails, which is a Ruby-on-Rails-targeted IDE, complete with version control, debugging, local testing and debugging, and remote deployment capabilities. The Aptana project has been growing fast with additions of full PHP and iPhone support and has recently incorporated the entire RadRails project, providing developers with the simultaneous advantages of a supported Ruby on Rails IDE with native AJAX development support. The Aptana Project has also found user-funded opportunities thanks to the development of Aptana Studio Pro, the beefier brother to Aptana, complete with JSON support, SVN & SSL control, Internet Explorer JavaScript debugging, and enhanced support features.
I’ve compiled some research done on both IDEs, and present to you a feature comparison chart that goes over the advantages and disadvantages of each choice. Since Aptana is free, I highly recommend you download it and try it out on something less-than pressing, such as a new theme for your new WordPress install. While I’m hesitant to suggest that you try to convert your workplace to loyal Aptana followers, I think it’s a great way to get started learning Ruby on Rails or AJAX.
|
Aptana
|
Dreamweaver CS3
|
|
|---|---|---|
|
XHTML
|
YES
|
YES
|
|
Browser Compatibility Testing
|
IE7, Firefox
|
YES – IE, Firefox, Opera, SafariIntegration with Adobe CSS Advisor |
|
CSS
|
YES
|
YES
|
|
XML
|
YES
|
YES
|
|
JavaScript
|
YES
|
YES
|
|
AJAX
|
YES – Spry
|
YES – All major libraries
|
|
PHP
|
YES
|
YES
|
|
ColdFusion
|
NO
|
YES
|
|
ASP
|
NO
|
YES
|
|
ASP.NET
|
NO
|
YES
|
|
Ruby on Rails
|
YES. Use the RadRails plugin
|
YES. Spotty support on plugin
|
|
JSP
|
Not currently. Future possibility
|
YES
|
|
Version Control
|
SVN
|
File Check-in/Check-out. A bit buggyThird-party SVN plugin available for $53 Support for MS SharePoint Servers |
|
JSON Support
|
Studio Pro Only
|
YES
|
|
Secure FTP
|
Studio Pro Only
|
YES
|
|
JavaScript Debugging
|
Community: FirefoxStudio Pro: Firefox, IE |
YES. See Browser Compatibility Checking
|
|
Support Plan
|
Typical open-source support scheme for community version. Beefier and more comprehensive plan with Studio Pro
|
Decent corporate support plan. Call center full of monkeys, web-knowledge-base
|
|
Price
|
Community: Free
Studio Pro: $99/$199 Initially. $79 Annually Thereafter |
$399 initially. $199 for the upgrade
|
|
PROs
|
Great Open Source IDE with boundless potential for growth. It’s the best Ajax/RoR solution you will find anywhere. |
Dreamweaver is clearly a mature, proven, and enterprise-ready product that has been in use by developers and designers alike for years. Dreamweaver is the best choice for mission-critical work.
|
|
CONs
|
It’s JAVA-based, and JAVA is notoriously bad at managing system resources. Expect to upgrade your memory. Support is what you pay for. Bug fixes and feature adds come only as fast as the development team can afford to make them. |
Support for Ruby on Rails is sketchy, and the price is prohibitive to entry-level developers and designers.
|
ShareThis