4 ms·

All extensions are different. My extension (excluding NPM-dependencies) counts in at around 20k lines of TypeScript + various other resources. I think that cou

All extensions are different. My extension (excluding NPM-dependencies) counts in at around 20k lines of TypeScript + various other resources. I think that counts as above average. Granted, the background-page/worker portion of it was not the dominant aspect, and thus had less rewrites required than if things had been the other way around. That said, migrating to V3 was way less effort than I thought it would be. I'm not saying it will be so for all extensions, but it was for mine, and it may be for others as well. Basically I'm just trying to provide some additional perspective here besides the usual content-blocker perspective which so far has gotten 100% of the narrative. Note I'm in no way dismissing that concern, but I think having the entire conversation framed around those extensions only does not correctly represent the huge variations found across the extension ecosystem.

creesch 4y ago
> All extensions are different. Absolutely, I didn't reply to say you are wrong or anything in that regard. I basically wanted to give some additional perspective. > I'm not saying it will be so for all extensions, but it was for mine, and it may be for others as well. Yup, for many extensions it might be relatively painless. It was for a different extension where I just had to replace ancient ajax calls for fetch and move some functionality to the front into content_scripts. At the same time it was a lot of work for the extension I mentioned in my previous comment. Which I might add is not an extension that has anything to do with content blocking which I agree does get a lot of attention. But the truth is that there are also a number of extensions that made creative use of the current manifest construction. Those extensions no longer can offer the same functionality, have to rewrite a lot of code with no functional benefit or redo functionality in a way that degrades the user experience. Even if for the majority of extensions migration is relatively painless it still leaves those extensions where it isn't and even those that can't be migrated due to how they work. They won't be a majority, but it still means that once the switch is done the ecosystem will be less diverse.

creesch 4y ago

> All extensions are different. Absolutely, I didn't reply to say you are wrong or anything in that regard. I basically wanted to give some additional perspective. > I'm not saying it will be so for all extensions, but it was for mine, and it may be for others as well. Yup, for many extensions it might be relatively painless. It was for a different extension where I just had to replace ancient ajax calls for fetch and move some functionality to the front into content_scripts. At the same time it was a lot of work for the extension I mentioned in my previous comment. Which I might add is not an extension that has anything to do with content blocking which I agree does get a lot of attention. But the truth is that there are also a number of extensions that made creative use of the current manifest construction. Those extensions no longer can offer the same functionality, have to rewrite a lot of code with no functional benefit or redo functionality in a way that degrades the user experience. Even if for the majority of extensions migration is relatively painless it still leaves those extensions where it isn't and even those that can't be migrated due to how they work. They won't be a majority, but it still means that once the switch is done the ecosystem will be less diverse.