14 ms·
That seems uncharitable. The issue at hand is that Mozilla is dropping support for plug-ins, and hangouts' implementation of media streaming uses a plug-in. G
by ajross 10y ago
That seems uncharitable. The issue at hand is that Mozilla is dropping support for plug-ins, and hangouts' implementation of media streaming uses a plug-in. Google didn't do anything to break Firefox here except fail to develop an alternative in time. The actual software change being pushed to break the functionality is on Mozilla's end (which I don't disagree with, FWIW).
Lots of other stuff is breaking because of this Firefox change too, and it's not a conspiracy.
- chimeracoder 10y ago> hangouts' implementation of media streaming uses a plug-in. Sort of. That's true in non-Chrome browsers. In Chrome, Hangouts uses WebRTC. Though the Google Talk plugin that Hangouts uses in Firefox is (as I understand) used as a way of patching Firefox's WebRTC to make it behave more like Chrome's WebRTC.
- Etzos 10y agoConsidering Mozilla has been planning to remove support for NPAPI plugins for well over a year and had made public announcements of such and considering Chrome has already removed such support it actually is far less uncharitable. How much leeway should be given when they had ample notification of such breakage and had workarounds available for their own browser? I'll agree that the parent's link is a bit uncharitable, but given the circumstances it seems a bit more poignant and dismissing it entirely seems a bit much.
- hackuser 10y ago> The issue at hand is that Mozilla is dropping support for plug-ins, and hangouts' implementation of media streaming uses a plug-in Every time two systems need to integrate, the vendors always can and often do point the finger at each other. In this case, Google had since October 2015 to fix this, didn't do it, and now attributes the problem to Firefox. https://news.ycombinator.com/item?id=13764449 https://news.ycombinator.com/item?id=13764449
- bpodgursky 10y ago> Google had since October 2015 to fix this Sorry, but I don't really believe in an internet where the default assumption is "you have to rewrite your application within two years, or if it's broken it is your fault" Hangouts relied on browser support which worked. It's crufty, I get it, but it was supported. If this was Microsoft pulling support for old Windows 98 API calls, everyone on HN would be appalled that their old-but-reliable software no longer worked on a new OS. But then for some reason, they give Mozilla a complete pass on the exact same behavior. Finished webapps should not require a constant refactoring and fixing to keep them usable. We're only hearing about this because it is Hangouts and Google. Sure, Google _could_ throw a bunch of money at it and fix it, but there are thousands of other little sites which will just silently die forever, and I don't believe Google should _have_ to update this.
- hackuser 10y ago> I don't really believe in an internet where the default assumption is "you have to rewrite your application within two years, or if it's broken it is your fault" In a way I agree; the lack of stability is costly for users, especially in managed environments where changes needs to be planned and tested thoroughly before deployment. Frequent updates do seem to greatly improve quality, but the lack of support for old versions is painful. It's a way of shifting the cost of old versions from the vendor (who would have to maintain them) to the user (who has to deal with the updates). On the other hand, Google does the same thing and it seems like the norm now for software, especially web and Internet-based applications. I've come across many web apps that will only support the latest (or two latest) versions of browsers. It's also far better for security. Arguably nobody has less reason to complain than Google: It's their own practice, and possibly nobody has better resources for keeping up - money, personnel, talent, and expertise - they make browsers themselves.
- digi_owl 10y agoFrankly it was Google that set the ball in motion, by frequently, and quietly, downloading Chrome updates in the background. Next time you launched Chrome, whole new version etc. Mozilla felt they had to jump on the bandwagon or come across at lethargic. To me this is the web dev "push to prod" mentality encroaching on the desktop, and i am not really sure it belongs there.
- ubernostrum 10y agoThe part you're missing is: this comes from Firefox dropping support for NPAPI. Google is also dropping NPAPI. But rather than turn Hangouts into a plugin that could work in the new non-NPAPI world, they've just given it special privileges in Chrome to allow it to keep working, and are letting it break in Firefox.
- TorKlingberg 10y agoIf it was Chrome that dropped support for something (like they do all the time), Hangouts and other Google properties would have been ready on day one.
- accountface 10y agoThey also would have likely known about it for a longer period of time before it was public knowledge.
- mncharity 10y ago> it's not a conspiracy But is it a conflict of interest? Nestle formula wasn't let's kill babies in Africa. It was let's do PR damage control first, and if the PR cost gets too high, we'll eventually change our marketing strategy. Unilever wasn't let's increase racism in India. It was skin lightening products are the largest personal care market segment, so let's advertise and develop the market. Microsoft wasn't let's reduce the world's access to knowledge in books. It was what's bad for Google is good for us, so let's quietly fund stumbling blocks. Why should I inconvenience my customers by fixing my implementations of your standards? Why should I delay giving features to my customers because of your standardization slowness? What part of your customers switching to be my customers should I prioritize as a problem? Situations have associated incentives. Ethics can shape response. But incentives do matter. No conspiracy needed.