Initial thoughts on Google doctype
Today Google launched Google doctype, their new open reference for the web. I’m just starting to look it over, and while I’ll reserve my final judgement until I have the opportunity to spend more time poking at it, I thought I’d share my initial thoughts.
Google is right that there needs to be a solid, reliable, and complete reference to the web. The Mozilla Developer Center is being built as a complete reference to the open web. Notice the difference there. It appears that Google’s aim is to build a complete reference to all web browsers, even the ones that diverge from open standards.
That’s a critical difference. Mozilla aims to improve the web by encouraging the use of genuine open standards. The more compatible browsers are with a universal standard, the better the web experience becomes for all users, regardless of which browser they choose. Our goal isn’t to get everyone to use Firefox — it’s to get everyone using the web to the utmost of its potential.
John Resig has a great analysis of how the tests were done to determine browser compatibility, so I won’t go there.
Reading through the documentation, such as it is at this point, is an interesting experience. It’s clear that this initial release is something of a rush job, with automatically exported material posted and hoping that people will come along and tweak it up. For example, take a look at the documentation of the document.getElementsByClassName method in the DOM. It’s pretty much a stub right now. The most interesting part there is the test they did to see which browsers offer the method (not to mention the links to John Resig’s blog posts on the subject).
Contrast this to MDC’s documentation for the same property, which includes a description of what the method does, what its result means, as well as a number of examples and a link to the WHATWG specification.
This is a pretty typical example.
Google doctype is an interesting experiment, and I’ll be curious to see what happens with it, despite my confusion over its purpose.
free viagra
buy viagra online
generic viagra
how does viagra work
cheap viagra
buy viagra
buy viagra online inurl
viagra 6 free samples
viagra online
viagra for women
viagra side effects
female viagra
natural viagra
online viagra
cheapest viagra prices
herbal viagra
alternative to viagra
buy generic viagra
purchase viagra online
free viagra without prescription
viagra attorneys
free viagra samples before buying
buy generic viagra cheap
viagra uk
generic viagra online
try viagra for free
generic viagra from india
fda approves viagra
free viagra sample
what is better viagra or levitra
discount generic viagra online
viagra cialis levitra
viagra dosage
viagra cheap
viagra on line
best price for viagra
free sample pack of viagra
viagra generic
viagra without prescription
discount viagra
gay viagra
mail order viagra
viagra inurl
generic viagra online paypal
generic viagra overnight
generic viagra online pharmacy
generic viagra uk
buy cheap viagra online uk
suppliers of viagra
how long does viagra last
viagra sex
generic viagra soft tabs
generic viagra 100mg
buy viagra onli
generic viagra online without prescription
viagra energy drink
cheapest uk supplier viagra
viagra cialis
generic viagra safe
viagra professional
viagra sales
viagra free trial pack
viagra lawyers
over the counter viagra
best price for generic viagra
viagra jokes
buying viagra
viagra samples
viagra sample
cialis
generic cialis
cheapest cialis
buy cialis online
buying generic cialis
cialis for order
what are the side effects of cialis
buy generic cialis
what is the generic name for cialis
cheap cialis
cialis online
buy cialis
cialis side effects
how long does cialis last
cialis forum
cialis lawyer ohio
cialis attorneys
cialis attorney columbus
cialis injury lawyer ohio
cialis injury attorney ohio
cialis injury lawyer columbus
prices cialis
cialis lawyers
viagra cialis levitra
cialis lawyer columbus
online generic cialis
daily cialis
cialis injury attorney columbus
cialis attorney ohio
cialis cost
cialis professional
cialis super active
how does cialis work
what does cialis look like
cialis drug
viagra cialis
cialis to buy new zealand
cialis without prescription
free cialis
cialis soft tabs
discount cialis
cialis generic
generic cialis from india
cheap cialis sale online
cialis daily
cialis reviews
cialis generico
how can i take cialis
cheap cialis si
cialis vs viagra
levitra
generic levitra
levitra attorneys
what is better viagra or levitra
viagra cialis levitra
levitra side effects
buy levitra
levitra online
levitra dangers
how does levitra work
levitra lawyers
what is the difference between levitra and viagra
levitra versus viagra
which works better viagra or levitra
buy levitra and overnight shipping
levitra vs viagra
canidan pharmacies levitra
how long does levitra last
viagra cialis levitra
levitra acheter
comprare levitra
levitra ohne rezept
levitra 20mg
levitra senza ricetta
cheapest generic levitra
levitra compra
cheap levitra
levitra overnight
levitra generika
levitra kaufen


May 15th, 2008 at 6:15 PM
They could have left an Open Search Description XML, as we have in the (excellent) MDC.
It would have been more useful
(by the way, it lacks too in PHP documentation)
May 17th, 2008 at 2:05 AM
Unfortunately, it makes no sense for MDC as it is now to be a documentation repository for the web at large. MDC needs to serve a very different audience as well – extension developers and others who work on Mozilla-based code. This means it must document the Mozilla specific things (e.g. XBL, XPIDL), which is totally pointless and distracting for people looking for documentation on cross-browser things.
If MDC is intended to document the rest of the world, it needs to have a good filtering capability, such that the user can choose which set of documentation to look at. Ideally, with different URLs (generated from the same set of sources, or something). This needs to exist for different Gecko versions as well (1.8, 1.9, .next at the minimum). MSDN does this very well, with every page noting the minimum required version – though I believe there’s an opportunity to improve by reversing to browsing documentation for the intended version.
P.S. Not sure if the MoFo installation is better (still can’t see it!), but dekiwiki seems to be worse than MSDN in being totally unusable with scripting disabled. All the menus are DHTML with no fallback.