Mozilla’s Uncertain Future

Re:Mozilla’s Uncertain Future by ohgodplsno on Saturday August 15, 2020 @04:52AM (#24167213)

Whereas Chrome makes life miserable for users not using Chrome, because of the sheer amount of non-standard, Chrome-only features used in current webdev.

[ Parent | on HN ]

Re:Mozilla’s Uncertain Future by harshitaneja on Saturday August 15, 2020 @05:01AM (#24167252)

Which non-standard features?

[ Parent | on HN ]

Re:Mozilla’s Uncertain Future by ohgodplsno on Saturday August 15, 2020 @05:28AM (#24167416)

Using google properties is a bit of an easy jab, but:

Youtube using polymer/shadowdomv0 and absolutely destroying performance on Firefox is a an easy example. Google Earth used non-standard APIs.

Otherwise, have a quick search for "non-standard" on MDN, and see how many of those Chrome implements.

[ Parent | on HN ]

Re:Mozilla’s Uncertain Future by eyko on Saturday August 15, 2020 @07:06AM (#24167996)

But both of those are Google products. Yet here we are in a thread blaming an entire generation of web creators and users.

[ Parent | on HN ]

Re:Mozilla’s Uncertain Future by pjmlp on Saturday August 15, 2020 @12:11PM (#24169914)

Ah, so only when Microsoft does it is bad, but when that generation worships Google for doing the same it is suddenly alright.

[ Parent | on HN ]