|
On November 7, 1996, the following typewritten confession was found on a steel chair bolted to the floor of Room 101 in the basement of Bay City Police Headquarters. There was no sign of a struggle. Just a few cigarette burns and blood stains. And one very frightened fly on the wall.
Uh-ohAccording to the November 4, 1996, issue of Web Week, Netscape Communications Corporation is abandoning industry-supported Cascading Style Sheets (CSS) in favor of its own JavaScript Style Sheets (JSS). To prove it's serious, Netscape has already dotted its "i"s and crossed its "t"s with the World Wide Web Consortium (W3C) by submitting JSS as an industry standard. Assuming this latest move by Netscape is not a clever ruse to force shamelessly chameleon Microsoft Corporation to squander resources on a Strangelovean "Doomsday Machine" of its own, JSS is bad news for web developers everywhere.
Style sheets are goodTo understand what's wrong with JavaScript Style Sheets, you have to understand what's good about style sheets. "Style sheets have been on the W3C's agenda since day one," says the WWW Consortium. Why? Because they enable authors to control the look and feel of text from a central location. Desktop publishers use templates to control margins, paragraph styles, character styles, and the like. Web developers, so the theory goes, will soon use style sheets to do the same thing. Style sheets should have been a no-brainer for the WWW Consortium. The HyperText Markup Language (HTML) is based directly on the 10-year-old Standard Generalized Markup Language (SGML), which uses style sheets extensively. In SGML, you define styles for literally everything in a book in one style sheet file. This style sheet file is then referenced by every other component file of that book. Then, if you decide you want to switch all headings from hot pink to geometric blue, you make the change in the style sheet and -- wallah! -- all headings in the book change automatically. In SGML, style sheets are the holy of holies, the mother of all labor saving tools, goodness itself.
Cascading Style Sheets are badSo what's wrong with Cascading Style Sheets? The word "cascading," that's what. CSS allows three levels of style sheets:
But, wait a minute. What happens if you use local, global, and linked style sheets in CSS? Who wins? Drum roll, please: evil local style sheets override good linked style sheets. That's right: the lowest common denominator wins.
Evil twins are uglySo maybe JavaScript Style Sheets are better? Maybe. Maybe not. But JSS begs the question: why do in JavaScript what you can do in HTML? CSS may be a bad implementation of a good idea, but a second standard is, by definition, evil. And evil always leads to trouble:
Bottom lineIt appears Netscape is on the verge of making a fatal strategic error. If it really is serious about JSS, Netscape will lose market share to an enemy it will start to resemble. Given the corporate install base of Windows, using "human shields" as pawns in open warfare between Microsoft and Netscape will simply force Corporate America to hold its nose and choose Microsoft yet again, turning Netscape into the next Apple. Netscape, three words: Levis, Marlboros, open borders. Do the right thing or start looking for property in Redmond. Your choice.
See also |





