|
|
Posted by David on 10/01/06 19:34
Jim Scott wrote:
> When made my first website I used MS Publisher. Although I learned later that the
> resulting HTML was mucky and bloated, it taught me the fundementals.
> My next pc came with MS Frontpage and although it produced quite nice webpages, my
> provider at that time did not support FP extensions.
> My site was criticised by the purists on alt.html, so I abandoned FP for a time and
> produced my site using various other editors, each time validating every page with W3C.
> Although it uses frames a lot and tables extensively I have not changed it for a good
> while.
> My ISP these days is quite happy with FP extensions and provides me with heaps of
> webspace so I can see no good reason why I should not use FP with all its bells and
> whistles.
> Can you?
FRONTPAGE REALLY F**KS UP YOUR HTML! FrontPage is notorious for this.
FrontPage uses a tags that can only be used by Internet Explorer, which
messes up the web site for viewers who have the brains to use other
browsers, such as Mozilla, Safari, Firefox, Opera. FP also likes to use
stupid document formatting that makes code buggy and hard to read.
FrontPage Extensions
FrontPage uses little "programs" called "FrontPage Extensions" with the
idea of not having to use a server side language for functions. This
seems like a good idea because you don't have to use a server side
language such as ASP, PHP, or SSI. FrontPage Extensions have a habit of
screwing up and being terribly inefficient.
Because the frontpage extensions cause security issues.
The web components are non-web-standard, quirky to debug, and even
harder to convert over to a different editor such as Dreamweaver.
FrontPage was purposely designed to only work hassle-free ONLY with
Microsoft Web Servers. A whole series of artificial stumbling blocks
have been written into the program to make it less compatable with
non-Microsoft products.
Do a search on the web, there are many reasons NOT to use FrontPage.
Navigation:
[Reply to this message]
|