Slashdot Mirror
The Mozilla 1.0 Definition
The Evil Beaver writes: "Here we go. Mozillazine is reporting that Brenden Eich, mozilla.org's Technical Bigshot, has released the criteria to what is to be the 1.0 milestone. The 'manifesto' also explains why 1.0 is so important to reach, and why it isn't just another milestone, either. The Mozillazine article is here and the definition document here.
Here's the REAL issue: "Standards are an evolving thing." They *shouldn't* be, and true standards do not evolve much, if at all.
... HTML 1.0 and such base stuff, but web designers are trying to make the WWW do things it was never designed to do, and *that* is where this horrible mess of Javascript kiddies, broken CSS, and browser specific "features" came from. I don't know about you, but I'd rather not see all that flashy crap on a web site. Web sites need to contain *content*, not eye candy. :P
Imagine if a kilogram was 2.2lb one day, then 4.3lb the next. Not much of a "standard", is it?
The major browsers were all "compliant" with
Since Mozilla is beginning to look rather slick these days I have a quick question to someone enlightened. Is the new AOL (7.0?) interface based on Gecko or does it still use the IE control? Anybody in the know?
Your pizza just the way you ought to have it.
Listen I have been using Mozilla on and off since it began to be bundled with various distros.
.94+ version I am using right now and use it for most of my work. However, I do wish the thing was quicker in rendering pages. Any thoughts on this? Is it just my perception of the program?
When it first came out I swear the pages it could render came up as fast as anything I saw from even Opera but the program loaded really slowly. In other words, when it finally came up it was really fast unless it crashed.
Now, Mozilla can handle most any page Netscrape can handle and loads faster but the page rendering seems to be slower on regular html pages not nearly as fast as when it came out initially. I was impressed by the
ACK