FaceTime on the web requires Chrome or Edge, no mention of Firefox

Post by moron4hire » Tue, Jun 08, 2021, 2:00 PM UTC

kevincox wrote: post #68

hinoki wrote: post #66

Earlier quoted context omitted.

Even Microsoft couldn’t do it, gave up, and just used Blink. I assume management just saw how much of each release was spent being bug compatible with Chrome and decided it wasn’t worth it.

Microsoft dropping EdgeHTML was the biggest blow to the open web in many years. I really hope that Mozilla can pull some magic to keep Google from maintaining basically full control of web standards.

Post by swsieber » Tue, Jun 08, 2021, 2:02 PM UTC

hartator wrote: post #54

tyrion wrote: post #49

It may seem an advantage to use the latest cutting edge features of a single platform, instead of using well established standards which are compatible with every browser. Sure, you are going to leave out some small minority of users, but you gain access to many new features. However, you are helping push the web become an increasingly centralized place, controlled by just a few entities, with interests which are ver…

> you are helping push the web become an increasingly centralized place Does it? Open source standardization is a good thing. Still not sure why html/css/js engine should be the exception. No one is calling for competition for QR code, torrent protocol, or the other billion of very dominant open source projects.

Post by 52-6F-62 » Tue, Jun 08, 2021, 2:03 PM UTC

rchaud wrote: post #85

aseipp wrote: post #64

Earlier quoted context omitted.

> Next time that your manager asks you if you can have that sweet feature, instead of saying "sure, we just need to drop support for Firefox", please consider trying to explain what are the consequences in the long term. If the future of the web relies on developers groveling at the feet of a manager, then there's no fight or discussion to be had, because the web has already unequivocally lost. The only thing that's…

> If the future of the web relies on developers groveling at the feet of a manager, I see a lot of this 'devs v suits' type language used on HN, with the implication being that the developers are principled stewards of technology suffering under the cosh of KPI-obsessed MBAs. What causes this? The majority of product managers I've met have technical backgrounds, and they have also had to cut corners to keep their pro…

Post by 1over137 » Tue, Jun 08, 2021, 2:04 PM UTC

lotsofpulp wrote: post #78

whywhywhywhy wrote: post #59

Earlier quoted context omitted.

I can count the number of developers I've worked with over the last 5 years that care about it working in any browser other than Chrome on one finger. This idea that only Chrome matters is absolutely coming from the bottom up and when you point out something broken in Safari the first response from them is "Does it work in Chrome?" before they even look at it because they themselves don't even test in a second browse…

> This idea that only Chrome matters is absolutely coming from the bottom up and when you point out something broken in Safari the first response from them is "Does it work in Chrome?" before they even look at it because they themselves don't even test in a second browser. I would have thought at least iOS Safari would be a major consideration for anyone due to the ubiquity of iOS devices.

Post by 52-6F-62 » Tue, Jun 08, 2021, 2:06 PM UTC

ballenf wrote: post #72

whywhywhywhy wrote: post #59

Earlier quoted context omitted.

I can count the number of developers I've worked with over the last 5 years that care about it working in any browser other than Chrome on one finger. This idea that only Chrome matters is absolutely coming from the bottom up and when you point out something broken in Safari the first response from them is "Does it work in Chrome?" before they even look at it because they themselves don't even test in a second browse…

That mirrors my experience. It's not POs or PMs that hear about some new niche browser feature only supported by Chrome. It's devs that want to play with the latest toys and kind of look at you weird if you use Safari. There's an annoying assumption from other devs that I must be using Safari out of ignorance. They quickly get over it, but it's a problematic first impression thing when working with new teams.