Grow your CSS skills. Land your dream job.

What do you use to design with?

  • # December 19, 2012 at 5:02 pm

    So today I was posting about a CSS related subject and mentioned that I used Dreamweaver (on Windows). I’ve used it for many years. Most projects I work on (the vast majority) are 20 page or less sites with PHP and HTML. Sometimes .NET. When I’m doing .NET stuff I use Visual Studio but for my day to day I use Dreamweaver. For the style of sites I’m doing right now it seems to fit the bill just fine.

    When I mentioned it I got at least one person shunning me. OK, not really shunning me but I’ve seen other remarks here and there about not using Dreamweaver. So I’m wondering…

    Why NOT use Dreamweaver (is there a specific reason beyond “It sucks.” or “I hate it.”?)

    What do you you use to design in?

    # December 19, 2012 at 5:14 pm

    I personally don’t think there is anything bad about Dreamweaver. Only thing I think its “hated” for, is its generation of WYSIWYG output with kinda messy HTML and inline css which is kinda bad practice for what our goal is.

    If you use Dreamweaver as just a code editor with project functionality I think its a decent choice. (Especially for the limited amount of good code editors for windows)

    # December 19, 2012 at 5:24 pm

    It’s also a bad choice especially if you’re starting out or still somewhat new to coding (not that I’m implying you are) and writing your own css since it has that feature where you can just click an “Edit Rule” of “CSS Panel” you can click for a pop up where you literally don’t have to write any code and just fill in the boxes so it teaches bad practice in that way.

    I had a co-worker as me about a problem so I asked to see his CSS and he pulled up a Dreamweaver CSS Panel and I was like….really?? lol

    I agree with @SSchnitzler that if you’re just using it as a code editor it’s not a big deal.

    # December 19, 2012 at 5:36 pm

    As others as mentioned, what makes Dreamweaver suck is when people use it for anything but a straight code editor. But then you realize that for JUST a code editor it’s unbelievably bloated and slow. It’s kind of like the new FrontPage.

    So then you begin thinking as a code editor – what do you want? Speed and flexibility! A lot of folks have moved to Sublime Text for that – extremely light weight and its the most customizable thing ever. A lot of people use Coda on Mac because it’s just a really great editor (I use it still for most of my projects). On windows I used “E” which is their version of TextMate, but that is also a great editor.

    # December 19, 2012 at 5:55 pm

    Yep, agree with @JoshWhite. I use Sublime Text for editing code but that’s not that often.

    # December 19, 2012 at 6:27 pm

    I started in DW, but have been using Notepad++ for a while now, and enjoy it quite a bit..so much so that I haven’t really been interested in seeing what else is out there until very recently.

    I just think DW is too slow and clunky, IMHO

    # December 20, 2012 at 12:26 am

    I think @ChrisP hit the nail on the head; Dreamweaver is ‘Clunky’. It is an IDE (IntegratedDevelopment Environment) rather than a code editor. I’m also a massive fan of Sublime Text, as are many others.

    # December 20, 2012 at 8:31 am

    Thanks all. I’ve been using DW in some form for at least 8 or so years so I guess if you’ve only used on thing you don’t see it as “bloated, slow and clunky.” :-) I do use the built in CSS builder about 50% of the time because its quick but everything I do automated in DW I can also do by hand when I need to.

    I also like that DW Integrates with Photoshop…but now I’m interested in expanding my world. :-)

    Thanks for all the input and the recommendation for Sublime…I will check it out.

    # December 20, 2012 at 12:04 pm

    @IntegrityWebDev Check out Komodo, theres a little write up about it here http://j.mp/XPGLFs

    Admittedly, its for the lazy coder, but never the less, its feature packed, easy to use and free.

Viewing 9 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic.

*May or may not contain any actual "CSS" or "Tricks".