Postscript on Why I'm Not Using Dreamweaver

[jducoeur]

Do you remember, a month or so ago, when I was grousing about how horrifically bad the website for the Adobe MAX conference was? I had let that slide once the conference started, because the show itself was really quite well-organized and a lot of fun. So I figured they were just having an off day.

Well, today I got a followup email from Adobe, asking me to take a brief survey on what I thought of the conference. Great, think I: a chance to point out the flaws in the website. Yeah, nice theory. The link to the survey page takes me to a blank screen, and then hangs. It's not temporary, either -- I've tried twice, several hours apart.

These folks really need to learn that this isn't exactly a good advertisement for their tools. I mean, my principal reaction is that I want to learn what Adobe systems they used to build this site, and then *never* use those systems. Rarely have I seen a nominally professional website that was so hosed...

Comments

[siderea]

Well, if anyone is going to be bashing CF, I want in on the action. But I don't think one gets to blame CF for this -- it's not like CF automagically does anything, much less poorly. It's just a programming language. A very, very slow, interpreted language with retarded regular expressions and a completely non-standard definition of "variable scope".

[tashabear.livejournal.com]

Good point.

It's just that Dreamweaver *does* do things automagically, and actually does them pretty well. Fireworks, too; I used both a lot when I was coding webpages at TMP Worldwide.