7 ms·
Here's the reply: http://lists.w3.org/Archives/Public/www-style/2014Feb/0138.html http://lists.w3.org/Archives/Public/www-style/2014Feb/0138.h... the money qu
by bryanlarsen 13y ago
Here's the reply: http://lists.w3.org/Archives/Public/www-style/2014Feb/0138.html http://lists.w3.org/Archives/Public/www-style/2014Feb/0138.h...
the money quote: "We feel the
standard is sufficiently advanced, the remaining issues sufficiently
small, and the benefit to authors sufficiently great to justify
shipping sooner rather than later."
the Shadow DOM is pretty awesome, so I'll agree with the "benefit to authors sufficiently great" part. No comment on the rest.
- mcphage 13y agoThis part of his reply annoyed me: "Attributing an ultimatum to my words is blatantly violating the Principle of Charity, especially since I've very explicitly clarified that I'm talking about the latter." Given his words were "Whatever API gets shipped will be frozen almost immediately. If you want to suggest name changes, as we brainstormed a bit at the f2f, do so RIGHT NOW or forever hold your peace." ... I'm a proponent of the principle of charity, but I don't know how to read that as anything other than an ultimatum.
- chc 13y agoThis is the other way of reading it: He's essentially saying, "Once this is shipped, the cat will be out of the bag and we will not be able to put it back in, so if you need the cat for something, you should do it now." That's not what is traditionally meant by "ultimatum," because an ultimatum implies that you want someone to do something and will do something else to injure them if they fail to meet your demands.
- deleted 13y ago[deleted]
- agwa 13y agoYour cat analogy still sounds like an ultimatum to me: threatening someone with not being able to work with the cat unless they acquiesce to their demand to work with the cat on a very short timeframe. Here's how the email fits your definition of an ultimatum: Demand: that the working group suggest changes to the proposal "RIGHT NOW." Injury if they don't comply: Google will ship the API anyways and freeze it so the working group can't later change it without breaking compatibility with a major web browser.
- deleted 13y ago[deleted]
- chc 13y agoNo, that is not the form of an ultimatum. In an ultimatum, the threat will only come to pass if the target does not comply with the demand — it's an either-or situation, with the threat used as leverage to get what you really want. Google isn't saying, "Either suggest some stuff or we will ship the Shadow DOM API. We don't want that to happen, right?" The message was of the form of an advisement rather than an ultimatum. It is similar to "Hey, everybody, I'm putting these cupcakes out. Get them fast because when they're gone, they're gone." I don't think anybody would hear that and say, "Hey, stop throwing around ultimatums." The "threat" is not a threat — it's a heads-up about something that is going to happen, so that people have a chance to respond adequately. You can still say that Google was not considerate enough in what they did, but there is definitely a reading of the message that is not an ultimatum.
- joyeuse6701 13y agoIt reads as an advisement, but it really is an ultimatum. the analogy you provide about advisements is that something is going into effect which the adviser has no power over. However, Google does have the choice whether or not this goes through. It's not the weather, it's not a god, there are people that make decisions and they can be modified. That is where the ultimatum is, just disguised as an advisement.
- chc 13y agoYou criticized the analogy and ignored the entire rest of the text which made my point entirely clear. Why do people do this? OK, fine, here's another analogy: "I'm going to be leaving in 10 minutes, so if you have any questions, you'd better ask them now." The thing being "threatened" here is entirely in the speaker's control — he could opt not to leave. So is that an ultimatum? I don't think it would generally be viewed that way. Why? Because there is no threat being used as leverage to get something — the speaker (i.e. Google) isn't really making demands here, but rather stating what it's going to do. The thing being "threatened" will happen regardless; this is just an advisement that it will happen so that you can respond accordingly. Put another way, the "threat" component of an ultimatum can't be unconditional. It is conditioned on noncompliance. AFAIK that's the defining characteristic of an ultimatum. It is possible to read this as being a conditioned threat, but it seems entirely reasonable to me to read it more in the spirit of "I'm going to do something, so here's your chance to get ready." It's entirely possible that Google doesn't care if it receives any further input (which is theoretically the "demand" in this ultimatum).
- munificent 13y agoBy "be frozen" he didn't mean "Google will declare it to be unchangeable", he meant "users relying on it will prevent any of us from being able to change it." If it's an ultimatum, it's the users of the feature that are holding the gun, not Google. Tab clarified what he meant in a response: By the way, I deeply apologize for the confusion revolving around my use of the term "freeze". That term is used internally (within the Blink team) to indicate something that's no longer changeable (or at least is probably too difficult to change) *due to compat pain*. I'm aware that there are other uses of the term, like "feature freeze", that imply a much more deliberate *decision* by somebody to stop making changes. I forgot about those additional meanings and was intending just the more popular internal meaning. While I've certainly used that meaning in public, and have heard other people use it or other relatively close phrasings, I should have given more thought to the term and used something less likely to be confusing.
- josteink 13y agoBy "be frozen" he didn't mean "Google will declare it to be unchangeable", he meant "users relying on it will prevent any of us from being able to change it." And that's only a problem because Google decided to ship it now, RIGHT NOW instead of caring about the standards process and maybe holding off for a little bit. Nobody dies if Google ships a little bit later.
- mcherm 13y agoMaybe, but "We want to ship now!" is a VERY different statement than "We want to lock in the API now and refuse to change it later!". I have a great deal of sympathy for the first one.
- randallu 13y agoI disagree that the Shadow DOM is pretty awesome. I think scoping style is valuable, but building components that are exposed as new tags is not appealing given the vast complexity of the implementation and the limitations of tags. Markup has a very weak type system (strings and children) which makes building complex UIs more painful than it has to be (this also stands for markup driven toolkits like angular and knockout -- where the equivalent of main() is HTML markup and mostly declarative). Markup isn't a real programming language, and it's very weak compared to a true declarative programming language. JavaScript however is a real programming language with all of the constructs you need for building extensible systems. For building anything complex (which is where Shadow DOM should shine) you will need to use extensive JS, you will need your Shadow DOM components to expose rich interfaces to JS... At which point, why are you still trying to do mark-up first -- it's something that's more "in your way" than helpful.
- caitp 13y agoWhile you're perfectly allowed to disagree, it sounds like what you're saying is this: "Collections of div-soup activated by jQuery plugins are the way to write maintainable web applications that make sense" It's not as though Javascript has no role whatsoever in custom elements, but really, there's a lot to be said about how this way of working will be a huge improvement over the current jQuery + div-soup status quo.
- randallu 13y agoNo, that's not what I meant. I'm saying that DOM through its relationship to HTML has weaknesses that make it unsuitable for building application components out of. "jQuery-enabled div-soup" is an example of how mixing presentation with model and logic yields unmaintainable results. I have been interested in React.js recently, since it provides an interface to create reusable components and to use them inside a rich programming language with full types. I think that's a better example of a competing idea. My experience is with building single page apps from scratch, so maybe there's a common use-case (embedding a twitter widget, or a 3rd party comment system in a blog) that Shadow DOM and Custom Components will address that I'm not familiar with.
- chris_wot 13y agoThe following reply does not inspire confidence: Sorry, this is my fault. These things were defined in the spec before, but we sliced them out for a separate spec, which I was supposed to write and haven't gotten finished yet. http://lists.w3.org/Archives/Public/www-style/2014Feb/0113.html http://lists.w3.org/Archives/Public/www-style/2014Feb/0113.h...