Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

apple.com

Post reply on HN
Print view View original

181–190 of 199 posts

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

#181

Post by leppr »

neoberg wrote: post #124
syshum wrote: post #106

Earlier quoted context omitted.

Replacing Microsoft Overlord with Google Overlord does not seem like much of a win

This might come as a surprise but not everyone sees the world from a "freedom" perspective. In terms of practical/day to day experience we won something that works over something that didn't.

IE "worked" too. The main problems came from having to develop for multiple browsers with incompatible implementations. If you restricted yourself to IE, it was quite painless. Any quirk you'd encounter daily was documented, and at the time there were quirks in all implementations anyway.

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

#182

Post by Jcowell »

machello13 wrote: post #55
amq wrote: post #31

They did mention firefox during the presentation.

This feature also won't be available for several months, so it's possible they're planning for Firefox support but hedging their bets in case they can't get it done in time.

It’s technically available right now I believe.

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

#183

Post by wolverine876 »

gjsman-1000 wrote: post #67

If you review Mozilla's business practices, constant spending on NGOs and Politics, ludicrous executive compensation, and recent layoffs of the engineering team, constant buying and starting of new projects (Pocket, Firefox OS) only to abandon them, and so on, it is clear that at least part of the story is that Firefox has been through incredible mismanagement even as they should have been in the fight for their live…

> constant buying and starting of new projects (Pocket, Firefox OS)

Constant? Aren't those both ten years old or more? No organization can create successful projects by fiat; there's necessarily a lot of failure to find one success. If they ain't failin' they ain't tryin'.

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

#184

Post by slver »

extra88 wrote: post #169
acqq wrote: post #164

Earlier quoted context omitted.

The state of it in Firefox: "Opened Apr 2020" https://github.com/mozilla/standards-positions/issues/330 Then in October added "Insertable streams is worth prototyping " Also: "I will remind people that this isn't the place for advocating for what gets implemented in Firefox. This is something that the media team needs to work out." then "closed 26 Oct 2020" But, hey, it's June 2021, you just got a new UI redesign whi…

Do you really think the people who implemented UI changes are the same people who could implement an end-to-end encryption API?

Do you think people who implement ui changes are paid with same money as those who implement encryption api?

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

#185

Post by slver »

cyanydeez wrote: post #180
acqq wrote: post #164

Earlier quoted context omitted.

The state of it in Firefox: "Opened Apr 2020" https://github.com/mozilla/standards-positions/issues/330 Then in October added "Insertable streams is worth prototyping " Also: "I will remind people that this isn't the place for advocating for what gets implemented in Firefox. This is something that the media team needs to work out." then "closed 26 Oct 2020" But, hey, it's June 2021, you just got a new UI redesign whi…

firefox has serious performance issues, i had to switch to chromium. i really want to support firefox in my development but their tooling is just not presented in a rational footprint. when i inspect a vue proxy object, i dont want to see all the setters and getters. they are losing mind share because neight to user facing components normthe dev facing have a well considered presentation or pefformancd

After Chrome's RAM guzzling architecture and Firefox' Rust rewrite promises, reading this is so disappointing.

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

#186

Post by acqq »

slver wrote: post #184
extra88 wrote: post #169

Earlier quoted context omitted.

Do you really think the people who implemented UI changes are the same people who could implement an end-to-end encryption API?

Do you think people who implement ui changes are paid with same money as those who implement encryption api?

The most money are paid to the same managers in both cases. The total company expenses in the same period mostly aren't dependent on the nature of the changes implemented. The managers just make their managerial decisions what to set as the goals.

And apparently the board thumbs that up. That's the scope of the problem: "look we make the UI changes" is the "color of the shed" easy to understand illusion of "something" being done.

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

#187

Post by extra88 »

slver wrote: post #184
extra88 wrote: post #169

Earlier quoted context omitted.

Do you really think the people who implemented UI changes are the same people who could implement an end-to-end encryption API?

Do you think people who implement ui changes are paid with same money as those who implement encryption api?

Money is fungible, employees are not. Whether others at Mozilla may be tasked with implementing this API or Mozilla (or someone else) contracts Igalia to do it, the employees responsible for and qualified to work on UI are still going to get paid and will still have other work to do.

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

#188

Post by machello13 »

Jcowell wrote: post #182
machello13 wrote: post #55

Earlier quoted context omitted.

This feature also won't be available for several months, so it's possible they're planning for Firefox support but hedging their bets in case they can't get it done in time.

It’s technically available right now I believe.

Right, I obviously meant actually released publicly and not in beta.

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

#189

Post by slver »

extra88 wrote: post #187
slver wrote: post #184

Earlier quoted context omitted.

Do you think people who implement ui changes are paid with same money as those who implement encryption api?

Money is fungible, employees are not. Whether others at Mozilla may be tasked with implementing this API or Mozilla (or someone else) contracts Igalia to do it, the employees responsible for and qualified to work on UI are still going to get paid and will still have other work to do.

As far as I know Mozilla is not a foundation for charity towards unemployed developers. So their goal is not finding work for their existing employees, their goal is improving the browser in meaningful ways. They're free to lay off and hire people to do this.

Also honestly any developer worth keeping could figure out the task at hand given sufficient time. So to talk about developers as if there's a developer who can only alter the rendering of tabs and what not is kinda silly.

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

#190

Post by DeliriumTrigger »

acqq wrote: post #186
slver wrote: post #184

Earlier quoted context omitted.

Do you think people who implement ui changes are paid with same money as those who implement encryption api?

The most money are paid to the same managers in both cases. The total company expenses in the same period mostly aren't dependent on the nature of the changes implemented. The managers just make their managerial decisions what to set as the goals. And apparently the board thumbs that up. That's the scope of the problem: "look we make the UI changes" is the "color of the shed" easy to understand illusion of "something…

If there wasn't one manager at Mozilla who said to himself maybe in the pandemic with all the working from home stuff being done. Maybe we should look in our webrtc, video codec stack just is sad. No excuse that's just plain bad management.
Post reply on HN