News for hackers. Stuff that matters.
Re:Google sets burial date for legacy Chrome Extensions, fea... by cinquemb on Tuesday September 28, 2021 @04:51AM (#28680609)
As someone who wouldn't mind if Mozilla post Eich can die under a metadata drone strike (doubly so for google) and will still use my FF fork and avoid chrome/chromium based browsers like the plague, brave, seems like they are willing to build in support for decentralized (to me at least) and p2p web directly into the browser (rather than leave it up to potentially less performant 3rd party extensions which may be ok, but not ideal in ff) than all the crap I have to compile out of ff occasionally.
Re:Google sets burial date for legacy Chrome Extensions, fea... by 2Gkashmiri on Tuesday September 28, 2021 @05:25AM (#28680799)
why cant brave build on top of firefox?
Re:Google sets burial date for legacy Chrome Extensions, fea... by cinquemb on Tuesday September 28, 2021 @06:08AM (#28681038)
See Brendan's response to me last week[0], which I think comes down to feature set they want to support rather than do all the work it would require to build that in servo now (they went from gecko [no public info on this] -> electron -> and now chromium. they would have to migrate from chromium -> servo).

I wish they did, and just cared less about all the other features that were missing from gecko (but that's just be being selfish and not wanting to build out native stuff myself lol)

[0] https://news.ycombinator.com/item?id=28605711

Re:Google sets burial date for legacy Chrome Extensions, fea... by 2Gkashmiri on Tuesday September 28, 2021 @07:30AM (#28681540)
cool. so an excel sheet decided google to be the clear winner in present feature comparison set and instead of helping the community in bridging the gap, they decide to go with the flow. cool. i am fine with my ff