3 ms·

I made Firefox as the primary browser even though battery usage during conference call and some webapps is much higher than chrome on a Mac. I do it on princip

I made Firefox as the primary browser even though battery usage during conference call and some webapps is much higher than chrome on a Mac. I do it on principle and make sure my apps work on Firefox besides chrome. Although many friends and fellow developers tell me why I spend extra efforts. Web components created a lot of issue when trying to make them run on both Firefox and chrome. But I went ahead with it and my front end team need to put a lot of additional efforts. I don't know why it's so hard to stick to standards. Both chrome and Firefox will behave bit differently for CSS and JavaScript. Developing a PWA which works good on both browser feels like developing native apps for Android and iOS using cross platform toolkits, which at times require a lot of additional code and testing just so that they work predictable. Still results in not so good experience.

sfink 7y ago
What I've heard is that Chrome shipped an unfinished early version of the web components spec, and now there are sites relying on it because it works in Chrome and that's good enough. I think the spec has been more or less finalized now? I'm not sure whether it's shipping in both browsers, though. Something is (eg for firefox it's since 63), but I don't know exactly what. I believe YouTube uses a whole framework based on the preratified spec?
- dragonsh 7y ago
  Even though the spec is finalized there are enough variation on support on different browsers leading to substantial efforts to make a web components based pwa work on multu-browser. If it had been worked out properly there's isn't any need of react or angular except for a state management library, since the views and components is taken care of by the browser directly.