On Tue, 8 Jan 2002 00:40:08 -0600 Robert Wittig <[EMAIL PROTECTED]> wrote:
> Sam, >> Why should the developers of any good web browser stoop to > condescend >> to comply with the psuedo-standards of some rogue software producer >> and web page developer such as Micro$oft? > They shouldn't. Opera is stricter than MSIE browser. I can only assume > that MS page authoring tools are designed to work with their browser, > since I author my pages with a text editor. >> Whenever I try to compile some C language source code with my Turbo > C >> compiler, my compiler will flag bad code as an error. That is > because >> Turbo C is a good compiler and it conforms to accepted standards. >> Similarly, when you are trying to render an M$ web page with a good >> browser, your browser should flag the bad HTML and and poorly > written >> scripts encountered on M$ web pages as errors. > Heh. I think that your comparison here is a little unreasonable, > especially at the level of HTML. A little flexibility in reading > errored pages is not all bad. Compilers have to be a heck of a lot > more exacting than HTML authoring tools, since they are building > executables that will have direct access to memory, whereas bad HTML > cannot crash your computer. Bad HTML can lock up your computer and you will have to reboot. I could refer you to several websites that will consistently cause Arachne to crash. I know that there used to be some websites out there that will always cause MSIE or NetScape to crash. About three years ago I used to know about a web page that had links saying something like "Click here to crash MSIE" and "Click here to crash Netscape" and "Click here to crash Arachne". According to what was being said about the site on a mailing list I subscribed to at the time, all of the links were reported to work exactly as advertised! Bad HTML usually contains inserted so-called Java Scripts or Java Applets which run like executables to cause your computer to crash. Of course not all so-called Java Scripts and Applets are bad. > Also, choosing C as an example was > probably a worse choice than say, Java, since the C compiler will let > you over-write your memory allocations with impunity, and do all sorts > of other disasterous stuff, as I have learned myself.<g> I haven't yet encountered the problem of overwriting my memory allocations. I haven't yet seen this happen probably because I have considerably less experience with C than you do. I do have enough experience to have learned that C can do all kinds of other disastrous stuff to me when I really screw up <g>. The compiler isn't the culprit. If you accidently shoot yourself in the foot you shouldn't blame the gun, even if the gun is found to be defective in design and manufacture. > It is pretty funny, how many messed up scripts there are on the Web, > though. My debugger detects them and goes off while I am surfing, > asking me if I want to debug. I don't think it's funny at all. I think it is pathetic. Sam Heywood -- This mail was written by user of The Arachne Browser - http://arachne.cz/ To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with unsubscribe SURVPC in the body of the message. Also, trim this footer from any quoted replies. More info can be found at; http://www.softcon.com/archives/SURVPC.html
