Google proposes changes to Chromium which would disable uBlock Origin

Re:Google proposes changes to Chromium which would disable u... by jbigelow76 on Tuesday January 22, 2019 @10:08PM (#18975305)

I bet a decent chunk of the MS engineers lobbied to adopt Gecko instead of Chromium when they decided to move away from EdgeHtml. I wonder what the reasoning was for not going that route, it seems like a huge miss and a total acceptance of a browser monoculture.

[ Parent | on HN ]

Re:Google proposes changes to Chromium which would disable u... by ChrisSD on Tuesday January 22, 2019 @10:24PM (#18975389)

Gecko is deep in to a transitional phase. Once it comes out the other end it may be simple to embed but it's currently far too early for that.

On the other hand Chromium is relatively simple to adapt with many real world examples to learn from.

(Personally I think they should stick with EdgeHtml but it seems that ship has sailed).

[ Parent | on HN ]

Re:Google proposes changes to Chromium which would disable u... by dralley on Tuesday January 22, 2019 @11:06PM (#18975589)

I wish they would have thrown in with the Servo project, but Chromium is ready now and Servo isn't, so I'm sure that factored in.

[ Parent | on HN ]

Re:Google proposes changes to Chromium which would disable u... by fiddlerwoaroof on Wednesday January 23, 2019 @01:20AM (#18976108)

I wonder how quickly servo could become feature if a major player decided to adopt it.

[ Parent | on HN ]

Re:Google proposes changes to Chromium which would disable u... by addicted on Wednesday January 23, 2019 @02:45AM (#18976457)

nodeJS uses Chromium and not Gecko. I suspect MS’s requirements basically necessitated the use of Chromium.

However, this does provide an opening for MS edge, if MS forks Chromium for Edge and excludes user hostile “features” such as this.

[ Parent | on HN ]