Press F on Chrome

Google's browser has several release rings which reflect changes to Chrom* at different speeds:
1- fastest (Canary Chrome) *closed source
2- fast (Chromium) *open source
3- slow (Chrome) *closed source

In the Google Groups post linked above Simeon Vincent (Chrome Team) had this to say: "Our goal with this preview is to give developers a way to start experimenting with some of the most significant changes to the platform in order to provide targeted feedback. We're hoping to land this in Canary in the next few months. We'll share more details about the preview in the Chromium Extensions Google Group once we get closer to launch. "

As is the case with all changes to the Chrome source they will first be reflected in Chrome Canary, then they will be seen in Chromium, and eventually they will make their way into Chrome (stable). All of these browsers will eventually fully adopt ManifestV3 as the new extension API.

Attached: ChromeTeam.webm (320x262, 300.12K)

I just switched to Chrome literally 2 weeks ago because Firefox has finally become an unusable piece of shit I've been using Firefox forever and swot eby it, but they just continually made it worse and and less stable. Am I going to be forced to Opera now or what?

Read this post:
Opera and many others are all based on Chrom*/Electron. Even Microsoft's newest version of Edge is based on Chromium.

Attached: 1500225836463.jpg (482x427, 60.77K)

It's also worth noting that modern Firefox (just like Chrome) is outright spyware.
spyware.neocities.org/articles/firefox.html
spyware.neocities.org/articles/chrome.html

Full list here:
spyware.neocities.org/articles/browsers.html

Time to make a pslemoon/waterfox esque fork of chromium I guess.


Do it right or don't do it at all.

Waterfox or palemoon.
You know shit sucks when enthusiasts has to unfuck shit by forking it.

Best case scenario is a Waterfox-like soft fork.
Worst case scenario is a Palemoon-like hard fork.
Twitter images explain the problem with the API "aging out" even if for a brief time it can be re-enabled with some minor adjustments to source / some flags.

Attached: Screen Shot 2019-05-30 at 9.07.27 PM.png (638x1109 274.19 KB, 199.45K)

you mean the furry browser that blacklisted an ad-blocker and intentionally mislabeled it as malware because it dared to actually click the ads while blocking them? (adnauseam)

if they did it with one add-on they are likely to do it to another. yes i know the blacklist was easily bypassed by it shows the furry faggot dev is not someone to be trusted

lol single threaded Palememe is so fucked up because it never got the improvements from modern firefox like Waterfox did.

Lovely that we are going down this path with Chrome now.

doubtful; the enterprise version is surely proprietary.

This is an intentional power grab by google they aren't going to leave it as a flag, and even if they did the damage would be done. 99% of users are goyim and wont' compile their browser themselves, this means the add-on developers will be forced to use the more restricted api's anyway to cater to the lemmings, which are the majority of the userbase. The damage will be done.