Gecko Appearing in Compuserve Betas

Thursday October 18th, 2001

AOL today confirmed that Gecko has been embedding into beta versions of CompuServe 7, according to this article. AOL 7 was released yesterday, still with IE as its embedded browser, but because CompuServe's software seems to be much like the AOL software, it's likely that we could also see AOL sporting Gecko as it's browser in the future.

#64 Re: What's depressing...

by strauss

Monday October 22nd, 2001 9:37 AM

You are replying to this message

>> What's depressing is that this person and many others are probably professional web designers, these people should know how to write proper standards compliant HTML and code to web standards. <<

You can't do serious client-side interactivity within the web standards. The W3C standards are created by academics who have no grasp of the needs of actual developers. That's why Mozilla has had to adopt non-standard IE-isms like "innerHTML." IMHO they shouldn't stop there.

>> Real coders have to obey the syntax laws of their language, <<

Are you a real coder? If so, you know that almost all development environments have their own extensions and that most coders working on real-world projects take advantage of them.

>> writers have to use correct english, <<

Not even slightly true. What century is this, anyway?

>> but HTML weenies often write anything and class it as valid if it works in IE rather than testing it properly. <<

"Testing it properly" apparently means making sure it works on Mozilla, even though Mozilla is still not ready for prime time. I had a pretty typical experience of this a couple of weeks ago, when the DHTML guy at the next desk was complaining that he had to make his project work on Netscape 6. He was running into bugs at every twist and turn, and practically cursing up a storm at how long it had taken the project to deliver practically nothing. We web developers are very daunted by the prospect of having to weave in and out of thousands of remaining bugs and spend our days and long nights coming up with elaborate workarounds for them. We already had much more of that than we could stand with Netscape 4.x, which is why we dumped the platform for the most part.

This is not meant to be inflammatory, just to inform people what the actual situation is for web developers. The bug-riddled nature of Mozilla hurts us more than anyone, and it is not a dream, not a hoax, and not an imaginary tale.