How to fight back against Google AMP as a web user and a web developer

Re:How to fight back against Google AMP as a web user and a ... by kodablah on Thursday December 05, 2019 @12:28PM (#21714205)

> which is based on Chromium, but does not phone home to Google

Same deal with the browser I use. My preferred UI + Chromium is better for me than FF. There are three common cross-platform browser approaches: Chrome, FF, and Chromium-based. Only one of those three offers extreme visual and feature flexibility. I sound like a broken record saying it, but FF should really invest in embeddability so we can take their engine and run.

[ Parent | on HN ]

Re:How to fight back against Google AMP as a web user and a ... by o-__-o on Thursday December 05, 2019 @01:28PM (#21714805)

And chromium was forked from webkit.. so why not head to the source and cut off the cancer at the root?

I can't believe I just called Google the cancer, but would anyone disagree?

[ Parent | on HN ]

Re:How to fight back against Google AMP as a web user and a ... by kodablah on Thursday December 05, 2019 @02:32PM (#21715586)

> so why not head to the source and cut off the cancer at the root?

For me, easy consumability. I use Chromium Embedded Framework, I don't actually put the hard work into building and maintaining an API myself. I'd love a similar effort for Gecko (there was effort at one time, but nothing of late IIRC).

[ Parent | on HN ]