4 ms·
I wouldn't get too excited. The way the Chromium project responded to concerns over the API change leads me to believe that Chromium has a lot more restricting
by jgowdy 7y ago
I wouldn't get too excited. The way the Chromium project responded to concerns over the API change leads me to believe that Chromium has a lot more restricting... I mean "redesigning" of extension APIs in the pipeline regardless of what users want. Think about it.
1) Propose API changes with blatantly obvious impacts on some of the most popular extensions. Include no explanation of how these extensions can rationally adapt to these new APIs and provide the same or adequately similar functionality.
2) Don't bring any timing data to justify the performance claim that ad blockers are taking an irrational amount of time implementing their content filtering. When others run these same tests they find no performance issues.
3) Characterize any strong reactions to such a suggested change as inappropriate. Feign surprise and dismay at the fact that such reckless API changes, which would drastically change the status quo on the web, are invoking.
4) Condemn those who didn't react the way you expected when you threatened to vastly change their web browsing experience for the worse. This helps diminish user input in the future, by tying everyone with honest opinions to those who express their opinions in an inappropriate or unprofessional way.
5) Act insulted when people point out that your employer, who is in control of the situation, happens to financially benefit from the changes.
The above experience was so distastefully handled across the board, I really think it justifies a unified and community supported "ungoogled-chromium" project without any of their trademarks in the name. That way we the users of the web can determine our relationship with the browser. It's the user's agent, not the browser vendor's agent.
But most importantly, use Firefox with containers and uBlock Origin.
PS. Despite the above, kudos on the port of NoScript. Never give up, never surrender.
- kevin_b_er 7y agoI've seen this pattern of behavior as well. It makes me seriously wonder if the Google engineers working on Chromium/Chrome are being corrupted by the advertising desires of Google's management. Their behavior is much of a politician trying to do something while trying to hide their end-goal.
- barberousse 7y agoProbably the middle: management makes the executive call and deliberately leaves the explaining to the bottom of the pyramid who themselves are largely trained in providing technical responses, not intricate PR spin
- jgowdy 7y agoI prefer to direct my thoughts towards the project as a whole and not fixed on any particular person or persons within the project. I have a very limited view of the project, certainly not enough to question anyone's motives specifically.