> I can see that being an issue if the web is centralising around one proprietary engine, but why does that apply to Blink? If Google turns completely evil that won't take away from all the webcompat, optimisations, and security in Blink, and any bad feature (ManifestV3) can be patched out easily. I argued this before, and I still stand by it: They'd also have better webcompat, and take away one reason to switch to Chrome (i.e., sites that break in Firefox that render fine in Chrome and sites that rely on cutting edge draft standards that Firefox won't implement for a few months/years). But they'd also be able to much more easily benefit from Blink's security (already had site isolation for years, apparently a better sandbox, etc) and the contributions thousands of other companies make to Blink (Intel, Samsung, etc), companies that don't contribute to Gecko and Webkit as much if at all. That would be the "trustworthy, community Blink". It does not store any personal data.If Mozilla switched to Blink, they'd be maintaining their own version, and it could diverge from Google's. The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. The cookie is used to store the user consent for the cookies in the category "Performance". This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. The cookies is used to store the user consent for the cookies in the category "Necessary". The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". The cookie is used to store the user consent for the cookies in the category "Analytics".
These cookies ensure basic functionalities and security features of the website, anonymously. Necessary cookies are absolutely essential for the website to function properly.
0 kommentar(er)
