3 ms·

The details of both the semantics and syntax in question have been widely discussed and understood. It's pure hyperbole to appeal to "reverse engineer Blink's i

The details of both the semantics and syntax in question have been widely discussed and understood. It's pure hyperbole to appeal to "reverse engineer Blink's implementation" (which, as you might be aware, is Open Source). Here's a refresher for those who missed it: https://docs.google.com/a/chromium.org/document/d/1cxW4MtsDbCUTdnr_7lxwrlywmpKj04aD5TRVKjd446o/edit?pli=1 https://docs.google.com/a/chromium.org/document/d/1cxW4MtsDb...

ddebernardy 13y ago
The fact that web developers will then need to worry about differing implementations across browsers and -- pray not -- across blink versions, on the other hand, is not hyperbole. If it's ready to ship with nobody else agreeing on how it should work, please do everyone a favor and ship it with a prefix. If only as a courtesy to fellow developers who will need to deal with this mess. Nevermind that you don't want a prefix. Use one. Better prefix hell than different implementations using the same syntax.
- deleted 13y ago
  [deleted]
pcwalton 13y ago
> (which, as you might be aware, is Open Source) Being open source has never been an excuse to break the standards process. It's disheartening to see open source being used to justify this behavior again (first with PNaCl, now this).
- slightlyoff 13y ago
  That's moving the goalposts. The full context of your statement was: > it'll be other vendors' pain as they have to reverse engineer Blink's implementation Which was the salient point I was replying to. Quoting out of context to imply I made statements I did not is...disheartening.
Ygg2 13y ago
Problem is - even if something is open source, doesn't mean it will be easy to pull and implement in your code base... Maybe cat/hat Shadow DOM depends on some C lib that causes incompatibility with a lib you use, which means you'll have integration problems.

ddebernardy 13y ago

The fact that web developers will then need to worry about differing implementations across browsers and -- pray not -- across blink versions, on the other hand, is not hyperbole. If it's ready to ship with nobody else agreeing on how it should work, please do everyone a favor and ship it with a prefix. If only as a courtesy to fellow developers who will need to deal with this mess. Nevermind that you don't want a prefix. Use one. Better prefix hell than different implementations using the same syntax.

deleted 13y ago
[deleted]

pcwalton 13y ago

> (which, as you might be aware, is Open Source) Being open source has never been an excuse to break the standards process. It's disheartening to see open source being used to justify this behavior again (first with PNaCl, now this).

slightlyoff 13y ago
That's moving the goalposts. The full context of your statement was: > it'll be other vendors' pain as they have to reverse engineer Blink's implementation Which was the salient point I was replying to. Quoting out of context to imply I made statements I did not is...disheartening.

Ygg2 13y ago

Problem is - even if something is open source, doesn't mean it will be easy to pull and implement in your code base... Maybe cat/hat Shadow DOM depends on some C lib that causes incompatibility with a lib you use, which means you'll have integration problems.