|
|
135 of 143 people found the following review helpful:
3.0 out of 5 stars
Sooner or later you'll need Dreamweaver, August 11, 2001
I bought FrontPage 98 a few years ago probably for the same reason you're at this page now--I wanted to start making my own web pages, but I was intimidated by all the stuff I would have to learn.FrontPage is a great tool to get you started, but, if you talk to enough people, and you spend as time on the phone with tech support as I find I have to do because of problems related to FrontPage, you'll hear the same thing over and over again: FrontPage writes messy code, Dreamweaver does not. Why? Well the answer is both simple and familiar: Microsoft, once again, has chosen to create its own set of standards rather than follow those 95% of the rest of the world uses. Consequently, all the "extra stuff" required behind the scenes to make FrontPage work is essentially incompatible with many other things. In fact, I upgraded from FP 2000 because the latter had a major bug, a known issue, as they call it--it cannot upload large sites; it almost always gives some sort of error when doing so. Worse, you MUST use FP to upload; you cannot simply FTP your files as you can with other HTML generators. So, I upgraded to FP 2002, and the upload problem was fixed, but more problems were created. My current web host and at least two other ones (two of which are the largest in the industry) have told me the same thing--they are not supporting FP 2002 yet because it is too buggy. FP's whole approach of editing your site "live" presents a couple of other problems as well. You will notice that when you work in FP, you are actually working on "live" pages; i.e., you are editing the very page that is on your web site. No big deal, you're thinking, right? Wrong. As buggy as it is, FP often messes up its functions or crashes, and you're stuck with a crazy page live on your web site. Dreamweaver, on the other hand, essentially duplicates your entire web site on your hard drive, and all editing takes place on your hard drive first. If something goes awry, you don't need to upload the changed pages from your hard drive to your web site--if worse comes to worse, you can choose to overwrite your local pages with the ones that are live on your site. After working for a long time in both editors, I have come to think of having TWO web sites when working with Dreamweaver; I can tinker with and tweak the one on my hard drive at will and, when it's just how I want it, I can upload it. In FP, I have no such option. I don't mean to beat a dead horse, but imagine you had an electronic billboard that was visible to the world--wouldn't you want to upload the new one all at once instead of little by little? Part of the reason I'm writing this review right now is that I now, as I write, have one of those so-called "known issues" plaguing my web site. FP 2002 has a bug that causes certain parts of the page to duplicate itself. So, now, as I type, visitors are seeing my page in double!! I am SO tired of the whole FP deal. I am now sure that I will convert my entire site to Dreamweaver so that I can be done with FP forever!! Finally, FP uploads in a special way that is necessary for FP to function properly. From what I understand, FP uploads via the web while most editors do so via FTP. This may seem a small matter, but think of it this way--have you learned, the way I have, that you must save frequently? Probably. Do you hit CTRL+S (to save) between every other breath in most other programs? If so, you will quickly grow tired of FP. Each save takes from five to twenty minutes, no joke, and I have DSL. Dreamweaver, on the other hand, can upload a page in just a few seconds, always. I now realize that I should have just learned Dreamweaver in the beginning, and have a purely Dreamweaver site. Trust me on this one.
|