5 ms·

> However, I admit that I missed myself and should've called out that the spec, while stable, is still a draft - that's a mistake on my part. As is never menti

> However, I admit that I missed myself and should've called out that the spec, while stable, is still a draft - that's a mistake on my part. As is never mentioning the fact that WebUSB is considered harmful by both Safari and Firefox, and hiding it behind "oh, I do hope other browsers will implement it". They won't, you are perfectly aware of it, and the reasons why they won't.

RReverser 5y ago
I think I already made it clear in another thread why I'm not going to interact with your comments in particular. There's no need to try and post variations of the same comment throughout the tree. At the same time, I'm perfectly happy to respond to questions and concerns of other people like the one above who can express their thoughts without resorting to personal attacks.
- dmitriid 5y ago
  > I'm perfectly happy to respond to questions and concerns of other people What a wonderful word, "respond". Not answer. Respond. That's exactly what you're doing: responding HN: This is not "finalised" Respond: oh yes, it is finalised. Because browsers [sic! plural] conform to the living standard HN: It's not implemented or supported by browsers (plural). Respond: Oh, it doesn't matter, all that matters is that Chrome implemented it (Aside: for something to be considered standard and finalised there should be at least two independent implementations. See history of why WebSQL on top of Sqlite never happened) HN: Others view this standard as harmful Respond: why are you attacking me personally > who can express their thoughts without resorting to personal attacks. To me you are just another in a long list of Chrome's talking heads who all behave absolutely identically (and their behaviour is very well documented across various internet platforms): ignore, deflect, gaslight. What you see is simply a reaction to this. To your credit you haven't stooped down to gaslighting. Want to see a different approach? Change your (as in Chrome team's) behaviour. That is, however, unlikely: Chrome stands nothing to lose by ignoring any and all concerns about its behaviour.

RReverser 5y ago

I think I already made it clear in another thread why I'm not going to interact with your comments in particular. There's no need to try and post variations of the same comment throughout the tree. At the same time, I'm perfectly happy to respond to questions and concerns of other people like the one above who can express their thoughts without resorting to personal attacks.

dmitriid 5y ago
> I'm perfectly happy to respond to questions and concerns of other people What a wonderful word, "respond". Not answer. Respond. That's exactly what you're doing: responding HN: This is not "finalised" Respond: oh yes, it is finalised. Because browsers [sic! plural] conform to the living standard HN: It's not implemented or supported by browsers (plural). Respond: Oh, it doesn't matter, all that matters is that Chrome implemented it (Aside: for something to be considered standard and finalised there should be at least two independent implementations. See history of why WebSQL on top of Sqlite never happened) HN: Others view this standard as harmful Respond: why are you attacking me personally > who can express their thoughts without resorting to personal attacks. To me you are just another in a long list of Chrome's talking heads who all behave absolutely identically (and their behaviour is very well documented across various internet platforms): ignore, deflect, gaslight. What you see is simply a reaction to this. To your credit you haven't stooped down to gaslighting. Want to see a different approach? Change your (as in Chrome team's) behaviour. That is, however, unlikely: Chrome stands nothing to lose by ignoring any and all concerns about its behaviour.