rbyers

8 ms·

1.
by rbyers 3y ago
In the case of blink-dev, yeah moderators like me. But AFAIK we didn't block any replies there at all because nobody in that forum was making threats or anything like that. I also haven't seen much of anything on these HN threads
2.
by rbyers 3y ago
> Some things just aren't consistent, and I don't believe that you know what "the openness of the web" means, or really care :-). I certainly could have done a better job trying to convince you of that in that post. P
3.
by rbyers 3y ago
Thank you!
4.
by rbyers 3y ago
Did you read the rest of the thread? Plenty of really good constructive yet forceful feedback on that thread which I was applauding and celebrating.
5.
by rbyers 3y ago
I think it's pretty disingenuous to suggest that I "tarred all opposition as criminals". Still I admit my wording could have been better, please see follow-up: https://groups.google.com/a/chromium.org&#x2
6.
by rbyers 3y ago
Bingo
7.
by rbyers 3y ago
Did you see my point later in the thread about moderators like me explicitly approving all the posts which were arguing forcefully (but respectfully) against WEI? I think it's pretty clear we're not shutting down respectful disagr
8.
by rbyers 3y ago
I'm one of the blink API owners who would need to approve this feature if it were to ship in Chrome. I outlined some of my thoughts on this earlier here: https://groups.google.com/a/chromium.org/g/blink-d
9.
by rbyers 11y ago
This is a complicated set of trade offs and I've argued on both sides of the fence so I can't pretend to imply the decision is at all clear cut. But let me respond to a couple details here. First, the 'jQuery bloat' you
10.
by rbyers 11y ago
I think there is a valid concern here. But what we're seeing in practice from many major frameworks and apps is that they're unifying events anyway and special-casing the device type when needed for a great experience. Pointer E
11.
by rbyers 11y ago
Of course Microsoft has now shown the DO value compatibility enough to implement Touch Events, and is even one of the most active members in the Touch Events community group working to improve Touch Events in the W3C.
12.
by rbyers 12y ago
> I'm pretty sure Microsoft is going to go full steam ahead with pointer events. Note that even Microsoft acknowledges the "touch events are here to stay" argument: IE mobile now supports touch events: http://bl
13.
by rbyers 12y ago
Agreed! We had a great "input face-to-face" meeting at Microsoft back in June, and the collaboration between IE, Safari, Firefox and Chrome teams seems better than ever. Despite our differences of opinion, we finally all appear
14.
by rbyers 12y ago
Right, we (Chrome team) definitely care about multi-input-device scenarios (I started at Google by leading the chrome work for the chromebook pixel). We're just trying to project out 5-10 years where we expect most Interent traffic to
15.
by rbyers 12y ago
There was a delay, but we worked past it. The web would definitely be a better place if Apple would participate in the input API standardization process though.
16.
by rbyers 12y ago
Well said. We're deeply committed on the blink team to making such polyfills and frameworks easy (eg. it's a big part of why we shipped touch-action in blink). That's where the fighting over what API shape is "best&quo