4 ms·
> Why is this even a thing? Do you think that this point was never raised with them? It was, look at w3c lists, look at mozilla bugzilla, look at chrome bug tr
by baybal2 7y ago
> Why is this even a thing?
Do you think that this point was never raised with them? It was, look at w3c lists, look at mozilla bugzilla, look at chrome bug tracker and long lists of WONTFIX bugs asking to let user disable those sensors. It goes almost like this "I do not need the website know how I hold the phone, — No, you really have no reason to disable sensors," after them being asked for the tenth time. HOW DO YOU REASON WITH SUCH PEOPLE?
Whomever ever came first with this idea must be found and fired, and people should make sure that no contributions to web standards to be accepted from that person. Whomever followed, allowed, and collaborated on that process should also be fired along.
People who got to write web standards today are unqualified for this role in their prime majority. Some of those "software engineers" speak in more lawyery, MBA-like manner than real lawyers do. They are really hired as lobbyist, to push, push, push their client's proposals to approval in any way possible, no matter how much they have to break the browser to do that. People can't work with them. They are toxic.
It should be a default presumption that people hired to write standards should be highly professional in their demeanour, experienced, trusted, and give no favours to one vendor or another, be direct, and above all be helpful. There should be no second thought about that.
Now, how many of people involved with WhatWG will meet these criteria?
- edoceo 7y agoI agree with your points and am not sure why your response is light grey. Those criteria are too wordy for my liking - I think the summary from Tron works just as well here and is slightly more succinct: I fight for the user.