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 prophesi on Thursday December 05, 2019 @02:09PM (#21715313)

Welppp, that's a sad chart.

Though I really doubt Firefox's drop in market-share is that tied to performance. The story is more likely to be Chrome/Chromium as the default on Android, the release of Chromebooks, etc. Of course, this is just me interpreting facts with my feel good opinion.

Back to the main point at hand, though, Firefox is obviously not doing well today either according to that chart. But its performance and dev tools are top-notch.

[ Parent | on HN ]

Re:How to fight back against Google AMP as a web user and a ... by LoSboccacc on Thursday December 05, 2019 @03:17PM (#21716036)

performance, yes, dev tools are lacking all the listed features

historically speaking, Chrome got the share it got because Firefox was a memory hog and was running a purely interpreted JavaScript engine on top of a single threaded rendering engine in a time where core numbers and web app were becoming mainstream.

[ Parent | on HN ]

Re:How to fight back against Google AMP as a web user and a ... by prophesi on Thursday December 05, 2019 @04:23PM (#21716709)

Hm, touché! That lines up with the timeline, though I still think Chrome's _sustained_ and _stark_ uptick in market share is due to their market dominance in every field of one's digital life.

I must admit that I've never used those missing dev tools in Chrome, as those issues are non-existent in a webpack environment (that's essentially what workspace mounting and hot code reloading is mirroring). And the search function works with all files, including inline code, as of Quantum as well.

[ Parent | on HN ]